Task Status
This page is part of the ongoing SWIM communities 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.
Guidance
This template allows for the documentation of service definitions based on the requirements found at: /wiki/spaces/SCOI/pages/59605116
General requirements to remember:
| SWIM-DEFN-010 | Service definition coverage | A service definition shall define a single service | Note: This concerns the definition of a service that can be implemented by service providers. It is not used to describe a running service - use a service description in that case. Note: This requirement uses "define" rather than "describe". |
| SWIM-DEFN-020 | Service definition language | The textual descriptions in a service definition shall be written in English using the spelling listed as the primary British spelling when conflicting spellings exist. | - |
Status Key
- TBD - No work has started
- WORKING - Content is being worked on, comments discussed
- DRAFT - Draft is ready, comments resolved
- REVIEWED - Group has reviewed, edited the final draft
- AGREED - Content is finalised and agreed
Service Definition Identification
TBD
Trace
| service definition identification | title | Service Definition for Aeronautical Aerodrome Maps Service |
|---|---|---|
edition | 00.00.01 | |
reference date | 2022-04-27 |
Service Identification
WORKING
Trace
| service identification | service name |
|
|---|
Service Abstract
TBD
Trace
| service abstract | PJ15-11: The Aeronautical Digital Map Common Service provides users the capability to retrieve graphical representation of aeronautical data / information. The output is a standardized / harmonised graphic information that can be retrieved by individual requests demanding specific geographical areas. 8.3.10: The AeronauticalInformationMap service provides the CDM for the provision of aeronautical information maps. The purpose of the service is the provision of digital aeronautical information maps resembling the current aeronautical AIP charts but improving its functionalities and usability. 8.3.10: The main purpose of the AeronauticalInformationMap service is to provide maps as raster images to consumers AMIS: AccessAMDBMap Aims to fulfil Information Exchange Requirements of accessing pre-styled geo-referenced AMDB layers (bitmap images). |
|---|
Service Definition Provider
TBD
Trace
service definition provider | name | EUROCONTROL |
|---|---|---|
| abbreviated name | ||
| description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. |
Geographical Extent of Information
DRAFT
Trace
Working notes
SAT 2022-12-13:
Agreed to leave empty as it is not possible to give a precise requirement.
The service is expected to provide information for the area of responsibility (e.g. a specific FIR or worldwide) of the state plus delegations. This may be found in GEN 3.1 of the AIP. Other options are e.g. FABEC.
| geographical extent of information |
|---|
Service Categories
DRAFT
Trace
Service Standard Reference
WORKING
Trace
service standard reference | reference | |
|---|---|---|
| implemented options | ||
| deviations/additions |
Operational Environment
DRAFT
Trace
Working notes
SAT 2022-11-11:
The service will focus on what the AISP makes available to the next intended user. Therefore, it will not cover A3SG-IER-02 Aerodrome Mapping Data Exchange. This will be looked at later and as a different service.| operational environment | operational needs | Air traffic management is defined as the "dynamic, integrated management of air traffic and airspace including air traffic services, airspace management and air traffic flow management - safely, economically and efficiently - through the provision of facilities and seamless services in collaboration with all parties and involving airborne and ground-based functions". It is provided by the air traffic management system that, amongst other things, relies on the collaborative integration of information and services. Stakeholders operating in the global air traffic management system have the need for graphical representations of aeronautical data (i.e., maps). This facilitates the safe, economical and efficient execution of their duties both in planning and during operations. There is a need for aeronautical aerodrome maps in support of integrated digital briefings. The maps can be used to ensure a common situation awareness on which to notify changes e.g. in the availability of the aerodrome infrastructure. This service satisfies this need by offering aeronautical aerodrome maps as regulated by ICAO Annex 15 - Aeronautical Information Services. The scope satisfies the EU Implementing Regulation 2021/116 - Common Project One. The aeronautical aerodrome maps may also used in other systems such as those used for surface management at aerodrome. A complete list of these is available as a High level description of the service offer. However, the service is not intended for in-cockpit use. |
|---|---|---|
| capabilities | The service provides aeronautical aerodrome maps based on service consumer requests (for example, for a specified geographical area or based on a specific data layer). The maps have standardised / harmonised symbols and annotations. | |
information exchange requirements |
Service Functions
DRAFT
Trace
| service functions | function | name | discover the layers that are available |
|---|---|---|---|
| description | A mechanism by which the consumer will know which data is available for the map; which layers. | ||
| real-world effect | Service consumer knows the content offered by the service. | ||
| function | name | get map | |
| description | A mechanism to specify which layers to include in the map based on their location and/or attributes and how to style them. | ||
| real-world effect | Service consumer receives the requested map. | ||
| function | name | get map based on filters | |
| description | A mechanism to specify conditions (queries) on the layers to include in the map. | ||
| real-world effect | Service consumer receives the requested map. | ||
| function | name | get map based on temporal filter | |
| description | A mechanism to specify the temporality conditions for the map. (Valid for a certain time, etc.) | ||
| real-world effect | Service consumer receives the requested map. |
Service Access and Use Conditions
TBD
Trace
service access and use conditions | legal constraints | 8.3.10: worth mentioning is related to the legal framework for data distribution. To really achieve all benefits from digital data distribution, all aspects related to copyright, use rights of data and liabilities need to be clearly stated. | |
|---|---|---|---|
service policies | business policy | TBD | |
operational policy | TBD | ||
technical policy | TBD | ||
service consumption constraints | TBD |
Security Constraints
TBD
Trace
security constraints | authentication | Consumer side authentication: TBD Provider side authentication: Authentication is required |
|---|---|---|
authorisation | ||
confidentiality | ||
integrity |
Quality of Service
TBD
Trace
quality of service | performance | capacity | |
|---|---|---|---|
| response time | <= 1 second | ||
| Time for Transmission | PJ15-11: <= 1 second | ||
| reliability | availability | >= 99.95 % | |
| recoverability | |||
| security | confidentiality | ||
| integrity | >= 99.999 % |
Quality of Data
DRAFT
Trace
| quality of data |
|
|---|
Source of Information
DRAFT
Trace
source of information | source | AIRPORT_OPERATOR |
|---|
Service Validation Information
TBD
Trace
service validation information | prototyping | The service was prototyped in SESAR |
|---|
Application Message Exchange Pattern
DRAFT
Trace
application message exchange pattern |
|---|
Service Behaviour
WORKING
Trace
service behaviour | typical behaviour | The service behaviour is in accordance with the Synchronous Request/Reply pattern detailed in Message Exchange Patterns: Identification Guidelines. The ISO 19128:2005 Geographic information - Web map server interface defines the basic behaviour. Synchronous Request/Reply
|
|---|
Service Monitoring
TBD
Trace
service monitoring | There is no expectation that a service monitoring mechanism is made available to service consumers. |
|---|
Service Interfaces
TBD
Trace
service interfaces | interface | name | PJ15-11: AccessMapService 8.3.10: AccessMapService |
|---|---|---|---|
| description | PJ15-11: AeronauticalInformationMapService access map interface. ISO 19128:2005 Geographic information - Web map server interface 8.3.10: The service interface is designed to be compatible with the ISO "IS 19128:2005 Geographic information - Web map server interface" standard. | ||
| provider/consumer side |
SWIM TI Profile and Interface Bindings
DRAFT
Trace
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile |
|---|---|---|
profile version | 1.1 | |
| selected service interface binding | WS_LIGHT | |
| selected network interface binding | ||
| supported optional requirements | The OGC Web Map Service 1.3.0 Interface Standard is used in the service implementation including all standardised operations for a Queryable WMS. |
Service Interface Protocols and Data Format
TBD
Trace
service interface protocols and data format | transport / messaging protocols | |
|---|---|---|
| data format | This is captured at Service Message level (see below). |
Service Operations
TBD
Trace
Service operations | operation | operation name | |
|---|---|---|---|
description | |||
messages | |||
| operation | operation name | ||
description | |||
messages |
Service Messages
DRAFT
Trace
Working notes
SAT 2022-12-13:
There is no need to consider the data as this is covered by the feature access service.
There is a need to look at how the content of the map is styled:
- SEAG-10 looked at symbology
- Annex 4 symbology not enough
- Make it look like Annex 14?
.. we can also say that the symbology language uses a standard e.g. SLD.
service messages | message | name | Aerodrome Map |
|---|---|---|---|
| description | This is the map that is generated as a result of the query to the service. It is in graphical format e.g. raster or vector. | ||
| type | Out | ||
| data format | This may be GIF, JPEG, etc. The desired output format may be included in the query to the service. | ||
| message | name | ||
| description | |||
| type | |||
| data format |
Information Definition (Minimum) and (Extended)
DRAFT
Trace
| information definition | The service offers layers based on features defined in the Aeronautical Information Exchange Model (AIXM 5.1.1). See the AMD data set column in Information aspects of the service. |
|---|
Filter Encoding
DRAFT
Trace
| filter encoding | The service sorts the data based on layers. The layers are based on the AMD features as given in the AMD data set column of Information aspects of the service. The layers are based on features that have a geographical footprint. The service offers a filter based on the ICAO location indicator of an aerodrome allowing all layers to be returned for that aerodrome. The service supports spatial, temporal and logical filtering based on (subset of the) the operators defined in the OGC Filter Encoding 2.0 Encoding Standard (equivalent to ISO 19143 - Geographic Information - Filter encoding). The temporal extension (WFS-TE) is used to support advanced temporal filtering. |
|---|
Machine-Readable Service Interface Definition
TBD
Trace
machine-readable service interface definition | reference |
|---|
Model View
TBD
Trace
model view | reference |
|---|
Abbreviations and Acronyms
TBD
Trace
| abbreviations and acronyms | abbreviation | code | SWIM |
|---|---|---|---|
| term | System Wide Information Management | ||
| abbreviation | code | ||
| term |