Official; Crown Copyright 2014; Released under OGL Experience with INSPIRE GML Peter Parslow Principal Geographic Information Architect May 2014

Official; Crown Copyright 2014; Released under OGL Summary – experience of 23 companies / 14 different software Most software can’t handle multiplicity > 1 Most software hardly uses the XSD No software used the GML ‘wrapper’ of grid data Some problems with multiSurface The most commonly used software in UK local authorities doesn’t support GML 3 yet INSPIRE Geographic Names is too complex But Elevations & Hydrology are OK (if you leave out the names!)

OGC UK Interoperability Assessment Plugfest 9 th December 2013 and 3 rd March 2014 OGC Engineering Report – pending This presentation is from my own notes on the day Three scenarios: GML, WMS, WFS Two sprints, with time to fix issues in between Eleven companies participated, using nine GIS clients: Arc, QGIS, Intergraph, CadCorp, Astun, Snowflake, Safe, Helyx, Magellium GML Sprint 1: basically, could the software open GML 3.2 Simple Features Profile data generally, yes Sprint 2: ten pages with 23 detailed questions! Official; Crown Copyright 2014; Released under OGL

OGC UK Interoperability Assessment Plugfest Scenario 3, Sprint 2 Coordinate reference systems Simple Features Profile level 0 Code lists and dictionaries Measures Simple Features Profile level 1 Maximum multiplicity > 1 User defined property types Use of nillable and xsi:nil Beyond Simple Features / aspects of GML 3.3 LanguageStringType Dictionaries as gml:ReferenceType Compact geometry encodings Official; Crown Copyright 2014; Released under OGL

OGC plugfest GML: Highlights 1 of 3 Coordinate Reference Systems: some software recognised coordinates in 3D space; only ArcScene/ArcGlobe actually used them Slight preference for srsName on the bounding box Most software recognises a small range of fixed strings: short name & http URI formats Don’t think anyone deferences a URI Some concern about differences between EPSG & OpenGIS.net definitions Confusion of CRS formats in OGC standards (WMS 1.3, WFS 1.1, WFS 2.0, GML 3.2.1) – as OWS Common has changed Some software makes its own decision on lat/long order, independent of the EPSG/OpenGIS definitions Official; Crown Copyright 2014; Released under OGL

OGC plugfest GML: Highlights 2 of 3 Code lists and dictionaries In Arc & QGIS, the codeSpace / xlink:href is clickable In other software it isn’t even visible. No one exposes the xlink:title etc. Measures Very little software uses/exposes the uom Level 1: multiplicity > 1 Real problem: some software simply ignores the attribute User defined type Often usable Official; Crown Copyright 2014; Released under OGL

OGC plugfest GML: Highlights 3 of 3 GML 3.3 Some companies waiting for ISO (or something), but LanguageStringType ok Dictionaries as gml:ReferenceType mixed/minimal Official; Crown Copyright 2014; Released under OGL

OS Insight Hackday Six recent / ‘under development’ products, including three that are INSPIRE compliant (Hydrology, Geographic Names, Elevation – to draft TG) Twelve organisations, seven pieces of software Elevation vector: easy Elevation grid: no one used the GML; loaded ASCII grid Hydrology: easy – except 3D coordinates Note: we avoided repeated INSPIRE names, adding an os: simple attribute for each name Most software can’t handle 3D coordinates Geographic Names: too complex, no software could use it Official; Crown Copyright 2014; Released under OGL

Links for further information OGL: Open Government LicenceOpen Government Licence OGC UK Interoperability Assessment Plugfest: interoperability-assessment-plugfest/ Ordnance Survey’s OS Insight programme: support/os-insight/index.html