BGL File Format - Revision history

Hervesors: re

2026-02-18T16:12:08Z

← Older revision		Revision as of 11:12, 18 February 2026
Line 6,000:		Line 6,000:
	\| QMID V value (Level 9)		\| QMID V value (Level 9)
	\|}		\|}
	~~Records~~ are sorted using the following order (based on string comparison):		VOR/ILS, NDB, TACAN index records are sorted using the following order (based on string comparison):
	Region identifier (except ILS indexes)->Airport identifier->ICAO identifier		Region identifier (except ILS indexes)->Airport identifier->ICAO identifier
			Waypoint index (0x2A) records are sorted using the following order: Waypoint type (NDB->VOR>other types)->Region identifier->Airport identifier->ICAO identifier
	= Annexe A =		= Annexe A =
	== Computing the bounding coordinates from a DWORD value ==		== Computing the bounding coordinates from a DWORD value ==

2026-02-08T22:49:24Z

← Older revision		Revision as of 17:49, 8 February 2026
Line 6,094:		Line 6,094:
	for airports, ILS, VOR, NDB and waypoints there are up to 5 digits/letters, and the result is shifted		for airports, ILS, VOR, NDB and waypoints there are up to 5 digits/letters, and the result is shifted
	left by 5 positions, i.e. multiplied by 0x20. Bits 0 .. 4 of the resulting DWORD may be used		left by 5 positions, i.e. multiplied by 0x20. Bits 0 .. 4 of the resulting DWORD may be used
	for other purposes, maybe indexing (0x01 for airport identifiers, 0x02 for ILS and VOR, 0x03 for enroute NDBs, 0x04 for terminal NDBs, 0x05 for enroute waypoints ~~and~~ 0x06 for terminal waypoints).		for other purposes, maybe indexing (0x01 for airport identifiers, 0x02 for ILS and VOR, 0x03 for enroute NDBs, 0x04 for terminal NDBs, 0x05 for enroute waypoints, 0x06 for terminal waypoints and 0x07 for marker Ids).
	The ICAO identifiers for primary and secondary ILS in a runway record are not shifted.		The ICAO identifiers for primary and secondary ILS in a runway record are not shifted.

2026-02-05T17:55:56Z

← Older revision		Revision as of 12:55, 5 February 2026
Line 6,094:		Line 6,094:
	for airports, ILS, VOR, NDB and waypoints there are up to 5 digits/letters, and the result is shifted		for airports, ILS, VOR, NDB and waypoints there are up to 5 digits/letters, and the result is shifted
	left by 5 positions, i.e. multiplied by 0x20. Bits 0 .. 4 of the resulting DWORD may be used		left by 5 positions, i.e. multiplied by 0x20. Bits 0 .. 4 of the resulting DWORD may be used
	for other purposes, maybe indexing (~~0x00~~ for ~~NDB~~ identifiers, 0x02 for ILS ~~identifiers~~ and 0x06 for terminal waypoints).		for other purposes, maybe indexing (0x01 for airport identifiers, 0x02 for ILS and VOR, 0x03 for enroute NDBs, 0x04 for terminal NDBs, 0x05 for enroute waypoints and 0x06 for terminal waypoints).
	The ICAO identifiers for primary and secondary ILS in a runway record are not shifted.		The ICAO identifiers for primary and secondary ILS in a runway record are not shifted.

2023-12-31T08:51:40Z

2023-12-20T09:16:44Z

ILS/VOR

← Older revision		Revision as of 04:16, 20 December 2023
Line 2,770:		Line 2,770:

	= ILS/VOR =		= ILS/VOR =
	The records for ILS and VOR are in the same section and they are identical for the fixed section. ILS records can have an additional subrecords. The fixed part is 40 bytes long and has the following structure:		The records for ILS and VOR are in the same section and they are identical for the fixed section. ILS records can have additional subrecords. The fixed part is 40 bytes long and has the following structure:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 2,984:		Line 2,984:
	\| Range		\| Range
	\|}		\|}
	After these subsections, a name subsection ~~is added~~:		After these subsections, a name subsection may follow:

	== Name ==		== Name ==
Line 3,012:		Line 3,012:
	The coordinates for this objects are taken from the ILS/VOR and adjusted, if BiasXYZ is added to the VisualModel.		The coordinates for this objects are taken from the ILS/VOR and adjusted, if BiasXYZ is added to the VisualModel.
	<br/><br/>		<br/><br/>

	= TACAN =		= TACAN =
	{{Infobox-Applicable-FSVersion		{{Infobox-Applicable-FSVersion

2023-12-20T09:13:52Z

TACAN

← Older revision		Revision as of 04:13, 20 December 2023
Line 3,062:		Line 3,062:
	\| Type. The following numbers have been found:		\| Type. The following numbers have been found:
	* bit 0: 0=X type, 1=Y type		* bit 0: 0=X type, 1=Y type
	* bit 1: 0=DmeOnly ~~true~~, 1=DmeOnly ~~false~~		* bit 1: 0=DmeOnly TRUE, 1=DmeOnly FALSE
	* bit 2-7: Unknown/Unused(0)		* bit 2-7: Unknown/Unused(0)
	\|-		\|-

2023-12-20T09:03:34Z

TACAN

← Older revision		Revision as of 04:03, 20 December 2023
Line 3,114:		Line 3,114:
	\| Name		\| Name
	\|}		\|}
			Note: By itself the TACAN record will not provide Azimuth and DME informations on standard civilian VOR/DME receivers
	<br/><br/>		<br/><br/>

2023-12-20T08:55:53Z

TACAN

← Older revision		Revision as of 03:55, 20 December 2023
Line 3,019:		Line 3,019:
	<br/>		<br/>

	The TACAN record has a 63 bytes long fixed section. An optional name ~~subrecord~~ may follow. The fixed section has the following structure:		The TACAN record has a 63 bytes long fixed section. An optional name subsection may follow. The fixed section has the following structure:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-

2023-12-20T08:54:35Z

TACAN

2023-12-20T08:53:44Z

TACAN

← Older revision		Revision as of 03:53, 20 December 2023
Line 3,019:		Line 3,019:
	<br/>		<br/>

	The TACAN record has a 63 bytes long fixed section ~~and a~~ name ~~section of variable length~~. The fixed section has the following structure:		The TACAN record has a 63 bytes long fixed section. An optional name subrecord may follow. The fixed section has the following structure:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 3,084:		Line 3,084:
	\| DWORD		\| DWORD
	\| bit 0-10 regionId		\| bit 0-10 regionId
	bit 11-31 ~~airportId (for ILS)~~		\| bit 11-31: All 0
	\|-		\|-
	\| 0x27		\| 0x27
	\| <center>24</center>		\| <center>24</center>
	\| BYTE		\| BYTE
	\| Unknown sub-record with an Id of 0x16		\| Unknown/unused sub-record with an Id of 0x16 (DME sub-record?)
	\|}		\|}
	~~The~~ name subsection ~~has~~ the following structure		A name subsection may follow with the following structure
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-