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 | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
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
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 |
---|---|---|
description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. | |
point of contact | swim@eurocontrol.int |
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. 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. This service satisfies this need by offering The aeronautical aerodrome maps as regulated by ICAO Annex 15 - Aeronautical Information Services. The scope satisfies 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 | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-140 |
service functions | function | name | Discover the layers that are available |
---|---|---|---|
description | The service consumer shall be able to discover the layers that are available for the map. | ||
real-world effect | Service consumer knows the content offered by the service. | ||
function | name | discover the layers that are availableGet map | |
description | A mechanism by which the consumer will know which data is available for the map; which layersThe service consumer shall be able to get the map. | ||
real-world effect | Service consumer knows the content offered by the servicereceives the requested map. | ||
function | name | getGet map based on filters | |
description | A mechanism The service consumer shall be able 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 Get map based on filterstemporal filter | |
description | A mechanism The service consumer shall be able to specify conditions (queries) on the layers to include in the mapthe temporality conditions for the map e.g. that it covers the current AIRAC. | ||
real-world effect | Service consumer receives the requested map. | ||
function | name | get Style map based on temporal filter | |
description | A mechanism The service consumer should be able to specify the temporality conditions for the map. (Valid for a certain time, etc.)how to style the layers in the map. | ||
real-world effect | Service consumer receives the map according to the requested mapstyles. |
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 he service may offer unauthenticated/public use. It In the case of authenticated use, the service shall ensure provider consumer authentication in accordance with SWIM TIYP through 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.It The service shall ensure consumer provider authentication in accordance with SWIM TIYP through EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate or the use of a username/password. |
---|---|---|
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 ensures shall ensure point-to-point confidentiality in accordance with SWIM TIYP through EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above. | |
integrity | The service ensures shall ensure point-to-point integrity in accordance with SWIM TIYP through EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above. |
Quality of Service
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-180 |
quality of service | performance | capacity | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | quality of service | performance | capacity |
---|---|---|---|---|---|---|
response time | Time for Transmission | reliability | availability | recoverabilityresponse 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 | Confidentiality shall be shall be ensured using SWIM TIYP The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. | ||||
integrity | Integrity shall be shall be ensured using SWIM TIYP The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. |
Quality of Data
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-185 |
quality of data | The data must satisfyaeronautical aerodrome map offered by the service shall be based on 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 aeronautical data that applies the AIXM 5.1.1 coding guidance is applied to the data. See:guidelines. This includes:
The AMD coding guidance shall be applied:aeronautical aerodrome map offered by the service shall be based on aeronautical data that follows:
|
---|
Source of Information
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-190 |
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., |
---|
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 shall be 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 shall be used for the basic behaviour. The typical behaviour is as follows: 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 Servicethe ISO 19128:2005 Geographic information - Web map server interface. | ||
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 (TI) Yellow Profile |
---|---|---|
profile version | 1.1 | |
selected service interface binding | WS_LIGHT | |
selected network interface binding | Shall The service 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 shall be 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 The service shall use TLS1.2 or later in accordance with SWIM TIYP: TLS1.2 or laterEUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile. | |
---|---|---|---|
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. This is according to the OGC Web Map Service 1.3.0 Interface Standard used to implement the service | ||
type | In | ||
data format | Defined by the implementation standard. |
Information Definition (Minimum) and (Extended)
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
information definition | The service offers shall offer GIS layers based on features that:
|
---|
Filter Encoding
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
filter encoding | The service sorts shall allow the selection of data based on GIS layers. The service offers shall offer 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 shall support 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 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. |
---|
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 |
Appendix A: References
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
This is not traced to a requirement. |
references | reference | title | CP1 |
---|---|---|---|
version | |||
description | |||
url | |||
document type | |||
reference | title | Commission Implementing Regulation (EU) 2017/37 | |
version | |||
description | |||
url | |||
document type | |||
reference | title | AIXM 5.1.1 coding guidance https://ext.eurocontrol.int/aixm_confluence/display/ACG/Common+coding+guidelines | |
version | |||
description | |||
url | |||
document type | |||
reference | title | https://aixm.aero/page/data-coding-guidelines | |
version | |||
description | |||
url | |||
document type | |||
reference | title | Use of Geography Markup Language (GML) for Aviation Data | |
version | |||
description | |||
url | |||
document type | |||
reference | title | AMD coding guidance | |
version | |||
description | |||
url | |||
document type | |||
reference | title | Message Exchange Patterns: Identification Guidelines. | |
version | |||
description | |||
url | |||
document type | |||
reference | title | ISO 19128:2005 Geographic information - Web map server interface / OGC Web Map Service 1.3.0 Interface Standard | |
version | |||
description | |||
url | |||
document type | |||
reference | title | AIXM 5 temporality model | |
version | |||
description | |||
url | |||
document type | |||
reference | title | Aeronautical Information Exchange Model (AIXM 5.1.1) | |
version | |||
description | |||
url | |||
document type | |||
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 | |||
document type | |||
reference | title | ses | |
version | |||
description | |||
url | |||
document type |
Appendix B: Information Definition for Aeronautical Aerodrome Map Request Service
Status | ||||
---|---|---|---|---|
|
GIS Layer (based on AIXM 5.1.1 features) | Aeronautical Aerodrome Map Request Service
| ||
---|---|---|---|
AerialRefuelling | |||
AeronauticalGroundLight | |||
AircraftGroundService | |||
AircraftStand | y | ||
AirportClearanceService | |||
AirportHeliportCollocation | |||
AirportHeliport | y | ||
AirportHotSpot | y | ||
AirportProtectionAreaMarking | |||
AirportSuppliesService | y | ||
AirspaceBorderCrossing | |||
Airspace | |||
AirTrafficControlService | |||
AirTrafficManagementService | |||
AltimeterSource | |||
AngleIndication | |||
ApproachLightingSystem | y | ||
ApronElement | y | ||
ApronLightSystem | y | ||
ApronMarking | |||
Apron | y | ||
ArrestingGear | y | ||
ArrivalFeederLeg | |||
ArrivalLeg | |||
AuthorityForAirspace | |||
Azimuth | |||
ChangeOverPoint | |||
CheckpointINS | |||
CheckpointVOR | |||
CirclingArea | |||
DeicingAreaMarking | |||
DeicingArea | y | ||
DepartureLeg | |||
DesignatedPoint | |||
DirectionFinder | |||
DistanceIndication | |||
DME | |||
Elevation | |||
FinalLeg | |||
FireFightingService | |||
FlightRestriction | |||
FloatingDockSite | |||
GeoBorder | |||
Glidepath | |||
GroundTrafficControlService | y | ||
GuidanceLineLightSystem | y | ||
GuidanceLineMarking | y | ||
GuidanceLine | y | ||
HoldingAssessment | |||
HoldingPattern | |||
InformationService | |||
InitialLeg | |||
InstrumentApproachProcedure | |||
IntermediateLeg | |||
Localizer | |||
MarkerBeacon | |||
MarkingBuoy | |||
MissedApproachLeg | |||
Navaid | |||
NavigationAreaRestriction | |||
NavigationArea | |||
NDB | |||
NonMovementArea | |||
ObstacleArea | |||
OrganisationAuthority | |||
PassengerLoadingBridge | |||
PassengerService | |||
PilotControlledLighting | |||
PrecisionApproachRadar | |||
PrimarySurveillanceRadar | |||
ProcedureDME | |||
RadarSystem | |||
RadioCommunicationChannel | y | ||
RadioFrequencyArea | |||
Road | y | ||
RouteDME | |||
RouteSegment | |||
Route | |||
RulesProcedures | |||
RunwayBlastPad | y | ||
RunwayCentrelinePoint | y | ||
RunwayDirectionLightSystem | y | ||
RunwayDirection | y | ||
RunwayElement | y | ||
RunwayMarking | y | ||
RunwayProtectAreaLightSystem | |||
RunwayProtectArea | y | ||
Runway | y | ||
RunwayVisualRange | |||
SafeAltitudeArea | |||
SDF | |||
SeaplaneLandingArea | |||
SeaplaneRampSite | |||
SearchRescueService | |||
SecondarySurveillanceRadar | |||
SignificantPointInAirspace | |||
SpecialDate | |||
SpecialNavigationStation | |||
SpecialNavigationSystem | |||
StandardInstrumentArrival | |||
StandardInstrumentDeparture | |||
StandardLevelColumn | |||
StandardLevelSector | |||
StandardLevelTable | |||
StandMarking | |||
SurveyControlPoint | y | ||
TACAN | |||
TaxiHoldingPositionLightSystem | y | ||
TaxiHoldingPositionMarking | y | ||
TaxiHoldingPosition | y | ||
TaxiwayElement | y | ||
TaxiwayLightSystem | y | ||
TaxiwayMarking | y | ||
Taxiway | y | ||
TerminalArrivalArea | |||
TouchDownLiftOffLightSystem | y | ||
TouchDownLiftOffMarking | |||
TouchDownLiftOffSafeArea | |||
TouchDownLiftOff | y | ||
Unit | |||
UnplannedHolding | |||
VerticalStructure | y | ||
VisualGlideSlopeIndicator | y | ||
VOR | |||
WorkArea | y |
Appendix C: Operational Needs
Status | ||||
---|---|---|---|---|
|
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. |
| Aircraft covers UAV. |
MILITARY_AIRSPACE_USER | Airspace User under the authority of a military organisation. |
| 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. |
| |
MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for military air traffic. |
| |
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). |
| |
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. | |
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). |
| |
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. |
| |
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. |