Miguel Frias Posted December 27, 2011 at 10:02 AM Posted December 27, 2011 at 10:02 AM This is actually a request for a future ES version. For oceanic controlling it's important that Euroscope can interpret oceanic positions. Not all formats are recognized by Euroscope. To what I've seen in flight plans all of these need to be recognized: Latitude: 31 Longitude: -50 31N050W 3150N 3100N05000W 3100N05000W N31W050 Miguel Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Gergely Csernak Posted January 13, 2012 at 10:51 AM Posted January 13, 2012 at 10:51 AM Miguel, Some of them are segistered in the TODO list. I will extend that list with yours and check the possibilities. The one with space more or less surely will not be implemented and the space is a separator in the route itself. Gergely. EuroScope developer Link to comment Share on other sites More sharing options...
Miguel Frias Posted January 13, 2012 at 11:12 AM Author Posted January 13, 2012 at 11:12 AM I know. I did an oceanic controller [Mod - Happy Thoughts]istant for our airspace and had to normalize the routes. I had to do a special regexp search in order to replace these types of coordinates: IF ([0-9]{4,4})(N|S)(\s+)([0-9]{5,5})(W|E) THEN # p[Mod - Happy Thoughts] and correct format, eg: 3800N 04000W to 3840N Miguel Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Recommended Posts