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
TBD
Trace
geographical extent of information | ... |
---|
Service Categories
TBD
Trace
service categories | category | category name | Regulated Information Exchange |
---|---|---|---|
value | AERONAUTICAL_INFORMATION_EXCHANGE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeRegulatedInformationExchangeType | ||
category | category name | Business Activity | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeBusinessActivityType | ||
category | category name | intended service consumer | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType | ||
category | category name | intended service consumer | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType |
Service Standard Reference
TBD
Trace
service standard reference | reference | 8.3.10: Annex 15 and Annex 4 apply |
---|---|---|
implemented options | ||
deviations/additions |
Operational Environment
WORKING
Trace
operational environment | operational needs | 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 will provide the graphical representations needed to support these digital briefing concepts. 8.3.10: The service provides aeronautical information which main purpose is enabling a common infrastructure picture (airspace availability, airport infrastructure availability, etc.) to be used in planning and during operations. |
---|---|---|
capabilities | 8.3.10: The AeronauticalInformationMap service will have the capability to disseminate all aeronautical maps properly symbolized and annotated. | |
information exchange requirements |
Service Functions
WORKING
Trace
service functions | function | name | 8.3.10: -A mechanism by which the consumer will know which data is available for the map; which features/layers. -A mechanism to specify which features/layers to include in the map based on their location and/or attributes. -A mechanism to specify conditions (queries) on the features/layers to include in the map. -A mechanism to specify the temporality conditions for the map. (Valid for a certain time, etc.) |
---|---|---|---|
description | |||
real-world effect | |||
function | name | ||
description | |||
real-world effect |
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
TBD
Trace
quality of data |
---|
Source of Information
TBD
Trace
source of information | source |
---|
Service Validation Information
TBD
Trace
service validation information | prototyping | The service was prototyped in SESAR |
---|
Application Message Exchange Pattern
TBD
Trace
application message exchange pattern | Synchronous Request Reply |
---|
Service Behaviour
TBD
Trace
service behaviour | typical behaviour | 8.3.10: The AeronauticalInformationMap service is stateless; the diagram below depicts the simple service dynamic behaviour. |
---|
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
TBD
Trace
SWIM TI profile and interface bindings | profile name | TI Yellow Profile specification |
---|---|---|
profile version | Edition Number 1.0 | |
selected service interface binding | ||
selected network interface binding | ||
supported optional requirements |
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
TBD
Trace
service messages | message | name | |
---|---|---|---|
description | |||
type | |||
data format | |||
message | name | 8.3.10: bitmap representing the map | |
description | |||
type | |||
data format |
Information Definition (Minimum) and (Extended)
TBD
Trace
information definition | PJ15-11: the latest version of the AIXM standard 8.3.10: The AeronauticalInformationMap service relies on AIXM 5.1 standard for data exchange of aeronautical information features. 8.3.10: maps as raster images |
---|
Filter Encoding
TBD
Trace
filter encoding | 8.3.10: support layer filtering. The AeronauticalInformationMap service imposes a number of rules on the available layers the service must support and the layers properties. The layers must represent directly a number of AIXMFeatures. Additional layers can be supported. 8.3.10: timeSampleDimension AMIS: The EntityItem MandatoryLayer has been introduce to standardise which layers the AMIS service must support and gives some idea as to how the layers should be represented on the map. AMIS: FilterAllByICAOIdentifier, it supplies a single airport ICAO identifier. |
---|
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 |