Changes since last login
Needs attention
Data quality
Obstacle Type Distribution
Obstacle Overview Map
Activity
Recently Added
| Name | Type | Status | Elevation (m) | Latitude | Longitude | Date Added |
|---|
0 obstacles
Personnel
Accounts, organizations & security activity
| User | Role | Organization | Security | Last Login | Actions |
|---|
Aerodromes
OLS reference data — aerodromes, runways & directions
| ICAO | Name | ARP | Elev | Runways | Criteria | Actions |
|---|
Format
Which obstacles
Which fields
Imports
File with the corrections
Rows are matched to obstacles that are already in the register, by UID. An empty cell means leave that field alone, so a file that carries one corrected column changes only that column. Nothing is written until you have seen the list of changes. The name, the UID and the workflow status are never changed by a file.
Drop a spreadsheet or CSV here, or click to browse
Supported: .xlsx, .xlsm, .csv — an export from this register can be corrected and fed straight back
An update matches each row to an obstacle by the UID this register issued. AIXM carries no such column, so a row in it cannot find the obstacle it belongs to. Choose Spreadsheet / CSV.
File
The Excel template is generated from the register: the type column is a
dropdown of every value it accepts, and each heading carries a note
explaining the column. The plain CSV has the headings only.
Drop a spreadsheet or CSV here, or click to browse
Supported: .xlsx, .xlsm, .csv — columns are matched by name, so a register export can be used as it comes
Drop AIXM XML file here or click to browse
Supported: .xml (AIXM BasicMessage)