Task Status

Task Status

This page is part of the ongoing SWIM Community of Interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.

Service Definition Identification

Trace

SWIM-DEFN-030

WORKING

service definition identification	title	Service definition for the Aeronautical Simple Feature Request Service
	edition	00.00.05
	reference date	2025-03-28

TBD
WORKING
DRAFTED
AGREED

Service Identification

Trace

SWIM-DEFN-040

WORKING

service identification	service name	Aeronautical Simple Feature Request Service

Service Abstract

Trace

SWIM-DEFN-050

WORKING

service abstract

The Aeronautical Simple Features Service allows the service consumer to get features that are customised and assembled from aeronautical information for use in Geographical Information System (GIS) systems. The features are designed for direct use in commercial-off-the-shelf GIS tools and libraries without the need for further processing/assembly by the service consumer.

The features offered by the service are assembled from the high quality, up-to-date, trusted, regulated aeronautical information that is available in aeronautical information management (AIM) databases.

The service can be considered as a specialised aeronautical information service complementing the Aeronautical Information Request Service and the Aeronautical Aerodrome Map Request Service.

Service Definition Provider

Trace

SWIM-DEFN-085

WORKING

service definition provider	name	EUROCONTROL
	description	EUROCONTROL is a pan-European, civil-military organisation dedicated to supporting European aviation.
	point of contact	swim@eurocontrol.int

Geographical Extent of Information

Trace

SWIM-DEFN-090

WORKING

Explanatory note

This field is left empty.

geographical extent of information

Service Categories

Trace

SWIM-DEFN-095, SWIM-DEFN-100

WORKING

service categories	category	category name	information domain
		value	AERONAUTICAL_INFORMATION
		scheme	https://reference.swim.aero/information-services/service-categories/CodeInformationDomainType.html
	category	category name	business activity
		value	INFORMATION_MANAGEMENT
		scheme	http://reference.swim.aero/information-services/service-categories/CodeBusinessActivityType.html
	category	category name	intended service consumer
		value	CIVIL_AIRSPACE_USER MILITARY_AIRSPACE_USER CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER AIR_TRAFFIC_SERVICE_PROVIDER AERONAUTICAL_INFORMATION_SERVICE_PROVIDER COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER PROVIDER_OF_DATA_SERVICES NETWORK_MANAGER AIRPORT_OPERATOR AIRSIDE_GROUND_HANDLER MILITARY_DEFENCE_CENTRE UAS_GEOGRAPHICAL_ZONES_PROVIDER
		scheme	https://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html
	category	category name	intended service provider
		value	AERONAUTICAL_INFORMATION_SERVICE_PROVIDER
		scheme	https://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html
	category	category name	service type
		value	AERONAUTICAL_FEATURE_ACCESS_SERVICE
		scheme	https://reference.swim.aero/information-services/service-categories/CodeServiceType.html

Service Standard Reference

Trace

SWIM-DEFN-120

WORKING

Explanatory note

This field is left empty.

service standard reference	reference
	implemented options
	deviations/additions

Operational Environment

Trace

SWIM-DEFN-130

WORKING

operational environment

operational needs

Some stakeholders with a spatial data infrastructure using GIS technology require interoperable aeronautical information that can be used 'out-of-the-box' without the need for complex processing of geometry and/or temporality. Retrieving features that have already been assembled supports their operations in flight planning, ... tbd

A list of operational needs that this service contributes to satisfying is available in Appendix C.

capabilities

The service provides features that are customised and assembled from aeronautical information for use direct use in Geographical Information System (GIS) systems.

information exchange requirements

The service takes into account the following information exchange requirements:

IER 1	The service shall provide features that are in the scope of the AIS Data Catalogue (add ref.) Note: The features are assembled from aeronautical information that is normally normalised in an AIM database. There is no need for this normalisation to be preserved.
IER 2	Features with a spatial representation shall be provided using simple (self-contained) geometries The latitude and longitude shall be provided using a coordinate reference system that supports WGS84 (TBD, urn:ogc:def:crs:OGC::CRS84). The vertical representation shall be provided using an attribute (following the 2.5D pattern) i.e. not as part of the coordinates.
IER 3	Features that change over time shall have the values of their attributes integrated into one version that has a valid time period.
IER 4	Features/messages shall have the following metadata provided. tbd Note: It is possible to have the metadata inline or as a referenced file.

Service Functions

Trace

SWIM-DEFN-140

WORKING

service functions	function	name	Request aeronautical features
		description	The service consumer shall be able to request features filtered by feature type and/or name.
		real-world effect	The aeronautical feature is received and can be used in GIS and other systems.
	function	name	Enable advanced filtering of aeronautical features
		description	The service consumer shall be able to request features filtered according to spatial, temporal and logical operators.
		real-world effect	The aeronautical feature is received and can be used in GIS and other systems.

Service Access and Use Conditions

Trace

SWIM-DEFN-150

WORKING

service access and use conditions	legal constraints		TBD
	service policies	business policy	TBD
		operational policy	TBD
		technical policy	TBD
	service consumption constraints		There shall be a service consumption constraint to ensure that a service consumer does not impose undue loads on computer and network resources, for example, by polling it at a higher frequency than the status is normally provided.

Security Constraints

Trace

SWIM-DEFN-160

WORKING

security constraints	authentication	The service shall ensure consumer authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0042. The service shall ensure provider authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0042.
	authorisation	The service shall ensure that satisfactory authorisation is put in place according to EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070.
	confidentiality	The service shall ensure point-to-point confidentiality in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above.
	integrity	The service shall ensure point-to-point integrity in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above.

Quality of Service

Trace

SWIM-DEFN-180

WORKING

quality of service	performance	capacity	The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. The service should ensure that a single user is unable to monopolise a service or to degrade it below agreed service levels for others users.
	performance	response time	The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.
	reliability	availability	The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. *Note: the following factors must be used in deciding the fitness for purpose:* *the number of users likely to be delayed significantly by a loss of the service*
	reliability	recoverability	The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.
	security	confidentiality	The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
	security	integrity	The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.

Quality of Data

Trace

SWIM-DEFN-185

WORKING

quality of data

The quality of features offered by the service shall be verified by the service provider.

Meet data catalogue?

Source of Information

Trace

SWIM-DEFN-190

WORKING

source of information

source

The service provider shall ensure that the features offered by the service are based on aeronautical information received from the appropriate authorised originating sources acting as AIS. This includes:

modifications

Note: the features offered by the service can be assembled from multiple source information.

Note: it is possible to fill an attribute based on calculations from the source information.

Note: modifications may change resolution, etc.

Service Validation Information

Trace

SWIM-DEFN-200

WORKING

Explanatory note

This field is left empty.

service validation information	validation performed
	method used
	summary of the validation steps performed
	results achieved
	how the service consumer may obtain the validation evidence

Application Message Exchange Pattern

Trace

SWIM-DEFN-210

WORKING

application message exchange pattern	REQUEST_REPLY

Service Behaviour

Trace

SWIM-DEFN-220

WORKING

service behaviour	typical behaviour	The service behaviour shall be in accordance with the patterns detailed in the Message Exchange Patterns: Identification Guidelines. The typical behaviour for SYNCHRONOUS_REQUEST_REPLY (as used in Aeronautical Simple Feature Request Service Request Interface) is as follows: The request message is sent from the service consumer to the service The service consumer remains blocked while awaiting the reply The service remains blocked while processing the reply The reply message is sent from the service to the service consumer

Service Monitoring

Trace

SWIM-DEFN-230

WORKING

service monitoring	A service monitoring mechanism should be made available to service consumers.

Service Interfaces

Trace

SWIM-DEFN-240

WORKING

service interfaces	interface	name	Aeronautical Simple Feature Request Service Request Interface
		description	The interface is used to group the operations offered by the OGC API - Features standard.
		provider/consumer side	Provider side

SWIM TI Profile and Interface Bindings

Trace

SWIM-DEFN-250, SWIM-DEFN-255

WORKING

Aeronautical Simple Feature Request Service Request Interface

SWIM TI profile and interface bindings	profile name	EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
	profile version	1.1
	selected service interface binding	WS_LIGHT
	selected network interface binding	The service shall use the network bindings of the SWIM TIYP.
	description	The interface shall use the OGC API - Features standard. Check if there are different levels e.g. basic, advanced... and which should be supported

Service Interface Protocols and Data Format

Trace

SWIM-DEFN-260

WORKING

service interface protocols and data format	transport / messaging protocols	The service shall use TLS1.2 or later in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.
service interface protocols and data format	data format	This is captured at Service Message level (see below). WS_LIGHT does not mandate a data format. The header expresses what is used.

Service Operations

Trace

SWIM-DEFN-270

TBD

Explanatory note

The OGC API – Features standard is used to implement the service operations.

It is not the intention to repeat the standardised operations here. However, the table below illustrates how the xxx operation would look in the context of this service.

service operations	operation	operation name
		description
		messages
	operation	operation name
		description
		messages

Service Messages

Trace

SWIM-DEFN-280

WORKING

Explanatory note

The OGC API – Features standard details the basic messages such as request and response messages.

It is not the intention to repeat the standardised messages here. The table below provides illustrative details.

service messages	message	name	Reply
		description	OpenAPI returns a FeatureCollection
		type	Out
		data format	GeoJSON (2016) is used to encode features (https://www.rfc-editor.org/rfc/rfc7946.txt).
	message	name	Request
		description	Request message submitted to the service containing query expressions.
		type	In
		data format	JSON and/or XML

Information Definition (Minimum) and (Extended)

Trace

SWIM-DEFN-290, SWIM-DEFN-300

WORKING

information definition

The service shall offer feature as per TBD model/schema.

Note: The GetCapabilities operation will expose the available layers, styles and coordinate reference systems.

Note: The structuring and styling of the layers is a service design decision to be taken when implementing the service.

Note: The coordinate reference system and naming of the layers used in the service are subject to the requirements provided in this service definition.

Filter Encoding

Trace

SWIM-DEFN-310

TBD

filter encoding

Check if used: OGC API - Features - Part 3: Filtering

The service shall support the BBOX spatial operator defined in the OGC Filter Encoding 2.0 Encoding Standard.

The service shall support the During temporal operator defined in the OGC Filter Encoding 2.0 Encoding Standard.

The service should support other filtering based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard.

The service may support other filters on a case by case basis.

Example: other filters defined on a case by case basis are PARALLEL_TO and PERPENDICULAR_TO.

Machine-Readable Service Interface Definition

Trace

SWIM-DEFN-320

WORKING

Explanatory note

This field is left empty. No machine-readable service interface definition is provided.

machine-readable service interface definition

Model View

Trace

SWIM-DEFN-330

WORKING

Explanatory note

This field is left empty. No model view is provided.

model view

Abbreviations and Acronyms

Trace

SWIM-DEFN-350

TBD

abbreviations and acronyms	abbreviation	code	API
		term
	abbreviation	code	GIS
		term
	abbreviation	code	OGC
		term

Appendix A: References

references	reference	title	Message Exchange Patterns: Identification Guidelines.
		version	JULY 2nd, 2019
		description	Document intended to facilitate the understanding of message exchange patterns from an application and Technical Infrastructure perspective.
		url	https://reference.swim.aero/technical-infrastructure/message-exchange-patterns-identification-guidelines.html
		document type	SERVICE_BEHAVIOUR_DESCRIPTION
	reference	title	Info definition
		version
		description
		url
		document type	INFORMATION_DEFINITION
	reference	title	semantic correspondence
		version
		description	The report on the information definition and the ATM Information Reference Model (AIRM)
		url
		document type	SEMANTIC_CORRESPONDENCE_REPORT
	reference	title	OGC Filter Encoding 2.0 Encoding Standard or API takes over
		version	2.0
		description	This jointly developed OGC and ISO TC/211 International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. Note: This is equivalent to ISO 19143 - Geographic Information - Filter encoding.
		url	https://www.ogc.org/docs/is
		document type
	reference	title	OGC API Features specification
		version	1.0.1 \ MIGHT NEED DIFFERENT REFERENCES PER PART
		description	A multi-part standard that offers the capability to create, modify, and query spatial data on the Web and specifies requirements and recommendations for APIs that want to follow a standard way of sharing feature data
		url	https://ogcapi.ogc.org/features/
		document type
	reference	title	GeoJSON - WITH CRS extensions (JSON-FG) https://www.geonovum.nl/uploads/documents/220405-JSON-FG.pdf, https://docs.ogc.org/DRAFTS/21-045.html
		version	2016
		description	GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON).
		url	https://www.rfc-editor.org/rfc/rfc7946.txt
		document type

Appendix B: Information Definition forAeronautical Simple Feature Request Service

The table below lists the layers and features that are needed to support the scope of the Aeronautical Simple Feature Request Service.

feature
tbd

Appendix C: Operational Needs

Transversal

Collaborative information sharing is essential for decision making involving multiple actors. Automatic taxi with time and path information on the ground, collaborative decision making during emergencies, de-icing operations and infrastructure availability information are examples that involve multiple actors including the aircraft crew.

Retrieve layered geospatial aeronautical data for 'out-of-the-box' interoperable use within scope of the data domains managed in their spatial data infrastructure using GIS technology.
Retrieve integrated temporal aeronautical data for 'out-of-the-box' interoperable use within scope of the data domains managed in their spatial data infrastructure using GIS technology.

By service consumer role

Stakeholder/Role	Description of stakeholder/role	Needs for Aeronautical Data	Notes
CIVIL_AIRSPACE_USER	A generic term designating an organization operating aircraft and its pilots, the flight operations centres (FOC) responsible for the strategic planning of a flight and the entity responsible for the execution of a flight which is traditionally a flight deck.	Retrieve feature data in support of flight planning. Generate graphical representations of data in support of responsibilities. Visual support to pilots under the form of digital charts and cockpit displays. Airline engineering and operations departments may import and export obstacle data for use in their applications. Safety nets. Monitor aircraft for hazardous conditions.	Aircraft covers UAV.
MILITARY_AIRSPACE_USER	Airspace User under the authority of a military organisation.	Generate graphical representations of data in support of responsibilities. Visual support to pilots under the form of digital charts and cockpit displays. Airline engineering and operations departments may import and export obstacle data for use in their applications. Safety nets. Monitor aircraft for hazardous conditions.	There is an assumption that these will be working in DMZ under yellow profile. The AISP needs to meet the security needs. In general, they have the same needs as civil airspace users.
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER	Any public or private entity providing air navigation services for general air traffic.	Remote tower systems use different layers of visualisation to highlight movement areas, buildings, etc. for air traffic controllers. AMD data can be used to create more accurate restricted zones for geofencing around aerodromes. Creation of baseline scenarios for procedure design. Provide baseline data in support of incident analysis, including its use on to generate statistics.
MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER	Any public or private entity providing air navigation services for military air traffic.	Remote tower systems use different layers of visualisation to highlight movement areas, buildings, etc. for air traffic controllers. AMD data can be used to create more accurate restricted zones for geofencing around aerodromes.
AIR_TRAFFIC_SERVICE_PROVIDER	A generic term meaning variously, flight information service, alerting service, air traffic advisory service, air traffic control service (area control service, approach control service or aerodrome control service).	Create baseline scenarios for fast time simulations in support of capacity calculations and environmental impact assessments. Use of feature data and representations in support of the development of Operational manuals. Use of feature data and representations in support of the daily ATCO briefing. Integrate with other geographical information to provide provide ATC supervisors and ATCOS a complete operational picture of adjacent SECTORS. Integrate with other geographical information to provide management with an operational dashboard view and on support of crisis management. Provide baseline data in support of post ops analysis. Generate and validate flight plans. Update FDPS - flight data processing systems. Provide baseline data in support of the analysis and authorization UAS operations
REGULATED_METEOROLOGICAL_SERVICE_PROVIDER	An office designated to provide meteorological service for international air navigation.		No needs have been identified.
AERONAUTICAL_INFORMATION_SERVICE_PROVIDER	A service established within the defined area of coverage responsible for the provision of aeronautical information/data necessary for the safety, regularity and efficiency of air navigation.	Use another AISP's features on support of validations and verification of cross border data. Optimize AISP operations as being a possible integral part of the electronic chart implementation. Optimize AISP operations as being a possible integral part of the validations and verification proceses.
COMMUNICATION_NAVIGATION_AND_ SURVEILLANCE_SERVICE_PROVIDER	A provider of CNS services.	Analize coverage e.g. FIR boundaries. Provide baseline data in support of CNS performance monitoring. Provide baseline data in support of impact analysis on CNS infrastructure un-availabilities.
PROVIDER_OF_DATA_SERVICES	A public or private entity responsible for the management of a Data Service Provision (e.g. to one or several Virtual Centre).	Create flight manuals, Use local actual and forecasted status of the infrastructure
NETWORK_MANAGER	The organization responsible for enabling the optimum use of airspace and ensure that Airspace Users can operate preferred trajectories while allowing maximum access to airspaces and air navigation services.
AIRPORT_OPERATOR	The civilian or military agency, group or individual which exercises control over the operations of the civil airport or military airfield.	Manage ground lighting Manage movement area management Surface contamination management and inspection Local flight briefing/preparation tools (eg in ARO context) Airport capacity management
AIRSIDE_GROUND_HANDLER	A stakeholder involved in the services necessary for an aircraft's arrival at, and departure from, an airport, other than air traffic services.	Generate graphical representations of data and alerts when entering unauthorized locations.
MILITARY_DEFENCE_CENTRE	A military defence centre. Note: these centres, e.g., check for diplomatic clearance.	Know airspace boundaries, etc.
UAS GEOGRAPHICAL ZONES PROVIDER	A stakeholder making available UAS Geographical Zones on behalf of the State.	Retrieve data for geographical zones protecting air operations.

Aeronautical SWIM Services

Aeronautical Simple Feature Request Service - Service Definition

Service Definition Identification

Service Identification

Service Abstract

Service Definition Provider

Geographical Extent of Information

Service Categories

Service Standard Reference

Operational Environment

Service Functions

Service Access and Use Conditions

Security Constraints

Quality of Service

Quality of Data

Source of Information

Service Validation Information

Application Message Exchange Pattern

Service Behaviour

Service Monitoring

Service Interfaces

SWIM TI Profile and Interface Bindings

Aeronautical Simple Feature Request Service Request Interface

Service Interface Protocols and Data Format

Service Operations

Service Messages

Information Definition (Minimum) and (Extended)

Filter Encoding

Machine-Readable Service Interface Definition

Model View

Abbreviations and Acronyms

Appendix A: References

Appendix B: Information Definition forAeronautical Simple Feature Request Service

Appendix C: Operational Needs

Transversal

By service consumer role

Related content