Fixes #4822 - Update all incorrect fixes for airport RNAV sids / RNAV approaches

[AliceFord]

Fixes #4822

Summary of changes

• Coordinates updated (correct as of 2308)

Screenshots (if necessary)

[AliceFord]

AD2 fix parser has been added, it currently does not use the AIRAC class as adding it is going to start getting messy with all the different PRs. After this commit is pushed as well as #4817, I'll update all the tooling on a separate PR.

[PLM1995]

Changes all accurate.

[PLM1995]

I assume you're going to want to refactor this once the other tooling stuff is included? If so lets put this PR 'on hold' or 'draft' until ready :)

[AliceFord]

I was going to update the tooling in a different PR, as here I don't have access to the other classes. Either removing the AD2 parser from here or just pushing like it is now and then updating it later would work, but not pushing this one would leave me in a trap of not being able to get the backend code and would delay way longer :)

[PLM1995]

OK so you want me to merge this now? With or without the parser? Whatever's easier for you.

I thought it was #4817 you needed first, then update this using that stuff, but maybe I'm getting confused!

[AliceFord]

Yep you're right with that, I'll just explain fully here:
What I want to do is create a tooling system that uses a framework for parsing the eAIP (an API). This framework would have backend functions and other files and code that would be general across all parsers, not specific. If I were to update the tooling in each PR individually, I would have to duplicate these backend functions across every PR, which would a. cause lots of conflicts and b. if there were any changes requested of the backend functions, I would have to make those changes across all the different PRs which would take ages and be super inefficient.

So, to summarise, I don't mind whether you keep the parser here or not, its getting replaced soon anyway.

[PLM1995]

Yeah, OK, so what I had in mind was wait until those backend things are in place and introduce the new tooling with these PRs that use tooling. We have over 2.5 weeks to the next release, so we're not particularly in a rush to merge the actual changes to our Fixes.txt files. I was thinking get it right first time / in one PR rather than rushing to merge it peicemeal.

Of course if you want to get them merged now that's fine, and do all the tooling separately, if that's easier for you. In that case I personally wouldn't bother including the parser that's soon to be removed/replaced/refactored, unless you need it.

[AliceFord]

Cool, I've taken out the parser (I have a local copy), I'll update it all in a different PR, just have to wait for either #4817 to be merged or I'll also remove the parser from there and just stick it all on one now.