*Created by: svoop* :warning: See related issue ofmx#6 as well. --- ## General ### Document Upload * [x] 🇫🇷 Add support to upload AIP documents as HTML. * [x] 🇫🇷 Currently, each uploaded AIP document gets a autoincrement revision number (e.g. `3`) assigned which is used to reference the specific document.<br>&emsp;To decouple this, the revision number will be replaced with the AIRAC cycle date: When uploading an AIP document, you select which AIRAC cycle date the document belongs to. A selection between the current cycle date and the upcoming cycle date (default) should be sufficient (see anim GIF below), the selectable cycle dates can be [calculated from the current date](https://github.com/svoop/aipp/blob/master/lib/aipp/airac.rb#L36). Uploading the same document to the same cycle date will overwrite the document on the server.<br>&emsp;The AIRAC cycle date will then be used to reference documents in [<span>`@source`</span>](/openflightmaps/ofmx/wikis/Features#source) attributes of features in OFMX.  ### All Features * [x] 🇫🇷 All `*Uid`s must be globally unique. * [x] 🇫🇷 Tags (components/properties) have to occur in the specified order for the OFMX document to be valid. * [x] 🇫🇷 Implement [<span>`@region`</span>](/openflightmaps/ofmx/wikis/Features#region) and [<span>`@source`</span>](/openflightmaps/ofmx/wikis/Features#source) attributes * [x] 🇫🇷 Remove `@newEntity` attributes ### [<span>`AIXM-Snapshot`</span>](/openflightmaps/ofmx/wikis/Snapshot) * [x] 🇫🇷 The root element has to be renamed from `AIXM-Snapshot` to `OFMX-Snapshot`. * [x] 🇫🇷 Add support for [<span>`@namespace`</span>](/openflightmaps/ofmx/wikis/Snapshot#namespace) * [x] 🇫🇷 The arguments on the root element have to be [as specified here](/openflightmaps/ofmx/wikis/Snapshot). * [ ] The attributes `created`, `effective` and `expiration` are [datetimes](https://gitlab.com/openflightmaps/ofmx/-/wikis/Dates-and-Times#datetime) have to be UTC and therefore expressed with a tailing `Z` or `+00:00`. ### [<span>`TIMSH`</span>](/openflightmaps/ofmx/wikis/Timetable#timsh-timesheet) * [x] 🇫🇷 Times must be coded as `20:15` instead of `2015`. * [x] 🇫🇷 `xt_AlignSummerSavingT` is obsolete. This information has to be coded into `codeTimeRef` on the same level. ## Label Marker ### [<ins>`Lbm`</ins>](/openflightmaps/ofmx/wikis/Label-Marker#lbm-label-marker) * [x] Move and rename attribute `LbmUid@fir` to `LbmUid@region`. * [x] Rename `Lbz` to `ZoomLevel`. * [x] Rename `zoomLevel` to `valZoomLevel`. * [x] Remove `codeDatum` underneath `ZoomLevel`. The zoom level positions inherit the datum from the main `Lbm->codeDatum` property. ## Airport ### [<ins>`Ahp`</ins>](/openflightmaps/ofmx/wikis/Airport#rwy-runway) * [x] 🇫🇷 `xt_TypeOfTraffic`, `xt_TypeOfUsage` and `xt_TypeOfAircraft` have to be coded with `Ahu`. * [x] 🇫🇷 `xt_TypesOfFuel` has to be coded with `Ful`. * [x] `xt_lighting` has to be coded with `Rls`. * [x] `xt_GpsIdent` has to be renamed to `codeGps`. * [x] 🇫🇷 `xt_addFreq` has to be coded with `Aha->codeType=RADIO`. * [x] `xt_txtUrl` has to be coded with `Ahs->codeType=INFO` and `Aga->codeType=URL`. * [x] `xt_txtPhone` has to be coded with `Ahs->codeType=INFO` and `Aga->codeType=PHONE`. * [x] `xt_txtMetPhone` has to be coded with `Ahs->codeType=INFO` and `Aga->codeType=PHONE-MET`. * [x] Some airports or clubs on airfields have a weather briefing webpage, you might want to add `Ahs->codeType=INFO` and `Aga->codeType=URL-MET` for those. * [x] `xt_urlWebcam` has to be coded with `Ahs->codeType=INFO` and `Aga->codeType=URL-CAM`. * [x] `xt_email` has to be coded with `Ahs->codeType=INFO` and `Aga->codeType=EMAIL`. * [x] `xt_CustomsAvail` has to be coded with `Ahs->codeType=CUST`. * [x] `xt_TypeOfTraffic->Ppr` has to be coded with `Ahu->codeUsageLimitation=RESERV`. The contact details `xt_TypeOfTraffic->xt_PPR_txtContact`, `xt_TypeOfTraffic->xt_PPR_txtEmail` and `xt_TypeOfTraffic->xt_PPR_txtPhone` should go to `Ahu->UsageLimitation->txtRmk` ([see example](/openflightmaps/ofmx/wikis/Airport#ahu-airport-usage)) * [x] `xt_contactPractice` should be coded with `Ahs->codeType=INFO` and `Aga->noSeq=1` ([see example](/openflightmaps/ofmx/wikis/Airport#aga-airport-ground-service-address)) ### [<span>`Rwy`</span>](/openflightmaps/ofmx/wikis/Airport#rwy-runway) * [x] 🇫🇷 `xt_status` has to be coded with `codeSts`. The value `CLSD` remains, however, `IN OPS` does not exists, omit the entire tag to indicate normal operations. * [x] 🇫🇷 Add `Rwy->codePreparation` * [x] Add `Rwy->codeCondSfc` ### [<span>`Rdn`</span>](/openflightmaps/ofmx/wikis/Airport#rdn-runway-direction) * [x] 🇫🇷 Use `Rdd` to code declared distances:<br>`xt_valDispTres` and `xt_uomDispTres` -> `codeType=DPLM`<br> `xt_TORA` and `xt_uomDeclDistLimit` -> `codeType=TORA`<br>`xt_LDA` and `xt_uomDeclDistLimit` -> `codeType=LDA` ## Airspace ### [<ins>`Ase`</ins>](/openflightmaps/ofmx/wikis/Airspace#ase-airspace) * [x] 🇫🇷 Add `Ase->codeActivity` primarily to add recreational use into maps (acrobatics, gliding, winching, parachuting and such) * [x] ~~🇫🇷 Currently, the editor "remarks" are always stored as `Ase->txtRmk` of the main `Ase`. However, if class layers are present, the main `Ase` should only contain identifying properties and everything else should go into the slave `Ase#CLASS` elements in order to allow differing remarks per class layer ([see example](/openflightmaps/ofmx/tree/master/examples/airspace.ofmx)).~~ (won't do, see comments below) * [x] ~~🇫🇷 Rename the attribute `Ase@xt_classLayersAvail` to `Ase@classLayers` and assign it the number of class layers (1 or more) instead of a boolean.<br>*Note: `Ase@classLayers` is only used when OFMX is imported by the OFM editor to speed up parsing.*~~ (obsolete) * [x] 🇫🇷 Rename the element `xt_selAvail` to `codeSelAvbl` and allow only the values `Y` (yes/true) or `N` (no/false).<br>*Note: `codeSelAvbl` or selective availability declares that an airspace may be activated by third parties e.g. the military.* ### [<span>`Avx`</span>](/openflightmaps/ofmx/wikis/Airspace#avx-border-vertex) * [x] 🇫🇷 `GbrUid` must be the first children of `Avx` for frontiers (border transitions). Any other position within `Avx` renders the document invalid. ### [<span>`Adg`</span>](/openflightmaps/ofmx/wikis/Airspace#adg-derived-geometry) * [x] 🇫🇷 Wrap each `AdgUid` in it's own `Adg`. In other words: Only one `AdgUid` is allowed per `Adg`. * [x] 🇫🇷 Include complete `Adg->AseUidSameExtent` which contains the `codeType` and `codeId` of the referenced `Ase`. ## Navigational Aid ### All Navigational Aids * [x] 🇫🇷 Remove all properties not present in the documentation (or [sync with example](/openflightmaps/ofmx/tree/master/examples/navigational_aid.ofmx)). * [x] The exported AIXM contains illegal properties when you e.g. select "VOR", fill in the form, switch to "ICAO", export data. Easiest solution: Empty all input fields when switching the navigational aid type. ### [<ins>`Dpn`</ins>](/openflightmaps/ofmx/wikis/Navigational+aid#dpn-designated-point) (named "ICAO" in the editor) * [x] 🇫🇷 Remove the duplicate `codeId` which is *not* nested within `DpnUid`. * [x] Remove editor input fields for "magnetic variation", "year of magnetic variation" and "magnetic variation annual change". (Designated points are not subject to magnetic variation.) ### [<ins>`Dme`</ins>](/openflightmaps/ofmx/wikis/Navigational+aid#dme-dme) * [x] Remove editor input fields for "magnetic variation", "year of magnetic variation" and "magnetic variation annual change" and "VARIATION" subtitle. (Distance measuring is not subject to magnetic variation.) ### [<ins>`Mkr`</ins>](/openflightmaps/ofmx/wikis/Navigational+aid#mkr-marker-beacon) * [x] 🇫🇷 `codeId` may only contain any combination of `.` (dots) and `-` (dashes). * [x] `codePsnIls` dropdown is missing value `C` (backcourse). * [x] Remove the editor input fields `Frequency` and `Unit`, but always include the static properties ` <valFreq>75</valFreq>` and `<uomFreq>MHZ</uomFreq>`. (All markers operate on this frequency.) ### [<ins>`Ndb`</ins>](/openflightmaps/ofmx/wikis/Navigational+aid#ndb-ndb) * [x] Remove editor input fields for "magnetic variation", "year of magnetic variation" and "magnetic variation annual change" and "VARIATION" subtitle. (Non-directional beacon and magnetic variation are nonsensical.) ### [<ins>`Tcn`</ins>](/openflightmaps/ofmx/wikis/Navigational+aid#tcn-tacan) * [x] Remove the editor input fields `Frequency` and `Unit`. (TACAN work only with channels.) * [x] 🇫🇷 Add `valDeclination` and editor input field "magnetic declination". ### [<ins>`Vor`</ins>](/openflightmaps/ofmx/wikis/Navigational+aid#vor-vor) * [x] ~~Remove `valMagVarChg`~~ (under investigation) * [x] 🇫🇷 Verify VOR/DME is a *VOR followed by a DME which associates the VOR*. * [x] 🇫🇷 Verify VORTAC is a *VOR followed by a TACAN which associates the VOR*. (The generated markup is wrong right now, since it's a TACAN followed by a DME which associates the TACAN.) ## Organisation ### [<ins>`Uni`</ins>](/openflightmaps/ofmx/wikis/Organisation#uni-unit) * [x] Move `codeType` inside `UniUid` ### [<span>`Fqy`</span>](/openflightmaps/ofmx/wikis/Organisation#fqy-frequency) * [x] 🇫🇷 Use `valFreqTrans` instead of `valFreqRec` as transmitting frequency ## Obstacle ### [<ins>`Ogr`</ins>](/openflightmaps/ofmx/wikis/Obstacle#ogr-obstacle-group) * [x] `txtName`: UPCASE value * [x] Add `geoLat` and `geoLong` * [ ] Move `txtName` out of `OgrUid` as [shown by example](https://gitlab.com/openflightmaps/ofmx/-/blob/master/examples/obstacle.ofmx#L11). * [x] Add `codeDatum` with fix value `WGE` right before `valGeoAccuracy`. * [x] Rename `lateralPrecision` to `valGeoAccuracy` and add `uomGeoAccuracy` right after. * [x] Rename `verticalPrecision` to `valElevAccuracy` and add `uomElevAccuracy` right after. * [x] Remove `origin` and use [<span>`Ogr@source`</span>](/openflightmaps/ofmx/wikis/Features#source) attribute instead. ### [<ins>`Obs`</ins>](/openflightmaps/ofmx/wikis/Obstacle#obs-obstacle) * [x] Rename `txtDescrType` to `codeType`. * [x] Add `codeDatum` with fix value `WGE` right before `valElev`. * [x] Rename `DefaultHeight` to `codeHgtAccuracy`. * [x] `ObsUidLink`: use full `ObsUid` payload as shown by example. * [x] `codeLinkType`: UPCASE value * [ ] Add `@region` attribute * [ ] Remove `codeGroup` (an obstacle is member of a group if it contains an `OgrUid` association) * [ ] Move `OgrUid` out of `ObsUid` as [shown by example](https://gitlab.com/openflightmaps/ofmx/-/blob/master/examples/obstacle.ofmx#L25). * [ ] Make `OgrUid` optional:<br>Obstacles with no `OgrUid` are individual, it is no longer necessary to have a "pro forma" obstacle group. In other words: An obstacle group should have more than one obstacle! However, there are exceptions to this rule of thumb: In order to visualize obstacle groups for which only the number of group members is know but not the exact positions of each member, it is possible to assign only one obstacle to a group and mention the number of obstacles in `txtRmk`. * [ ] Add `uomElevAccuracy`:<br>An `Ogr` obstacle group defines horizontal accuracy (`valGeoAccuracy`/`uomGeoAccuracy`) and vertical accuracy (`valElevAccuracy`/`uomElevAccuracy`) for all group members. The same tags now exist on `Obs` obstacle as well to define accuracies for individual obstacles or – if ever necessary – override the group accuracies. Three of the for tags exist in AIXM already, only `uomElevAccuracy` is added by OFMX.