Re: [Flightgear-devel] Procedures SID/STAR/Approach

[Jonathan R <leg...@gm...>]

Yeah - you can have multiple transitions - different routes to get to a
central waypoint or VOR.

I noticed that no matter what transition you choose it never shows up in
the route manager... so that may well explain why!

Jonathan
On Saturday, November 30, 2019, Sascha Reißner <rei...@no...> wrote:

> Hi developers,
>
> i'm playing around with procedures.xml and found some weird things.
>
> The procedures are handled by '/flightgear/src/Navaids/LevelDXML.cxx'.
> In this file 'StarTr_Waypoint' will be evaluated in the function
> 'NavdataVisitor::endElement', but not in 'NavdataVisitor::startElement'.
> So i think Star Transitions will be left out from the code.
>
> The description in the wiki[1] shows what can be written in a procedure
> file, but no explanations.
> The tag 'Type' has no explanation. I found it in the source code and it
> can be one of "Normal", "Runway", "Hold", "Vectors", "Intc",
> "VorRadialIntc", "DmeIntc", "ConstHdgtoAlt", "PBD".
> Some types are clear for me, but others not.
> What means 'PBD'? 'Intc' stay for 'Interception', but intercept what???
> What tags need every type and what tags are optional?
>
> Tags:
> 'Latitude' and 'Longitude' is clear, but it should also noted that this
> value must be a floating point digit.
> 'Speed' (floating point value) is allways in knots.
> 'Altitude' (floating point value) is allways in feets.
> 'AltitudeCons' means what? what value can it have?
> 'Hdg_Crs (optional. example value = "1")'
> What does that mean? what means '1'? what other values are possible?
> I reckon 0 = true heading and 1 = magnetic heading, but how knows?
> 'Sp_Turn (optional. example value = "Auto")'
> I think this should be the turn direction (Left/Right) but i dont know.
> And there are other types that are not written down in the example.
> 'BankLimit' is minimum bank to accomplish the turn in that procedure (i
> think).
> 'Hld_Time_or_Dist' (default : "Time") change the holding length from
> 'Time' (in minutes) to 'Dist' (in nautical miles).
> 'Hld_td_value' (floating point value) set the length of the holding
> pattern in minutes or nautical miles (depending on 'Hld_Time_or_Dist').
> 'Hld_Rad_value' (floating point value) the inbound radial of the
> holding pattern.
> 'Hld_Turn' (default: "Left") set the holding pattern side ("Left" or
> "Right").
> 'Flytype' (default: "Fly-by") set how the waypoint should be used
> ("Fly-by" or "Fly-over").
> 'RadialtoIntercept' and 'DMEtoIntercept' (floating point value).
> I think the first is for type 'VorRadialIntc' and the second for
> 'DmeIntc'. But i don't know what tags this types are must have and what
> can they have.
>
> In the syntax example we found:
> 'Star_Transition [Name] (just one of these per Star)'
> But if we look in the example file below, there are STARs with more
> than one transitions. Whats correct?
> Can we have more than one transitions or not?
>
> And there are some tags that the code doesn't evaluate:
> AltitudeCons, BankLimit, Sp_Turn, Airport (???), ProceduresDB.
>
> It will be nice if 'Sp_Turn' and 'BankLimit' are evaluate,
> because i try to built procedures and the radius in the FG map are too
> small and the route manager turn in the wrong direction if the next
> point is located in the previous leg for missed approach (tear drop).
> I think the radius can be calculated out of speed and bank.
>
> Will be nice if someone finish or at least repair this code.
>
> [1] http://wiki.flightgear.org/Howto:Adding_procedures_to_
> the_route_manager
>
> --
> best regards
> Sascha
>
> GPG fingerprint: 5A68 F665 44E6 0E50 001C 75A6 92BB DD59 6C5F DC0F
> GPG key: https://pgp.mit.edu/pks/lookup?search=
> 0x92BBDD596C5FDC0F&op=vindex&fingerprint=on&exact=on
>