Each file will contain the respective fixes/navaid symbols and text associated with that airways.
Example image for part of V32:
Note: The two txt files attached are what makes this image. GitHub will not accept a .xml upload so just rename the extension to .xml
Line defaults per file:
AWY_HI_GEOMAP_FIXES-TEXT.xml
For simplicity and until more development time can be dedicated to this feature, Style="OtherWaypoints" will be used even for NAVAIDs.
Even though the example shows only one airways being completed, this will need to be all inclusive of all airways in the respective HI/LO categories.
When coding, keep in mind that the same fix/navaid can be used multiple times by different airways, so a scan for "duplicates" will be required.
Note the "SYMBOLS" file has "remarks" next to each line to indicate which waypoint it is to help with debugging.
For ease of coding, refer to the NAVAID_GEOMAP.xml and NAVAID_TEXT_GEOMAP.xml output code, as it is pretty much the same thing with the exception of the element defaults as described above.
Requesting 4 additional GeoMap files:
AWY_HI_GEOMAP_FIXES-TEXT.xml AWY_HI_GEOMAP_FIXES-SYMBOLS.xml AWY_LO_GEOMAP_FIXES-TEXT.xml AWY_LO_GEOMAP_FIXES-SYMBOLS.xml
These files will eventually be GeoJSON as well.
Each file will contain the respective fixes/navaid symbols and text associated with that airways.
Example image for part of V32: Note: The two txt files attached are what makes this image. GitHub will not accept a .xml upload so just rename the extension to .xml
Line defaults per file: AWY_HI_GEOMAP_FIXES-TEXT.xml
AWY_HI_GEOMAP_FIXES-SYMBOLS.xml
AWY_LO_GEOMAP_FIXES-TEXT.xml
AWY_LO_GEOMAP_FIXES-SYMBOLS.xml
NOTES:
Style="OtherWaypoints"
will be used even for NAVAIDs.AWY_LO_GEOMAP_FIXES-TEXT.txt AWY_LO_GEOMAP_FIXES-SYMBOLS.txt