[FEAT REQ.] - No FAA Generated Computer Codes Limit

[Nikolai558]

Is your feature request related to a problem? Please describe. I wonder if we can come up with a way to properly generate STARs and DPs that do not have a computer code associated with it. Reference the code below. Document Link

                string currentComputerCode;

                if (procedures[procKey][0].ComputerCode.IndexOf("NOT ASSIGNED") != -1)
                {
                    continue;
                }
                else if (procedures[procKey][0].Type == "S")
                {
                    currentComputerCode = procedures[procKey][0].ComputerCode.Split('.')[1].Substring(0, procedures[procKey][0].ComputerCode.Split('.')[1].Length - 1);
                }
                else if (procedures[procKey][0].Type == "D")
                {
                    currentComputerCode = procedures[procKey][0].ComputerCode.Split('.')[0].Substring(0, procedures[procKey][0].ComputerCode.Split('.')[0].Length - 1);
                }
                else
                {
                    throw new NotImplementedException();
                }

Describe the solution you'd like I'm not sure if this is possible but it is worth a second look.

Additional context Procedures:

Spokane Six (GEG6)
Blue Lake 3

[Nikolai558]

Idea Option 1)

"Creating a code" if it is is not "FAA Assigned"

For instance Spokane Six

NASR 2 SCT Knows that it does not have an assigned computer code. ( So that's simple to create one) I would create it by the "Point ID" So the above link would be .GEGGEGC (if multiple pages) .GEGGEG2C It also knows the Full URL for it already (we just don't print it to the alias file because there is no specified format for the command)

Issues I potentially see with this idea:

• If there are any Procedures like .SLCSLCC that do not have a computer code, you will end up with duplicate commands. (I am not sure if this is a thing) If it does cause a duplicate command this should be reflected in the "DuplicateCommands.TXT" output file.
• This should only effect the Alias command. I still won't be able to draw that procedure on the scope or do the fixes command for it. It would be a temporary "Created Code" only for Alias Commands (Unless we want to try it for ALL commands, I.E. Fixes, Drawing, etc.)

[Nikolai558]

Option 1 does allow the commands to be completed, however there are about 90 of them that are duplicates and overlap. Also, there are about 90 of them that are for Airforce Bases. This brings the question do I "forget" about the Airforce Bases and come up with a syntax for the 90 ish ones that are for Civilian Airports?

I found out how Jeppeson Charts accounts for this. http://www.jeppesen.com/download/briefbull/fra00-f.pdf.

Would the solution that Jeppeson Charts uses be enough of a "Syntax" that people would know and understand how its put together?

• Take the first 5 Characters (if length >=5) of the name of the chart???
• If length is less than 5 do all the the characters
• If multiple words, combine up to 5 characters.

Examples:

• ANC - KNIK 3: Command = .ANC KNIK C
• TCM - OLYMPIC 4: Command = .TMC OLYMP C
• WRI - POINT PLEASENT 5: Command = .WRI POINT C
• NTD - SAN MARCUS 1: Command = .NTD SANMA C

[Nikolai558]

Added Version 0.8.1

Will now create commands for charts even when there is no FAA Computer Code. There are minimal duplicate commands created due to this. Format for these procedures are first 5 characters of the chart name not including any spaces. (see examples below) Example: TNX - DP - TUMBE ONE would be .TMXTUMBEC Example: GTB - DP - WATERTOWN TWO would be .GTBWATERC Example: TTD - DP - BLUE LAKE THREE would be .TDDBLUELC