Tom Stian Posted May 26, 2016 Report Share Posted May 26, 2016 Hello POL5R (rwy23R) at EGCC have some wierd drawing. Route: EGCC POL1R POL UP17 TIPTA UM82 NIVUN M82 UNBUD UNBU2V ENHD Navigraph Cycle 1605 Should look more like this Quote Link to comment Share on other sites More sharing options...
Litjan Posted May 26, 2016 Report Share Posted May 26, 2016 Thanks, Tom! Jan Quote Link to comment Share on other sites More sharing options...
tkyler Posted June 9, 2016 Report Share Posted June 9, 2016 *Sigh...I have never seen this one before. There is a waypoint of type "Runway" in the Sid departure procedure. My code doesn't even attempt to handle these becasue it never expected them. It should not be there period. I am wondering if this will be a constant struggle with the nav data...always watching out for "abnormal stuff" and having to code around it. I am wondering if we should try to code around it, or contact the provider for "fixing"? If I simply open the XML and delete the offending waypoint altogether then this is what I get......and probably a lot closer to what you want Tom -tkyler Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 9, 2016 Author Report Share Posted June 9, 2016 (edited) 1 hour ago, tkyler said: I am wondering if we should try to code around it, or contact the provider for "fixing"? If I simply open the XML and delete the offending waypoint altogether then this is what I get......and probably a lot closer to what you want Tom -tkyler Does Aerosoft have this also ? Maybe both, contact the provider and get it fixed, and code a rutine, for failsafe, that remove ID="1" from a SID if the type is runway. If it is so simple <Sid Name="POL5R" Runways="23R"> <Sid_Waypoint ID="1"> <Name>RW23R</Name> <Type>Runway</Type> <Latitude>53.361319</Latitude> <Longitude>-2.259281</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Sid_Waypoint> <Sid_Waypoint ID="2"> <Name>MCT</Name> <Type>DmeIntc</Type> <Latitude>53.357025</Latitude> <Longitude>-2.262289</Longitude> <Speed>0</Speed> <Altitude>760</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>233</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <DMEtoIntercept>3.0</DMEtoIntercept> <Sp_Turn>Auto</Sp_Turn> </Sid_Waypoint> Edited June 9, 2016 by Tom Stian Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 9, 2016 Author Report Share Posted June 9, 2016 (edited) Did a content search in all files in SidStar folder. And got 219 hits in 41 files when searching for <Sid_Waypoint ID="1">\r\n <Name>RW I havent quality checked this result. The search requires that the next line after <Sid_Waypoint ID="1"> have 8 blank spaces before <Name> So its 41 airports that have "runway" as the first waypoint in the SID, of the 6805. So I guess I was "lucky" that found one of them ^^ Edited June 9, 2016 by Tom Stian Quote Link to comment Share on other sites More sharing options...
Tchou Posted June 9, 2016 Report Share Posted June 9, 2016 maybe it's to specify that this SID is Exclusive to that Runway… Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 9, 2016 Author Report Share Posted June 9, 2016 (edited) 8 minutes ago, Tchou said: maybe it's to specify that this SID is Exclusive to that Runway… I think that is specified by the <Sid Name="POL5R" Runways="23R"> From KJFK <Sid Name="HAPIE4" Runways="All"> Edited June 9, 2016 by Tom Stian Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 22, 2016 Author Report Share Posted June 22, 2016 (edited) Hi I dont know your progress on this, maybe it is solved. But I checked Navigraph cycle 1607, and there is only one airport that have changed (DTTF) from cycle 1606, concerning the runway as first waypoint. Cycle 1607 The difference on one SID at DTTF. Cycle1606 Cycle 1607 Edited June 22, 2016 by Tom Stian Quote Link to comment Share on other sites More sharing options...
63 Degrees Right Posted June 25, 2016 Report Share Posted June 25, 2016 The solution is coming: https://www.navigraph.com/forum/viewtopic.php?f=30&t=3586&p=15451#p15451 1 Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 25, 2016 Author Report Share Posted June 25, 2016 Good job. :=) Quote Link to comment Share on other sites More sharing options...
Rodeo Posted June 25, 2016 Report Share Posted June 25, 2016 That's only for Navigraph. I know Aerosoft includes many legs of the type "fix to an altitude" in their data for the X-Plane GNS430 GPS (e.g. LSGG SID procedures); not sure about their IXEG data. That being said, "fix to <something>" where the first fix is the runway threshold is really not much different than a "course to <same something as before>" and the legs should contain enough information to magically convert it internally should the IXEG code require it. Quote Link to comment Share on other sites More sharing options...
Rodeo Posted June 25, 2016 Report Share Posted June 25, 2016 I guess Aerosoft doesn't include "fix to <something>" as the first leg of a SID procedure in the IXEG database, only the GNS430 (Airbus X Extended) one. Quote Link to comment Share on other sites More sharing options...
Rodeo Posted June 25, 2016 Report Share Posted June 25, 2016 I guess the issue here was simply that the format used by IXEG could represent "fix to <something>" so the runway threshold was incorrectly included as a normal waypoint instead… Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 26, 2016 Author Report Share Posted June 26, 2016 Rev2 is out of the FMC data. The are still some airports that have the runway as first waypoint, but its reduced. Quote Link to comment Share on other sites More sharing options...
Tom Stian Posted June 26, 2016 Author Report Share Posted June 26, 2016 Its acually only 2 airports that have this issue now with rev2 of cycle 1607. KASE and LEDA. And they will be fixed in next cycle. Quote Link to comment Share on other sites More sharing options...
.thumb.jpg.ede78836fe6795baf7b91e5eb2aad35e.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.