ISO 23629-7:2021

UAS traffic management (UTM) - Part 7: Data model for spatial data

This document specifies the data model that is related to various spatial information for common use between the UAS service provider and the system for operation control, e.g. UTM. This document specifies the names of the items for the data model, while the communication architecture and responsibilities of actors to define the items are not included.

Gestion du trafic des aéronefs sans pilote (UTM) — Partie 7: Modèle de données pour les données spatiales

General Information

• Status: Published
• Publication Date: 28-Sep-2021
• ICS: 49.020 - Aircraft and space vehicles in general
• Technical Committee: ISO/TC 20/SC 16 - Unmanned aircraft systems
• Drafting Committee: ISO/TC 20/SC 16/WG 4 - UAS Traffic Management
• Current Stage: 6060 - International Standard published
• Start Date: 29-Sep-2021
• Due Date: 11-Jan-2022
• Completion Date: 29-Sep-2021

Relations

• Consolidated By: ISO 11118:2025 - Gas cylinders - Non-refillable metallic gas cylinders - Specification and test methods
• Effective Date: 19-Nov-2022

Overview

ISO 23629-7:2021 - "UAS traffic management (UTM) - Part 7: Data model for spatial data" defines a standardized data model for spatial information exchanged between UAS service providers and operation‑control systems (for example, UTM). The standard specifies the names and minimum attributes of spatial data items (ground features, obstacles, virtual constructs and dynamic phenomena) but does not define communication architecture or actor responsibilities. It is intended as a reference model to improve interoperability, reduce implementation costs and support consistent map data compilation and maintenance.

Key technical topics and requirements

• Four primary data packages form the overall model:
  • Ground map package - entities such as takeoff and landing areas and land with attributes like Identifier, Generate time, Disappearance time, Elevation, Geoid undulation, Time zone, Magnetic declination, Shape and Location.
  • Obstacle data package - static and temporal obstacles (e.g., buildings, towers, scaffolding) with attributes including Height, Type of height, Shape, Location and Type of obstacle.
  • Virtual data package - virtual representations (airspace, flight routes, CNS coverage, geo-limitations and other intangible constructs) with named attributes for consistent interpretation.
  • Dynamic data package - transient objects and phenomena that change over time (object sub‑package and phenomena sub‑package) to support real‑time situational awareness.
• Data quality: implementations are expected to apply a data quality management system in accordance with ISO 19157.
• Terminology alignment: uses definitions from ISO 21384-4 and references common geospatial concepts (e.g., elevation, height above ellipsoid, shape, magnetic declination).
• Annexes provide examples of information (Annex A) and use cases (Annex B) to guide implementation.

Practical applications and who would use it

• UAS service providers and UTM system developers - to standardize the spatial datasets they exchange and consume for flight planning, deconfliction and authorization.
• Map and geospatial data providers - to compile consistent ground map and obstacle layers for UAS operations.
• UAS application developers and avionics vendors - to reduce integration effort by adopting a common data model for spatial inputs.
• Regulators and air navigation service providers - to define requirements and verify conformity of spatial information used in traffic management.
• Infrastructure owners and vertiport operators - to publish takeoff/landing area attributes and operational constraints in a machine‑readable form.

Benefits include improved interoperability, streamlined data maintenance, clearer semantics for safety‑critical spatial information, and facilitation of scalable UTM services.

Related standards

• ISO 19157 - Geographic information - Data quality
• ISO 21384-4 - Unmanned aircraft systems - Part 4: Vocabulary
• Other parts of the ISO 23629 UTM series (see ISO catalogue for list)

Keywords: ISO 23629-7:2021, UAS traffic management, UTM, data model for spatial data, unmanned aircraft systems, geospatial data, obstacle data, ground map package, dynamic data package.

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 23629-7
First edition
2021-09
UAS traffic management (UTM) —
Part 7:
Data model for spatial data
Gestion du trafic des aéronefs sans pilote (UTM) —
Partie 7: Modèle de données pour les données spatiales
Reference number
©
ISO 2021
© ISO 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Data model . 2
4.1 Overall data model . 2
4.2 Ground map package . 3
4.2.1 Overview . 3
4.2.2 Attributes of takeoff and landing area. 3
4.2.3 Attributes of land . 4
4.3 Obstacle data package . 5
4.3.1 Overview . 5
4.3.2 Attributes of static obstacle . 5
4.3.3 Attributes of temporal obstacle . 5
4.4 Virtual data package . 6
4.4.1 Overview . 6
4.4.2 Attributes of airspace . 6
4.4.3 Attributes of flight route. 6
4.4.4 Attributes of CNS coverage. 7
4.5 Dynamic data package . 7
4.5.1 Overview . 7
4.5.2 Object sub-package . 8
4.5.3 Phenomena sub-package . 9
Annex A (informative) Examples of information .11
Annex B (informative) Use cases.12
Bibliography .26
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/ patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/
iso/ foreword .html.
This document was prepared by Technical Committee, ISO/TC 20, Aircraft and space vehicles,
Subcommittee SC 16, Unmanned aircraft systems.
A list of all parts in the ISO 23629 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2021 – All rights reserved

Introduction
In order to enable UAS (unmanned aircraft systems) to operate safely, there is a need to define the data
model that is related to various spatial information for common use between the UAS operators and the
UAS traffic management (UTM) system. Existing standards regarding spatial data for safely operating
UAS including static data and dynamic data do not exist, whereas efforts are underway to establish
related standards on the part of ASTM and EUROCAE.
This document can be used as a reference model. Implementations of this document can lead to cost
reductions in maintenance/expansion for application developers as well as compilation/maintenance
of map data for map providers.
INTERNATIONAL STANDARD ISO 23629-7:2021(E)
UAS traffic management (UTM) —
Part 7:
Data model for spatial data
1 Scope
This document specifies the data model that is related to various spatial information for common
use between the UAS service provider and the system for operation control, e.g. UTM. This document
specifies the names of the items for the data model, while the communication architecture and
responsibilities of actors to define the items are not included.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 19157, Geographic information — Data quality
ISO 21384-4, Unmanned aircraft systems — Part 4: Vocabulary
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21384-4 and the following
apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
aerodrome
defined area on land or water (including any buildings, installations and equipment) intended to be
used either wholly or in part for the arrival, departure and surface movement of aircraft
[SOURCE: ICAO/Annex 2]
3.2
CNS
communications, navigation, and surveillance systems, employing digital technologies, including
satellite systems together with various levels of automation
[SOURCE: ICAO Doc. 9750]
3.3
time
mark attributed to an instant or a time interval on a specified time scale
Note 1 to entry: The representation rules are defined in the ISO 8601 series.
[SOURCE: ISO 8601-1:2019, 3.1.1.2, modified — The original notes to entry have been removed; a new
note 1 to entry has been added.]
3.4
elevation
vertical distance of a point or a level, on or affixed to the surface of the earth, measured from mean sea
level
[SOURCE: ICAO/Annex 4]
3.5
flight route
specified route designed for channelling the flow of traffic as necessary for the provision of UTM (3.11)
3.6
geo-limitation
entity that represents area surrounded by virtual boundary lines in the real world
3.7
geoid undulation
height of the geoid relative to a given ellipsoid of reference
3.8
height above ellipsoid
vertical distance of a point or a level, on or affixed to the surface of the earth, measured from World
Geodetic System 1984 (WGS 84) ellipsoid
3.9
shape
horizontal projection on earth of a given object
3.10
magnetic declination
angle on the horizontal plane between magnetic north and true north
3.11
UAS traffic management
UTM
set of traffic management and air navigation services aiming at safe, secure and efficient integration of
multiple manned and unmanned aircraft flying inside the respective designated operational coverage
of each service
4 Data model
4.1 Overall data model
Overall data model shall consist of four packages: ground map package, obstacle data package,
virtual data package, dynamic data package. Figure 1 shows the overall data model. For examples of
information, see Annex A. For use cases, see Annex B.
An overall, data quality management system shall prove the data quality in accordance with ISO 19157.
2 © ISO 2021 – All rights reserved

Figure 1 — Overall data model
4.2 Ground map package
4.2.1 Overview
Ground map package contains data that are defined as “geographical surface areas designed for specific
activities”. Ground map package shall as a minimum contain two entities: takeoff and landing areas and
land.
4.2.2 Attributes of takeoff and landing area
Takeoff and landing area is an entity that represents the area designated for either takeoff or landing
of a UA (unmanned aircraft) in the real world. Table 1 summarizes minimum attributes of takeoff and
landing area. Magnetic declination changes over time, and it may be updated as needed. Takeoff and
landing area may include vertiports using the elements of conditions for operation and resources.
Table 1 — Attributes of takeoff and landing area
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Available time interval Information indicating the time interval the area is available
Elevation Information indicating the elevation
Geoid undulation at elevation Information indicating the geoid undulation at elevation
Time zone Information indicating the time zone
Magnetic declination Information indicating the magnetic declination
Shape Information indicating the shape type and boundaries data (e.g. a group of
coordinates of control points for polygon or centre point with radius) of the
entity
Location Information indicating the centroid of the entity in terms of latitudes and
longitudes
Administration contact details Information indicating the entity’s administration contact details
(e.g. administration’s name, address, telephone)
Conditions for operation Information indicating the conditions for operation (e.g. weather conditions,
aircraft performance, operation procedures), either generally applicable to
all operations, or limited to specific operations
Resources Information indicating the equipment of the entity (e.g. energy supply,
repairment, on-site staff)
Availability of emergency landing Information indicating availability of emergency landing areas including
areas dimensions and operating conditions, if any
4.2.3 Attributes of land
Land is an entity that represents artificially divided areas for specific activities in the real world. Table 2
lists minimum attributes of land. Magnetic declination changes over time, and it may be updated as
needed.
Table 2 — Attributes of land
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Elevation Information indicating the elevation
Geoid undulation at elevation Information indicating the geoid undulation at elevation
Time zone Information indicating the time zone
Magnetic declination Information indicating the magnetic declination
Shape Information indicating the shape type and boundaries data (e.g. a group of
coordinates of control points for polygon or centre point with radius) of the
entity
Location Information indicating the centroid of the entity in terms of latitudes and
longitudes
Availability of emergency landing Information indicating availability of emergency landing areas including
areas dimensions and operating conditions, if any
Type of land Information indicating the type of land (e.g. farmland, road)
4 © ISO 2021 – All rights reserved

4.3 Obstacle data package
4.3.1 Overview
Obstacle data package shall contain data that are defined as “tangible objects having a temporarily or
permanently fixed location in the real world and pose a potential hazard to surface or air traffic of
aircraft”. Obstacle data package shall as a minimum contain two entities: static and temporal obstacle.
4.3.2 Attributes of static obstacle
Static obstacle can be used for buildings, pylons, trees, etc. Table 3 summarizes minimum attributes of
static obstacle.
Table 3 — Attributes of static obstacle
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Height Information indicating the height of the entity’s maximum vertical extent
measured from a specified datum (specified in type of height)
Type of height e.g. height above ellipsoid, height above mean sea level
Shape Information indicating the shape type and boundaries data (e.g. a group of
coordinates of control points for polygon or centre point with radius) of the
entity
Location Information indicating the centroid of the entity in terms of latitudes and
longitudes
Type of obstacle Information indicating the type of obstacle (e.g. building, tower, pole, antenna)
4.3.3 Attributes of temporal obstacle
Temporal obstacle can be used for short-term erections or for modifications to a static obstacle such as
scaffolding. Table 4 summarizes minimum attributes of temporal obstacle.
Table 4 — Attributes of temporal obstacle
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Height Information indicating the height of the entity’s maximum vertical extent
measured from a specified datum (specified in type of height)
Type of height e.g. height above ellipsoid, height above mean sea level
Shape Information indicating the shape type and boundaries data (e.g. a group of
coordinates of control points for polygon or centre point with radius) of the
entity
Location Information indicating the centroid of the entity in terms of latitudes and
longitudes
Type of obstacle Information indicating the type of obstacle (e.g. scaffolding, construction
equipment)
4.4 Virtual data package
4.4.1 Overview
Virtual data package shall contain data that are defined as “virtual objects that are intangible
representations (including computer simulated representations) of attributes of particular real-world
areas or objects”. Virtual data package shall as a minimum contain three entities: airspace, flight routes,
and CNS coverage.
4.4.2 Attributes of airspace
Table 5 summarizes attributes of airspace. Airspace may include geo-limitations using the elements of
conditions for operation and type of airspace.
Table 5 — Attributes of airspace
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Maximum height Information indicating the altitude of the entity's maximum vertical extent
measured from a specified datum (specified in type of height)
Minimum height Information indicating the altitude of the entity's minimum vertical extent
measured from a specified datum (specified in type of height)
Type of height e.g. height above ellipsoid, height above mean sea level
Shape Information indicating the shape type and boundaries data (e.g. a group of
coordinates of control points for polygon or centre point with radius) of the
entity
Location Information indicating the centroid of the entity in terms of latitudes and
longitudes
Administration contact details Information indicating the entity’s administration contact details
(e.g. administration’s name, address, telephone)
Conditions for operation Information indicating the conditions for operation (e.g. weather conditions,
aircraft performance, operation procedures), either generally applicable to
all operations, or limited to specific operations
Availability of UTM services Information indicating availability of UTM services (e.g. sharing of traffic
information between manned and unmanned aircraft), if any
Type of airspace Controlled airspace, uncontrolled airspace, authorized airspace, unauthorized
airspace, etc.
4.4.3 Attributes of flight route
Table 6 summarizes attributes of flight route. A flight route is an entity that consists of a sequence of
waypoints and tolerance from each waypoint, representing a group of coordinates in terms of latitudes,
longitudes and height for a flight of a UA, which may have a temporal element if necessary.
Table 6 — Attributes of flight route
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Sequence of waypoints Information indicating the sequence of elements the flight route entity entails,
along with a time element if necessary
6 © ISO 2021 – All rights reserved

Table 6 (continued)
Attribute Description
Tolerance of waypoints Information indicating the tolerated deviation from the entity in terms of
distance from a given waypoint, based on the same ICAO principles that are
used in required navigation performance (RNP) as necessary.
Administration contact details Information indicating the entity’s administration contact details
(e.g. administration’s name, address, telephone)
Conditions for operation Information indicating the conditions for operation (e.g. weather conditions,
aircraft performance, operation procedures), either generally applicable to
all operations, or limited to specific operations
Availability of UTM services Information indicating availability of UTM services (e.g. sharing of traffic
information between manned and unmanned aircraft), if any
Type of flight route Controlled flight route, uncontrolled flight route, etc.
4.4.4 Attributes of CNS coverage
CNS coverage is an entity that represents the coverage of individual units composing the CNS
infrastructure in the real world. Table 7 summarizes minimum attributes of CNS coverage.
Table 7 — Attributes of CNS coverage
Attribute Description
Identifier Information for identifying the entity
Generate time Information indicating the time the entity was generated
Disappearance time Information indicating the time the entity will be disappeared, if projected
Maximum height Information indicating the altitude of the entity's maximum vertical extent
measured from a specified datum (specified in type of height)
Minimum height Information indicating the altitude of the entity's minimum vertical extent
measured from a specified datum (specified in type of height)
Type of height e.g. height above ellipsoid, height above mean sea level
Shape Information indicating the shape type and boundaries data (e.g. a group of
coordinates of control points for polygon or centre point with radius) of the
entity
Location Information indicating the vertices or the centroid of the entity in terms of
latitudes and longitudes, where vertices are indicated for polylines, polygons,
and polynomial curves, and the centroid in case of circle
...