24
GeodesyML for efficient positioning data delivery Dr Ivana Ivánová
GeodesyML for efficient positioning data delivery
Dr Ivana Ivánová
Positioning in 2020 and beyond
2
▪ AUS$225million from federal budget to improve positioning in AU –ultimate aim: deliver precise (<5cm) position to ALL!
▪ How:▪ AU Satellite-Based Augmentation System and Southern Positioning Augmentation
Network (AU+NZ)
▪ National Positioning Infrastructure Capability
Positioning Australia
Agriculture Aviation Construction Consumer Maritime Resources Road Rail Spatial
Positioning in 2020 and beyond
▪ The challenge:▪ Too many dialects – GNSS site vs GNSS station;
▪ Too many/Too few protocols – data transmission not scalable;
▪ Heavy internet traffic – relies on 24h broadband connection;
▪ Too big datasets – users receive everything available rather than data of interest;
▪ Geodetic data and metadata not FAIR – difficult to discover and determine fitness for use;
▪ …
3
What kind of users want precise position?
▪ Users (machines or human) know that there we have SDIs and those curate metadata catalogues.
▪ Users still want to determine whether data fits their purpose.
▪ Users aren’t native geodesists, but have expectations on the quality of geodetic data and they learned use standard geodetic language for that.
4
What for do user want to use the data?
5
What do GNSS end-users want?
▪ Information about:
6
Agriculture Rail Road Maritime AviationLocation-Based
Services
Time &
SynchronisationSurveying
Metadata Accuracy
Availability
Integrity
Coverage
Reliability
Accuracy
Availability
Integrity
Coverage
Reliability
Robustness
Continuity
Authentication
Accuracy
Availability
Integrity
Continuity
Reliability
Authentication
Interoperability
Accuracy
Availability
Integrity
Coverage
Reliability
Coverage
Accuracy
Availability
Integrity
Continuity
Accuracy
Availability
Integrity
Authentication
Accuracy
Authentication
Accuracy
Availability
Search attempt Nr.17Search attempt Nr.2Search attempt Nr.3
So, let’s find ‘some geodesy’…
What are users getting today?
▪ I want GNSS data from Albany station from 6 June 2019 – where are the data?
Where are the data?Oh, I know now, this is part of national network, so must be somewhere within the national data portal…
Search attempt Nr.1Search attempt Nr.2
OK, OK, but where is the data?
what? where? At GA??8
Where are the data?OK, let’s go to GA then…
And after few more educated clicks and extra search, I get what I need
9
But how fit are these data for my purpose?Back to the catalogue:
Really? Let’s just double-check!
10
GeodesyMLfor efficient positioning data(and metadata) delivery
11geodesyml.org
What is GeodesyML?
▪ The Geodesy Markup Language (GeodesyML) is a standard way of describing (encoding) and sharing geodetic data and metadata.
▪ Harmonizes language of geodesy – allows mapping of geodetic database into a common language to exchange data with others.
▪ Enables machine-readable access via the internet, i.e. for more than dedicated (geodetic) equipment.
12geodesyml.org
Who is GeodesyML for?
▪ Primarily for GNSS data providers – example users IGS, UNAVCO, GA
▪ But then also, for machines discovering geodetic data on the web
13geodesyml.org
How is GeodesyML used?
▪ I want information about GNSS Site in Albany!
https://testgeodesy-geoserver.geodesy.ga.gov.au/geoserver/wfs?request=GetFeature&typeName=geo:Site&cql_filter=gml:identifier=’ALBY’
14geodesyml.org
How is GeodesyML used?
▪ Here you go!
15geodesyml.org
What types of data is GeodesyML for?
▪ Current version handles geodetic data and metadata relating to equipment, site logs, measurement, adjustment, quality, monuments, reference frames and data lineage.
16geodesyml.org
What types of data is GeodesyML for?
▪ Current version handles geodetic data and metadata relating to equipment, site logs, measurement, adjustment, quality, monuments, reference frames and data lineage.
17geodesyml.org
GeodesyML and international standards
▪ GeodesyML is an XM application schema (ISO 19109 and ISO 19110) providing information about geodetic data (ISO 19136) and metadata (ISO 19115-1 and ISO 19157) to users via standardised web interface (ISO 19142).
▪ Built upon SOPAC’s XML Schema for Geodesy
18geodesyml.org; sopac.ucsd.edu/xmlGeodesy.shtml
Is GeodesyML FAIR?
▪ We tested current version of GeodesyML to see if data&metadata is Findable, Accessible, Interoperable and Reusable.
19
Not quite there yet
FAIR self-assessment tool: https://www.ands-nectar-rds.org.au/fair-tool
Quo vadis GeodesyML?
▪ Extend the information model to cover the positioning information value chain
20
From ISO 19115-1
Quo vadis GeodesyML?
▪ Provide necessary information –create ‘positioning community’ profile;
▪ Our companions in this effort are ISO 19115-1, ISO 19106, ISO 19111, ISO 19116, ISO 19127, ISO 19157-1 amongst others;
21
Quo vadis GeodesyML?
▪ Improve FAIRness of GeodesyML:▪ define FAIR metrics for positioning data, and
▪ set-up FAIRness validation tool
22
From here To here
▪ Follow best practices for preparing information for sharing across the web and start by ‘upgrading GeodesyML to ISO/OGC Geospatial API’:▪ From WFS to Geospatial API Features
▪ From CSW to Geospatial API Records
▪ From current processing to Geospatial API Processes
▪ Our ultimate aim:
improve GeodesyML for acceptable standard for geodetic data interchange
Quo vadis GeodesyML?
23
