Welcome to TechNet Blogs Sign in | Join | Help
GPS detail level enumerations

In the XPack SDK we added more documentation about the enumerations relating to the GPS, but it looks like we left out some, too.  Some people were investigating what each meant based on trial and error, but I think I can help out a bit here.

For example, Geoff_D was wondering what these numbers meant from the gps_500.xml:

<CustomDrawParam id="ObjectDetailLayerAirports" Name="ObjectDetailLayerAirports"> 
<Value>0 0 0 0 0 0 0x5 0x5 0x7 0x7 0x1F 0x1F 0x1F 0x1F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 24 (@g:map_ZoomStep) case</Value>  

So here's a quick runthrough that I just put together of what the numbers that you're scratching your head about mean:

·         Detail level enumerations

o        Airport

§         Dot = 1

§         Circle = 2

§         Circle and runways = 3

§         Block runways = 4

§         Airport runways = 5

o        Vor

§         Dot = 1

§         Symbol  = 2

o        NDB

§         Dot = 1

§         Symbol = 2

o        Airway

§         Thin lines = 1

§         Thick lines = 2

o        Terrain

§         Water only = 1

§         Color = 2

o        Approach

§         Approach = 1

§         Approach missed = 2

§         Approach arrow head = 4

o        Flight plan

§         Solid line = 1

§         Dashed line = 2

o        Vehicles

§         ATC symbol = 1

§         TCAS symbol = 2

§         Realistic symbol = 3

 

·         Text detail level

o        Airport

§         ICAO = 1

§         Name = 2

§         Name and elevation = 3

§         Name, elevation, and frequencies = 4

§         Runways = 5

o        Vor

§         ID = 1

§         ID and frequency = 2

§         ID and morse code = 3

o        ILS

§         ID = 1

§         ID and frequency = 2

§         ID and morse code = 3

o        NDB

§         ID = 1

§         ID and frequency = 2

§         ID and morse = 3

o        Vehicles

§         Realistic = 1

§         Detailed = 2

·         Object detail level (flags and can be combined)

o        Airport

§         Towered = 0x1

§         Not towered = 0x2

§         Hard runway = 0x4

§         Soft runway = 0x8

§         Water = 0x10

§         Heliports = 0x20

§         Private = 0x40

o        VOR

§         VOR = 0x1

§         VOT = 0x2

o        Marker

§         Outer marker = 0x1

§         Middle = 0x2

§         Inner = 0x4

§         Backcourse = 0x8

o        Geopolitical

§         Coastline = 0x1

§         Boundary = 0x2

o        Airway

§         Victor = 0x1

§         Jet = 0x2

o        Flight plan

§         Enroute = 0x1

§         Approach = 0x2

§         Missed approach = 0x4

§         Waypoints = 0x8

o        Vehicles

§         Track line = 0x1

§         Ground vehicles = 0x2

§         Airborne vehicles = 0x4

§         Racing vehicles = 0x8

o        ILS

§         Cone = 0x1

§         Line = 0x2

 

So, to go back to Geoff_D's question:

<CustomDrawParam id="ObjectDetailLayerAirports" Name="ObjectDetailLayerAirports"> 
<Value>0 0 0 0 0 0 0x5 0x5 0x7 0x7 0x1F 0x1F 0x1F 0x1F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 0x4F 24 (@g:map_ZoomStep) case</Value>  

0x5 = 0x1 | 0x4 =  Towered and hard-runwayed airports
0x7 = 0x1 | 0x2 | 0x4 = Towered, untowered, and hard-runwayed airports.
0x1F = 0x1 | 0x2 | 0x4 | 0x8 | 0x10 = Towered, untowered, hard-runwayed, soft-runwayed, and water-based airports

and so forth...

In other words, the map is showing more and more airports as the user zooms in on the map (based on the value of @g:map_ZoomStep).

Thanks to Geoff_D for the question.

Posted: Wednesday, November 14, 2007 6:46 PM by EnGauged

Comments

Nick Pike said:

Thank you Susan, very useful. Please keep this sort of info coming.

Did you ever finish that GPS variables .doc document on enums and there meaning, although this seems to be covered in the SDK now (or are there any missing from the SDK)?

I like the .chm file format used in the SDK. However, there is no search facility. Be handy to add one.

I right click and search through 'view source'.

And what kind of chocolates do you like???

cheers,

nick

# November 17, 2007 3:53 PM

Nick Pike said:

Erm, I meant 'their' and not 'there'.

# November 17, 2007 10:37 PM

EnGauged said:

Actually, there is a Search facility in the SDK in the final version that we shipped for Acceleration (though not in the earlier betas).

The GPS variables documentation that I began in my blog (GPS variables) was rolled into the SDK, as has happened with a few other areas (XML gauges in general).

I'll try to keep the useful information flowing...

I like dark chocolate.  :)

# November 19, 2007 8:09 PM

Nick Pike said:

Hi Susan,

I updated to Xpack SDK RTM but still cannot find the search facility. I see the Search tab but that only lists the articles. You still have to wade through the artical to find the required info? Please advise.

cheers.

# November 22, 2007 5:30 PM

benicar said:

Your site is very interesting and useful

# February 22, 2008 7:02 AM

xmlnoob said:

Are those values works on FS9 too?

I'm currently wondering how to show the flightplan waypoint names on the gps while other nav aids are set not to show....

Thank you.

# April 22, 2008 1:34 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker