FSNav export for extended coordinates

Problems? Bugs found? Questions? Please post here.

Moderator: Michal Rok

Post Reply
Kyprianos Biris
Five Star Club
Posts: 37
Joined: Sun Sep 21, 2008 5:17 am

FSNav export for extended coordinates

Post by Kyprianos Biris » Fri Aug 10, 2012 5:43 pm

EGLL KJFK
CPT UL179 INLAK UL607 ABDUK UL180 LESLU 5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W 4610N05300W 4414N06000W 4246N06500W 4200N06700W KENDA LINND 3920N07200W OWENZ CAMRN JFK

For the above custom for Concorde Flight Plan (saved in private routes due to Eurocontrol validation rejection) any waypoint defined by the extended type of coordinates (whatever they're called) like 5041N01500W is not being recognized in the .fsn file for FSNavigator. Actually it must be generated but not recognized by FSNav because on loading it I got a message "9 waypoints not recognized" or something similar.

The 4200N06700W was recognized as 4267N and hence the 9 instead of 10 waypoints report.

Is there anything that can be done about it :?:

User avatar
Michal Rok
Five Star Club
Posts: 2445
Joined: Wed Aug 31, 2005 4:23 pm

Re: FSNav export for extended coordinates

Post by Michal Rok » Fri Aug 10, 2012 7:19 pm

Kyp,

the long waypoint format was introduced because people could not code all coordinates if they only had 1-degree precision. While you can convert 4200N06700W to 4267N, you will not be able to do the same with 4916N04000W so your flight is doomed anyway...


Michal

Kyprianos Biris
Five Star Club
Posts: 37
Joined: Sun Sep 21, 2008 5:17 am

Re: FSNav export for extended coordinates

Post by Kyprianos Biris » Sun Aug 12, 2012 7:49 pm

Thanks

Understood :)

Post Reply