Hi Arno,
It appears there are 3 truths here:
1 what is written in the SDK
2 what is specified in the bglcomp.xsd
3 what Microsoft/ACES are using
1: SDK
Tower: This element is used to place a tower location at an airport. This element is not allowed to contain other data (lat/lon/alt) and must be terminated with ‘/>’.
2: bglcomp.xsd:
Code:
<xs:complexType name="ctTower">
<xs:sequence>
<xs:element name="SceneryObject" type="ctSceneryObject" minOccurs="0" maxOccurs="1" />
</xs:sequence>
<xs:attribute name="lat" form="unqualified" type="stLatitude" use="optional" />
<xs:attribute name="lon" form="unqualified" type="stLongitude" use="optional" />
<xs:attribute name="alt" form="unqualified" type="stAltitude" use="optional" />
</xs:complexType>
3: Reversing the MS bgl's reveals multiple Tower objects in several airports, while bgclcomp.xsd specifies maxOccurs=1:
Code:
<xs:group name="grpAirportChildren">
<xs:choice>
<xs:element name="Tower" type="ctTower" minOccurs="0" maxOccurs="1" />
As you can see in my previous post, the first tower tag for EHAM contains an object and this is the main tower, yet the coordinates for the tower itself (not the libraryobject) are those of the satellite tower near the Polderbaan.
Daniel