For example suing route from:
KAVL to KACY
VIEWS COLZI FAK237020 FAK BUKYY JAYBO SIE
In both X-Plane format variants, the place/bearing/distance waypoint is coded as follows:
11 FAK237020 39000 37.300509 -78.134912
11 FAK237020 DRCT 39000.000000 37.300509 -78.134912
Going by the specification at: Flightplan files - v11 .fms file format - X-Plane Developer
Row/line code 11 corresponds to a named fix, which it isn’t.
Since this seemingly hasn’t been brought up until now, I suspect It’s possible X-Plane’s default avionics will gracefully fall back to using the latitude/longitude coordinates, but the waypoint should ideally be coded as per the specification (presumably as a latitude/longitude waypoint with row/line code 28, since there is no specific code or other facility in the format to allow for composite waypoint definitions), so that it can be parsed by third-party software which may adhere more strictly to the published specification
As a side note, the route_navigraph in the XML/JSON data is as follows:
DCT VIEWS DCT COLZI DCT FAK237020 DCT FAK DCT BUKYY DCT JAYBO DCT SIE DCT
…which Navigraph Charts cannot parse fully (gives an error relating to the place/bearing/distance waypoint too, and there is a “discontinuity” on the map in the application). It should probably be converted to a latitude/longitude for that field as well, provided Navigraph Charts does have some form of support for such waypoints?
Regards,
Tim