If you want to play with coding, at least be aware the syntax of the information in the database.
Public procedures, as you know, use 5 letters for waypoints that are pronouncable.
CNF waypoints used for FMS calcs, as 5 letters, all consonants, that cannot be pronounced. (although I have to wonder how some of the waypoints can be pronounced.
With coded procedures, such as RNP, there is now some reasoning to the naming convention. It is typical now to use the last 2 letters of the ICAO airport code as the first 2 letters of the waypoint, unless that is already used, then its the first 2 of the code or negotiated.
The IF will be a standard 5 letter pronounceable waypoint, but since the procedure waypoints are not announced over the radio, they do not need to be pronounced, so you will see XX123.
Now, the numbering, needs to be descending on the approach and increasing with the missed.
As an example YMML, would be ML600(VIP), ML598, ML596, ML594(FAF), ML300, ML302, ML304(HOLD)
Other than that, the numbering is up to the designer, and the navdatabase supplier to sort out....
I know, much to do about nothing, but that is how coding works....
Last edited by FlightPathOBN; 9th Jul 2012 at 20:46.