OGC Aviation DWG Bonn Hubert LEPORI EUROCONTROL DSRCMNIM

OGC Aviation DWG - Bonn Hubert LEPORI EUROCONTROL – DSR/CMN/IM 01 -March-2011 The European Organisation for the Safety of Air Navigation

Agenda • Vote on following documents to become public discussion papers (Hubert Lepori) • 10 -195 Requirements for Aviation Metadata • 10 -196 r 1 Guidance on the Aviation Metadata Profile • Update on OGC Aviation-related activities • OWS-8 scope and deliverables (Nadine Alameh) • Update on SAA OGC Pilot (Johannes Echterhoff) • Use of OGC B-XML for on-board airport mapping and navigation databases (Hubert Lepori) • Discussion - Meeting AIM’s temporality requirements in OGC standards: Limitations and recommendations (All) • Technical working session to review and edit the GML Profile for AIXM (Eduard Porosnicu) Enter here your presentation title 2

Requirements for Aviation Metadata Guidance on the Aviation Metadata Profile The European Organisation for the Safety of Air Navigation

Background • October 2010: 2 -day Aviation DWG technical meeting in Brussels • Metadata profile for Aviation • GML profile for Aviation Thanks again to all the participants !!! • Dec. 2010: draft discussion papers uploaded to the OGC portal and send for initial review • No comment received so far Enter here your presentation title 4

Metadata Requirements for Aviation ICAO Annex 15 (Ed. 13) Requirement/Source Annex 15 ADQ INSPIRE IR 5. 1. 1 Resource Title ADQ rules 5. 1. 2 Resource Abstract 5. 1. 3 Resource Language 5. 2. 1 Topic Category 5. 3. 1 Geographic Bounding Box 5. 3. 2 Spatial Reference System 5. 4. 1 Temporal Extent 5. 4. 2 Date of Publication INSPIRE 5. 4. 3 Date of Last Revision 5. 4. 4 Date of Creation 5. 4. 5 Temporal Reference System 5. 5. 1 Lineage 5. 5. 2 Accuracy of Numerical Data 5. 5. 3 Cyclic Redundancy Check Practical feedback: OWS-6. . . 5. 6. 1 Conditions Applying to Access and Use 5. 6. 2 Limitations on Public Access 5. 7. 1 Responsible Party 5. 7. 2 Responsible Party Role 5. 8. 1 Metadata Point of Contact Enter here your presentation title 5. 8. 2 Metadata Date 5. 8. 3 Metadata Language 5 OWS-6

Guidance on the Aviation Metadata Profile • This paper explains how to map the Requirements for Aviation Metadata into an ISO 19115 metadata profile. ISO 19115 Enter here your presentation title 6

Aviation Metadata • Does the group agree to endorse those documents as public discussion papers ? • Remaining questions (if the answer is yes): • Editor of the document ? • Template to be used ? Enter here your presentation title 7

Use of OGC B-XML for on-board airport mapping and navigation databases The European Organisation for the Safety of Air Navigation

B-XML – OGC Binary XML spec. • Arinc 816 - Database for Airport Navigation System • Uses OGC Binary-XML Encoding Specification Version 0. 0. 8. (OGC 03 -002 r 8, Version 0. 0. 8, 2003 -05 -07) • Already used operationally on-board! Source: Thales/Airbus – SESAR WP 9. 31 Enter here your presentation title 9

Arinc 424 A-NDBX specification AI P Navigation data AI P Arinc 424 A NDBX • Arinc 424 A/NDBX working group successfully implemented a prototype indexed B-XML for FMS navigation database. Enter here your presentation title 10

B-XML within OGC • If the B-XML topic is revived within OGC: • The specific requirements of the avionics systems (ANS, FMS…) should be taken into account • Need to consider also the datalink requirements Enter here your presentation title 11

SJU Call for new Associate Partners The European Organisation for the Safety of Air Navigation

SJU Call For Tender • The SESAR JU has very recently released of Call for new Associate Partners, in particular in the Information Management Domain • Target audience: small and medium-sized enterprises (SMEs), research organisations, universities, institutes etc… • http: //www. sesarju. eu/news-press/news/call-new-associatepartners-734 • http: //www. sesarju. eu/about/procurement Enter here your presentation title 13

Meeting AIM’s temporality requirements in OGC standards The European Organisation for the Safety of Air Navigation

Temporality requirements • Problem: insufficient support (in OGC standards) of the temporality • No concept of feature history • As a consequence, AIXM 5 has to define its own temporality model. The GML “timeslice” was somehow misused • Some issues are now encountered when trying to exchange AIXM 5 data over WFS/FES 2. 0 for instance (see OWS-7 results) Enter here your presentation title 15

Temporality requirements • This is NOT an issue specific to the Aviation Domain ! • Connections with other OGC groups • MET DWG ? • Simple Feature ? • … • How can we best handle that issue within OGC? Enter here your presentation title 16

Questions ? Enter here your presentation title 17