Openscope: Add "Airport File Standards" document

Created on 24 Apr 2017  路  6Comments  路  Source: openscope/openscope

This should outline a few different things for airport file development:

  1. Content Requirements

    • terrain

    • polygonal airspace boundary

    • airways

    • ALL supported procedures

    • accurate traffic level (and info to back it up)

    • base video map

  2. Requirements for "Premium (?) Airport" Designation

    • full documentation on facility's airspace

    • airspace and traffic flow diagrams

    • exceptionally high realism (subjective to local knowledge)

  3. Style Requirements

    • on spacing, bracket newlines, key order, etc

documentation

Most helpful comment

yeah airport-format.md would be explanations of how everything works, what it means, what it needs to work. This new file would be the requirements as far as quality control. If the airport does not meet these requirements, it will require extra work before being merged.

We're approaching the point where there is _more_ than enough variety available, and we need to begin focusing on increasing the quality of each, rather than the quantity of airports available. But knowing what can be improved for a given airport is a lot easier if we have a checklist of things that can elevate it to "premium" level (the next purpose for those little flags in the load list).

All 6 comments

how does this differ than openscope/openscope#184? Couldn't most of this in that document? Or do you envision this as a companion document with more specific, detailed information?

In my opinion it'd be better to separate it. It's easier to see a checklist of what should be done rather than going through a large document just to check what needs to be done.

totally cool. I just wanted to call that out. We can always cross reference the two docs.

yeah airport-format.md would be explanations of how everything works, what it means, what it needs to work. This new file would be the requirements as far as quality control. If the airport does not meet these requirements, it will require extra work before being merged.

We're approaching the point where there is _more_ than enough variety available, and we need to begin focusing on increasing the quality of each, rather than the quantity of airports available. But knowing what can be improved for a given airport is a lot easier if we have a checklist of things that can elevate it to "premium" level (the next purpose for those little flags in the load list).

perhaps I should wait till this is finished until I start #94 so that I can write that to follow this doc?

@n8rzz Probably. If it weren't for the fact that we've already delayed everybody's airports updates for months, I'd want to implement #47 first as well, since it will require yet another massive airport rework. But we'll just have to cross that bridge when we come to it. :smiley:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

panther2 picture panther2  路  3Comments

panther2 picture panther2  路  6Comments

artur-gajewski picture artur-gajewski  路  4Comments

tdawe picture tdawe  路  3Comments

felixscheffer picture felixscheffer  路  7Comments