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 |
|---|
Personnel
| User | Role | Organization | Security | Last Login | Actions |
|---|
Aerodromes
| ICAO | Name | ARP | Elev | Runways | Criteria | Actions |
|---|
Settings
Obstacle identifier
The UID a new obstacle gets: a prefix, then a number with at least this many digits. Existing obstacles keep their UID. An identifier is never issued twice — a deleted obstacle’s included — so the start number must be above every number already issued with the prefix. When the digits run out, the number gains a digit (9999 is followed by 10000); nothing is cut.
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.
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.