Insert excerpt |
---|
SCOI:Task Status | SCOI:Task Status | nopanel | true |
---|
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:
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. | - |
Info |
---|
|
- No work has started - Content is being worked on, comments discussed - Draft is ready, comments resolved Status |
---|
colour | Green |
---|
title | REVIEWED |
- Group has reviewed, edited the final draft Status |
---|
colour | Blue |
---|
title | AGREED |
- Content is finalised and Insert excerpt |
---|
| SCOI:Task Status |
---|
| SCOI:Task Status |
---|
nopanel | true |
---|
|
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: 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. | - |
|
Info |
---|
|
- - No work has started
- - Content is being worked on, comments discussed
- - Draft is ready, comments resolved
- - Group has reviewed, edited the final draft
- - Content is finalised and agreed
|
Info |
---|
|
Some fields in the template are left empty. This means that no requirement is specified for it and it is left to the service provider to decide. |
Service Definition Identification
service definition identification | title | Service definition for the Aeronautical Aerodrome Map Request Service |
---|
edition | 00.00.01 |
---|
reference date | 2023-02-09 |
---|
Service Identification
service identification | service name | Aeronautical Aerodrome Map Request Service |
---|
Service Abstract
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
service definition provider | name | EUROCONTROL |
---|
description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. |
---|
point of contact | swim@eurocontrol.int |
---|
Info |
---|
|
This field is left empty. This means that no requirement is specified for it and it is left to the service provider to decide. |
geographical extent of information | Service Categoriesprovides a capability for on-request aeronautical aerodrome maps that are generated from aerodrome mapping data.
Note: Aerodrome mapping data are based on the ICAO Annex 15 notion of aerodrome mapping data and the related aerodrome mapping datasets. Aeronautical aerodrome maps are a graphical representation of aerodrome mapping data.
The service generates aeronautical aerodrome maps from current or next AIRAC cycle aerodrome mapping data available in the service back-end.
The service encodes the aeronautical aerodrome maps in a graphical format.
The consumer of the service can specify in the aerodrome map request:
- the individual aerodrome,
- the aerodrome map layers to be included, and
- the geographical area of interest.
The provided aeronautical aerodrome map is used in visualisation contexts as a backdrop map. The service capability enables various use cases (e.g. Digital NOTAM overlay in ePIB applications).
The Aeronautical Aerodrome Map Request Service definition provides a common specification for the implementation of Aeronautical Aerodrome Map Request Service instances that conform with EU Implementing Regulation 2021/116 - Common Project One.
Note: In the context of European SWIM deployment the Aeronautical Aerodrome Map Request Service capability realizes the SESAR Deployment Programme Aerodrome Mapping Service – Map part. The capability to request airport layout features (i.e. aerodrome mapping data) is realized by the Aeronautical Information Request Service. |
Service Definition Provider
Info |
---|
|
This field is left empty. |
geographical extent of information |
|
---|
Service Categories
Service Service Standard Reference
Info |
---|
|
This field is left empty. No service standard was identified. |
service standard reference
| reference |
|
---|
implemented options |
|
---|
deviations/additions |
|
---|
Operational Environment
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 list of these is available in Appendix C. This service satisfies these by offering aeronautical aerodrome maps as regulated by ICAO Annex 15 - Aeronautical Information Services. However, the service is not intended for in-cockpit use. The aeronautical aerodrome maps offered by the service satisfy 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 |
---|
colour | Yellow |
---|
There is a need for aeronautical aerodrome maps in support of integrated digital briefing applications (e.g. ePIB). Aerodrome maps can be used to ensure common situational awareness using them as backdrops in applications that display changes in the availability of the aerodrome infrastructure (e.g. Digital NOTAM overlay). Another example is the use of aerodrome maps in applications in support of aerodrome surface management.
A list of aerodrome map related operational needs is available in Appendix C. The aeronautical aerodrome maps offered by the service satisfy 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, based on a specific map layer or for a specific aerodrome). |
---|
information exchange requirements | |
---|
Service Functions
service functions
| function | name | Discover the layers that are availablecapabilities
|
---|
description | The service consumer shall be able to discover the layers that are available for the mapcapabilities exposed by the service such as layers and styles. |
---|
real-world effect | Service The service consumer knows the content offered by capabilities of the service. |
---|
function | name | Request aeronautical aerodrome map |
---|
description | The service consumer shall be able to request the aeronautical aerodrome map and be able to specify select which layers to include in the mapon it. |
---|
real-world effect | Service The service consumer receives the requested map. |
---|
function | name | Request map based on filtersaeronautical aerodrome map by geographic area |
---|
description | The service consumer shall be able to specify the filters (location and/or attributes) select the geographic area to be used when generating the map. |
---|
real-world effect | Service The service consumer receives the requested map. |
---|
function | name | Request map based on temporalityaeronautical aerodrome map by identifier |
---|
description | The service consumer shall be able to specify the temporality (current AIRAC or next AIRAC) select an individual aerodrome to be used when generating the map. Note: The service shall support ICAO aerodrome location indicators as a minimum. |
---|
real-world effect | The service consumer receives the requested map. |
---|
function | name | Request aeronautical aerodrome map by AIRAC cycle |
---|
description | The service consumer shall be able to specify the AIRAC cycle (current and next) of the aerodrome map request. |
---|
real-world effect | Service consumer receives the requested map. |
---|
Service Access and Use Conditions
Info |
---|
|
This field is left empty. This means that no requirement is specified for it and it is left to the service provider to decide. |
service access and use conditions
| legal constraints |
|
|
---|
service policies | business policy | Due care should be taken if an application consuming the service is used in cockpit/flight. |
---|
operational policy |
|
---|
technical policy |
|
---|
service consumption constraints |
|
|
---|
Security Constraints
security constraints
| authentication | The service may offer unauthenticated/public use. In the case of authenticated use, the service shall ensure consumer authentication in accordance with the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate or the use of a username/password. The service shall ensure provider authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate. |
---|
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
quality of service | performance | capacity | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. |
---|
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. |
---|
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. |
---|
integrity | The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. |
---|
Quality of Data
quality of data | The aeronautical aerodrome map offered by the service shall be based on generated from aeronautical data that satisfies the applicable sections of Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 The aeronautical aerodrome map offered by the service shall be based on generated from aeronautical data that applies the AIXM 5.1.1 coding guidelines. This includes: The aeronautical aerodrome map offered by the service shall be based on generated from aeronautical data that follows: |
---|
source of information | source | The aeronautical aerodrome map offered by the service shall be based on aeronautical data received from the appropriate authorised originating sources, e.g.,. For example: |
---|
service validation information |
---|
|
This field is left empty. No prototyping or other validation has taken place. However, the description | The service definition is based |
---|
upon on work carried out in SESAR.
A similar service | validation informationprototyping | was implemented in the context of the Airport Toolkit per-operational trial. (ref)
No further validation has taken place on this service definition. |
---|
Application Message Exchange Pattern
Service Behaviour
service behaviour | typical behaviour | The service behaviour shall be in accordance with the Synchronous Request/Reply pattern detailed in Message Exchange Patterns: Identification Guidelines. The OGC Web Map Service 1.3.0 Interface Standard shall be used for the basic behaviour. The typical behaviour is as follows: Synchronous Request/Reply- 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 aeronautical aerodrome map, the reply message, is sent from the service to the service consumer.
|
---|
Service Monitoring
service monitoring | A service monitoring mechanism shall be made available to service consumers. |
---|
Service Interfaces
service interfaces | interface | name | Aeronautical Aerodrome Map Request Service Interface |
---|
description | The interface is used to group the operations offered by the OGC Web Map Service 1.3.0 Interface Standard. |
---|
provider/consumer side | Provider side |
---|
SWIM TI Profile and Interface Bindings
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 OGC Web Map Service 1.3.0 Interface Standard shall be used. 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
| transport / messaging protocols | The service shall use TLS1.2 or later in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile. |
---|
data format | Info |
---|
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
Info |
---|
|
The OGC Web Map Service 1.3.0 Interface Standard is used to implement the service operations. The table below illustrates how these would look in the context of this service. |
Service operations
| operation
| operation name | GetMap |
---|
description | The GetMap operation returns an Aeronautical Aerodrome Map that satisfies the query expressions specified in the GetMap Request message. |
---|
messages | Request, Aeronautical Aerodrome Map |
---|
Service Messages
service messages
Info |
---|
|
The OGC Web Map Service 1.3.0 Interface Standard details the basic messages such as request and response messages. The table below provides extra details for the Aeronautical Aerodrome Map. |
service messages
| message | name | Aeronautical Aerodrome Map |
---|
description | This is the map that is generated on the server as a result of the GetMap query to the service.
|
---|
direction | Out |
---|
data format | 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. |
---|
direction | Out |
---|
data format | It is in 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. This is according to the OGC Web Map Service 1.3.0 Interface Standard used to implement the service |
---|
direction | In |
---|
data format | Defined by the implementation standard. |
---|
is in a graphical format supported by the OGC Web Map Service 1.3.0 Interface Standard. The desired output format may be included in the query to the service.
If the queryable WMS is implemented, it allows access to the information on the map. The resulting information shall be based on the AIXM 5.1.1 exchange language. |
information definition | The service shall offer aeronautical aerodrome map layers based on the graphical representation of aerodrome mapping data. Note: The content of aerodrome map layers is the information service payload. Aerodrome map layers exposed by the service shall correspond to AIXM 5.1.1 aerodrome mapping data feature types that contain geospatial information. See Appendix B. When an aerodrome map layer exposed by the service corresponds to one AIXM 5.1.1 aerodrome mapping feature then the proposed layer names in Appendix B should be used to expose the capabilities of the service. When an aerodrome map layer exposed by the service combines multiple AIXM 5.1.1 aerodrome mapping data feature types into a single aerodrome map layer then an operationally significant name should be use used for the aerodrome map layer (e.g. aerodrome movement area). When the service consumer requests a combination of layers exposed by the service then the generation of the aeronautical aerodrome map shall be according to the OGC Web Map Service 1.3.0 Interface Standard.
|
---|
Filter Encoding
Filter Encoding
information definition | The service shall offer GIS layers based on features that: - have a geographical footprint and
- are defined in the Aeronautical Information Exchange Model (AIXM 5.1.1) and
- are included Appendix B (i.e., in the aerodrome mapping data set defined by ICAO, driven by AMDB industry requirements).
|
---|
Info |
---|
|
This field is left empty. The service allows for the selection of layers based on the information definition. No further filtering is required. |
Machine-Readable Service Interface Definition
Machine-Readable Service Interface Definition
Info |
---|
|
This field is left empty. No machine-readable service interface definition is provided. |
machine-readable service interface definition | reference | Model View
statusfilter encoding | The service shall allow the selection of data based on layers. If the service covers multiple aerodromes, the service shall offer a filter based on the ICAO location indicator of an aerodrome allowing all the layers to be returned for that aerodrome. If the service covers multiple aerodromes, the service shall support spatial and logical filtering based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard. The service shall support 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.
|
---|
Info |
---|
|
This field is left empty. No machine-readable service interface definition is provided. |
machine-readable service interface definition | reference |
|
---|
Model View
Abbreviations and Acronyms
abbreviations and acronyms
| abbreviation | code | AIRAC |
---|
term |
|
---|
abbreviation | code | AIXM |
---|
term | Aeronautical Information Exchange Model |
---|
abbreviation | code | ATM |
---|
term | Air Traffic Management |
---|
abbreviation | code | EPSG |
---|
term |
|
---|
abbreviation | code | GIF |
---|
term |
|
---|
abbreviation | code | GIS |
---|
term |
|
---|
abbreviation | code | ICAO |
---|
term |
|
---|
abbreviation | code | JPEG |
---|
term |
|
---|
abbreviation | code | OGC |
---|
term | Open Geospatial Consortium |
---|
abbreviation | code | PNG |
---|
term |
|
---|
abbreviation | code | SLD |
---|
term | Styled Layer Descriptor |
---|
abbreviation | code | SWIM |
---|
term | System Wide Information Management |
---|
abbreviation | code | TIFF |
---|
term |
|
---|
abbreviation | code | TLS |
---|
term | Transport Layer Security |
---|
abbreviation | code | WGS |
---|
term |
|
---|
abbreviation | code | WMS |
---|
term | Web Map Service |
---|
abbreviation | code | XML |
---|
term | Extensible Markup Language |
---|
Appendix A: References
Info |
---|
|
This is not traced to a requirement. |
Layer | |
---|
AircraftStand | Point
Polygonreferences
| reference
| title | EU Implementing Regulation 2021/116 - Common Project One |
---|
version |
|
---|
description | The Aeronautical Dataset Services constitute a family of services capable of providing, discovering and retrieving ICAO Annex 15 digital datasets. The information offered by the Aeronautical Information Request Service is aligned with that found in the Aeronautical Dataset Services specification in order to ensure consistency between the two services. |
---|
url | https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32021R0116 |
---|
document type |
|
---|
reference | title | Commission Implementing Regulation (EU) 2017/37 |
---|
version | 1 March 2017 |
---|
description | Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 laying down common requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011, (EU) No 1035/2011 and (EU) 2016/1377 and amending Regulation (EU) No 677/2011. |
---|
url | https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32017R0373 |
---|
document type |
|
---|
reference | title | AIXM Coding - Common coding guidelines |
---|
version |
|
---|
description | Coding guidelines for complex AIXM properties such as geometry, schedules, annotations, etc. It also contains general coding guidelines which are not for a particular subject area but applicable for all AIXM features. |
---|
url | https://ext.eurocontrol.int/aixm_confluence/display/ACG/Common+coding+guidelines |
---|
document type |
|
---|
reference | title | Data coding guidelines |
---|
version |
|
---|
description | A set of coding guidelines to promote the interoperability of AIXM 5.1.1 formatted data. |
---|
url | https://aixm.aero/page/data-coding-guidelines |
---|
document type |
|
---|
reference | title | (ICAO) Aerodrome Mapping Data Sets - Supporting Material |
---|
version |
|
---|
description | Supporting material for ICAO Aerodrome Mapping Data Sets. |
---|
url | https://ext.eurocontrol.int/aixm_confluence/display/ACGAMD/%28ICAO%29+Aerodrome+Mapping+Data+Sets+-+Supporting+Material |
---|
document type |
|
---|
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 | OGC Web Map Service 1.3.0 Interface Standard (equivalent to ISO 19128:2005 Geographic information - Web map server interface) |
---|
version |
|
---|
description |
|
---|
url | https://www.ogc.org/docs/is.ogc.org/docs/is |
---|
document type |
|
---|
reference | title | AIXM 5 Temporality Model |
---|
version | 1.1 |
---|
description | Explains the AIXM temporality concept |
---|
url | https://aixm.aero/sites/aixm.aero/files/imce/AIXM511/aixm_temporality_1.1.pdf |
---|
document type |
|
---|
reference | title | AIXM 5 Temporality ModelAeronautical Information Exchange Model (AIXM) |
---|
version | 5.1.1 |
---|
description | Explains the AIXM temporality concept |
|
---|
url | https://www.aixm.aero/sitesschema/aixm5.1.aero/files/imce/AIXM511/aixm_temporality_1.1.pdf1/AIXM_Features.xsd |
---|
document type | INFORMATION_DEFINITION |
---|
reference | title | aerodrome mapping data set defined by ICAO |
---|
version |
|
---|
description |
|
---|
url |
|
---|
document type |
|
---|
reference | title | AMDB industry requirements. |
---|
version |
|
---|
description |
|
---|
url |
|
---|
document type |
|
---|
reference | title | Aeronautical Information Exchange Model (AIXM) | version | 5.1.1OGC Filter Encoding 2.0 Encoding Standard (equivalent to ISO 19143 - Geographic Information - Filter encoding). |
---|
version |
|
---|
description |
|
---|
url | https://www.aixmogc.aeroorg/schema/5.1.1/AIXM_Features.xsddocs/is |
---|
document type | INFORMATION_DEFINITION |
---|
reference | title | aerodrome mapping data set defined by ICAO |
---|
version | description | url | document type | reference | title | AMDB industry requirements. |
---|
version | description | url | document type | reference | title | OGC Filter Encoding 2.0 Encoding Standard (equivalent to ISO 19143 - Geographic Information - Filter encoding). |
---|
version | description | url | https://www.ogc.org/docs/is |
---|
document type | reference | title | European ATM Service Description for the AerodromeMapInformation Service |
---|
version | description | This document describes the Aerodrome Map Information Service (AMIS) and the relevant architectural elements. The Service aims to publish Aerodrome Map Feature Types as described by EUROCAE in standard ED99C and Aerodrome Map Types as described by EUROCAE in standard ED119B . The service is named Aerodrome Map Information Service, abbreviated AMIS and was identified with the standard operations for the OGC WFS and WMS |
---|
url | document type |
|
|
---|
reference | title | European ATM Service Description for the AerodromeMapInformation Service |
---|
version |
|
---|
description | This document describes the Aerodrome Map Information Service (AMIS) and the relevant architectural elements. The Service aims to publish Aerodrome Map Feature Types as described by EUROCAE in standard ED99C and Aerodrome Map Types as described by EUROCAE in standard ED119B . The service is named Aerodrome Map Information Service, abbreviated AMIS and was identified with the standard operations for the OGC WFS and WMS |
---|
url |
|
---|
document type |
|
---|
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.
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.
Layer | AIXM 5.1.1 feature | | ED99-AMXM Feature |
---|
AircraftStandLocation | AircraftStand | Point | ParkingStandLocation |
---|
AircraftStandArea | AircraftStand | Polygon | ParkingStandArea |
---|
| AirportHeliport | Point (from Aerodrome Reference Point) |
|
---|
| AirportHotSpot | Polygon |
|
---|
| AirportSuppliesService |
|
|
---|
| ApproachLightingSystem |
|
|
---|
| ApronElement | Polygon |
|
---|
| ApronLightSystem |
|
|
---|
| Apron |
|
|
---|
| ArrestingGear |
|
|
---|
| DeicingArea |
|
|
---|
| GroundTrafficControlService |
|
|
---|
| GuidanceLineLightSystem |
|
|
---|
| GuidanceLineMarking |
|
|
---|
| GuidanceLine |
|
|
---|
| RadioCommunicationChannel |
|
|
---|
| Road | Polygon |
|
---|
| RunwayBlastPad | Polygon |
|
---|
| RunwayCentrelinePoint |
|
|
---|
| RunwayDirectionLightSystem |
|
|
---|
| RunwayDirection |
|
|
---|
| RunwayElement | Polygon |
|
---|
| RunwayMarking |
|
|
---|
| RunwayProtectArea |
|
|
---|
| Runway |
|
|
---|
| SurveyControlPoint |
|
|
---|
| TaxiHoldingPositionLightSystem |
|
|
---|
| TaxiHoldingPositionMarking |
|
|
---|
| TaxiHoldingPosition |
|
|
---|
| TaxiwayElement | Polygon |
|
---|
| TaxiwayLightSystem |
|
|
---|
| TaxiwayMarking |
|
|
---|
| Taxiway |
|
|
---|
| TouchDownLiftOffLightSystem |
|
|
---|
| TouchDownLiftOff |
|
|
---|
| VerticalStructure |
|
|
---|
| VisualGlideSlopeIndicator |
|
|
---|
| WorkArea | Polygon |
|
---|
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.
By service consumer role
Stakeholder/Role | Description of stakeholder/role | Needs for Aerodrome Maps | 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. | - Generate graphical representations needed to support digital briefing concepts.
- Have an up-to-date backdrop for dynamic layers (see SDP).
| Aircraft covers UAV.
|
---|
MILITARY_AIRSPACE_USER | Airspace User under the authority of a military organisation. | - Generate digital representation of ground operations
- Generate graphical representations needed to support digital briefing concepts.
- Have an up-to-date backdrop for dynamic layers (see SDP).
| 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 visualization 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.
|
|
---|
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 visualization 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). | - Generate digital representation of ground 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. |
| No needs have been identified. |
---|
COMMUNICATION_NAVIGATION_AND_ SURVEILLANCE_SERVICE_PROVIDER | A provider of CNS services. |
| No needs have been identified. |
---|
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). | - Update EFB - electronic flight bags
|
|
---|
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. |
| No needs have been identified. |
---|
AIRPORT_OPERATOR | The civilian or military agency, group or individual which exercises control over the operations of the civil airport or military airfield. | - Improved common situational awareness
- Ensure same digital representation of reality e.g. in low visibility operations (LVO)
- 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. |
| No needs have been identified. |
---|
MILITARY_DEFENCE_CENTRE | A military defence centre. Note: these centres, e.g., check for diplomatic clearance. |
| No needs have been identified. |
---|