- Messages
- 608
- Country
Even if the approach editor obviously contains some surprises for at least some people (like me) when it comes to more complicated procedures the results could be helpful to fill other gaps. In some cases it it could help e.g. to get a sort of framework for defining approaches for PMDG products (to give one example).
What ADE knows:
It's not a request to get the right format as long as Lat/Lon and other values would take the selected settings. Of course it would be sufficient to extend (optionally?) the existing list -> export function to *.csv or, alternatively, to have an option exporting to XML the comprehensive list of the Raw Data View, including even the non-compiled stock data (like waypoints).
What do you think?
What ADE knows:
- Fixes:
- Terminal waypoints (name and Lat/Lon)
- Named waypoints (name and Lat/Lon)
- Unnamed waypoints (name and Lat/Lon)
- Runways
- Just the names (for other products even the runway starting points, the heading and the length could be useful)
- Approaches
- Type
- Transitions (including the related STARS and Missed Approaches as far as I can see)
- Type
It's not a request to get the right format as long as Lat/Lon and other values would take the selected settings. Of course it would be sufficient to extend (optionally?) the existing list -> export function to *.csv or, alternatively, to have an option exporting to XML the comprehensive list of the Raw Data View, including even the non-compiled stock data (like waypoints).
What do you think?