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 the Aeronautical Aerodrome Map Request Service |
---|---|---|
edition | 00.00.01 | |
reference date | 2023-02-09 |
Service Identification
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
service identification | service name | Aeronautical Aerodrome Map Request Service |
---|
Service Abstract
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
service abstract | The Aeronautical Aerodrome Map Request Service allows the service consumer to get an aeronautical aerodrome map. The map is generated using up-to-date and accurate aeronautical information for the features at aerodromes. The content of the map can be in the request e.g. based on GIS layer and the location of the feature. The map can be used to support various operations such as serving as a baseline map for dynamic data operations. |
---|
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 | ||
---|---|---|
| ||
geographical extent of information |
---|
Service Categories
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-095, SWIM-DEFN-100 |
service categories | category | category name | regulated information exchange |
---|---|---|---|
value | AERONAUTICAL_INFORMATION_EXCHANGE | ||
scheme | |||
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 | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | intended service provider | |
value | AERONAUTICAL_INFORMATION_SERVICE_PROVIDER | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | service type | |
value | AERONAUTICAL_AERODROME_MAP_ACCESS_SERVICE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeServiceType (for the moment use https://ext.eurocontrol.int/swim_confluence/display/SCOI/Service+Categories+-+Service+Type). |
Service Standard Reference
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-120 |
service standard reference | reference | |
---|---|---|
implemented options | ||
deviations/additions |
Operational Environment
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-130 |
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". 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. 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. 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. |
---|---|---|
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 |
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 |
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 |
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 | Aeronautical Aerodrome Map Request Service 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 |
Service operations | operation | operation name | |
---|---|---|---|
description | |||
messages | |||
operation | operation name | ||
description | |||
messages |
Service Messages
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-280 |
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 serves a baseline (as per the AIXM 5 temporality model). Due care shall be taken to ensure the layers on the map are visible. For example, this may mean that GIS layers with a polygon geometry are below those with a a line geometry. It may be styled and/or labelled according to a service layer description (SLD) and should ensure an uncluttered map. It shall use EPSG:3857 (https://en.wikipedia.org/wiki/Web_Mercator_projection) as a minimum for its projection. The service consumer may specify another projection that is made available. Note that the projection does not alter the data. It still uses WGS-84 according Annex 15. | ||
type | Out | ||
data format | It is in raster graphical format e.g. GIF, JPEG, PNG, TIFF, 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. The resulting information shall be based on the AIXM 5.1.1 exchange language. | ||
message | name | Request | |
description | The request to the service. | ||
type | In | ||
data format | Defined by the implementation standard. |
Information Definition (Minimum) and (Extended)
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
information definition | The service offers GIS layers based on features that:
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 GIS layers. The service offers a filter based on the ICAO location indicator of an aerodrome allowing all the GIS 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 service supports a filter based on the AIRAC cycle allowing the service consumer to select a map for the current AIRAC cycle and the next AIRAC cycle. |
---|
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 |
References
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
This is not traced to a requirement. |
references | reference | title | |
---|---|---|---|
version | |||
description | |||
url | |||
document type | |||
reference | title | ||
version | |||
description | |||
url | |||
document type |