Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Info | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This template allows for the documentation of service definitions based on the requirements found at: /wiki/spaces/SCOI/pages/59605116 General requirements to remember:
|
Table of Contents | ||||
---|---|---|---|---|
|
Info | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
Service Definition Identification
Status | ||
---|---|---|
|
Info | ||
---|---|---|
| ||
service definition identification | title | Service Definition for Aeronautical Aerodrome Maps Service |
---|---|---|
edition | 00.00.01 | |
reference date | 2022-04-27 |
Service Identification
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
service identification | service name | Aerodrome Map Request Service |
---|
Service Abstract
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
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
Status | ||
---|---|---|
|
Info | ||
---|---|---|
| ||
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
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
Info | ||
---|---|---|
| ||
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
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-095, SWIM-DEFN-100 |
Service Standard Reference
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-120 |
service standard reference | reference | |
---|---|---|
implemented options | ||
deviations/additions |
Operational Environment
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-130 |
Info | ||
---|---|---|
| ||
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). | |
information exchange requirements |
Service Functions
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-140 |
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
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-150 |
Info | ||
---|---|---|
| ||
SAT 2023-01-30: Agreed to leave empty as it is not possible to give a precise requirement. |
service access and use conditions | legal constraints | ||
---|---|---|---|
service policies | business policy | ||
operational policy | |||
technical policy | |||
service consumption constraints |
Security Constraints
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-160 |
security constraints | authentication | The service may offer unauthenticated/public use. It shall ensure provider authentication in accordance with SWIM TIYP through X.509 certificate. It shall ensure consumer authentication in accordance with SWIM TIYP through X.509 certificate or the use of a username/password. |
---|---|---|
authorisation | The service shall ensure that satisfactory authorisation is put in place according to SWIM-TIYP-0070. | |
confidentiality | The service ensures point-to-point confidentiality in accordance with SWIM TIYP through Transport Layer Security (TLS) 1.2 or above. | |
integrity | The service ensures point-to-point integrity in accordance with SWIM TIYP through Transport Layer Security (TLS) 1.2 or above. |
Quality of Service
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-180 |
Info | ||
---|---|---|
| ||
SAT 2023-01-30: Agreed to leave empty (except the need for confidentiality and integrity) as it is not possible to give a precise requirement. |
quality of service | performance | capacity | |
---|---|---|---|
response time | |||
Time for Transmission | |||
reliability | availability | ||
recoverability | |||
security | confidentiality | Confidentiality shall be shall be ensured using SWIM TIYP bindings. | |
integrity | Integrity shall be shall be ensured using SWIM TIYP bindings. |
Quality of Data
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-185 |
quality of data |
|
---|
Source of Information
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-190 |
source of information | source | AIRPORT_OPERATOR |
---|
Service Validation Information
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-200 |
Info | ||
---|---|---|
| ||
SAT 2023-01-30: Agreed to leave empty (except the need for confidentiality and integrity) as it is not possible to give a precise answer. |
service validation information | prototyping |
---|
Application Message Exchange Pattern
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-210 |
application message exchange pattern |
---|
Service Behaviour
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-220 |
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
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-230 |
service monitoring | A service monitoring mechanism shall be made available to service consumers. |
---|
Service Interfaces
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-240 |
service interfaces | interface | name | nameofservice + Interface |
---|---|---|---|
description | The interface is used to group the operations offered by the Web Map Service. | ||
provider/consumer side | Provider side |
SWIM TI Profile and Interface Bindings
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-250, SWIM-DEFN-255 |
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 | Shall use the network bindings of the SWIM TIYP. See 3.1.2 for the options: IPV4, etc. | |
supported optional requirements | The OGC Web Map Service 1.3.0 Interface Standard is used in the service implementation All standardised operations for Basic WMS shall be implemented All standardised operations for Queryable WMS should be implemented Other operations such as getLegend may be implemented |
Service Interface Protocols and Data Format
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-260 |
service interface protocols and data format | transport / messaging protocols | Shall be in accordance with SWIM TIYP: TLS1.2 or later | |
---|---|---|---|
data format |
|
Service Operations
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-270 |
Info | ||
---|---|---|
| ||
SAT 2023-01-30: Using WMS standard names so no need to document further. |
Service operations | operation | operation name | |
---|---|---|---|
description | |||
messages | |||
operation | operation name | ||
description | |||
messages |
Service Messages
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-280 |
Info | ||
---|---|---|
| ||
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:
.. 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 on the server as a result of the query to the service. It is in graphical format e.g. raster or vector. It may be styled according to a service layer description (SLD). | ||
type | Out | ||
data format | This may be GIF, JPEG, etc. The desired output format may be included in the query to the service. A queryable WMS allows access to the information on the map. It shall be in AIXM 5.1.1. format. Other formats such as simple GML features, SHAPE files, GeoJSON may be supported. | ||
message | name | ||
description | |||
type | |||
data format |
Information Definition (Minimum) and (Extended)
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
information definition | The service offers GIS layers:
See the AMD data set column in Information aspects of the service. |
---|
Filter Encoding
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
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
Status | ||
---|---|---|
|
Info | ||
---|---|---|
| ||
machine-readable service interface definition | reference |
---|
Model View
Status | ||
---|---|---|
|
Info | ||
---|---|---|
| ||
model view | reference |
---|
Abbreviations and Acronyms
Status | ||
---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-350 |
abbreviations and acronyms | abbreviation | code | SWIM |
---|---|---|---|
term | System Wide Information Management | ||
abbreviation | code | ||
term |