Josh Glottmann Posted February 28, 2016 at 05:22 PM Posted February 28, 2016 at 05:22 PM In displaying the route of some aircraft, I've noticed their routes occasionally appear for lack of better words. AR23 URSUS UA301 UCA UG437 GONIS UL341 KIRAN appears as this. My issue here is the UCA happens to also be the name of a VOR in New York. This issue occurs relatively frequently with routings that p[Mod - Happy Thoughts] through Havana's airspace.What might be a good 'solution' to this problem would be to allow for some kind of exceptions list which would override waypoints in the Waypoints.xml file. In that file, foreign fixes (that would not be regularly included in Waypoints.xml), could be included as well. Another issue I've been facing is with routes that have specific aiways that are the same name as airports. The biggest occurrence of this I've noticed is with AR22. It feeds to one of Miami's main northern STARs and is also the identifier of Tommy's Flying Service Inc Airport. My proposed solution for this would be to ignore airport names in IFR routes which include more than X different waypoints. Odds are, most people don't use an airport as an actual waypoint too often. In the case of AR22, the airport would be ignored and it would be treated as an airway. Link to comment Share on other sites More sharing options...
Dhruv Kalra Posted February 28, 2016 at 11:07 PM Posted February 28, 2016 at 11:07 PM At present, the logic doesn't p[Mod - Happy Thoughts] airways at all. Dhruv Kalra VATUSA ZMP ATM | Instructor | VATSIM Network Supervisor Link to comment Share on other sites More sharing options...
Josh Glottmann Posted February 28, 2016 at 11:32 PM Author Posted February 28, 2016 at 11:32 PM At present, the logic doesn't p[Mod - Happy Thoughts] airways at all. I realized that, but it is parsing some of them as airports instead of nothing, creating oddly shaped routes. Link to comment Share on other sites More sharing options...
Recommended Posts