2017.2 Alternative encodings 48th MIG-T meeting 11-12 April 2018, Ispra

Prioritisation (MIG-T, n=19)

Prioritisation (FR implementers, n=7)

Comments (MIG-T) Please focus on end-users and well-known standards GeoJSON meets the same requirements as Simplified (flattened) GML. The same applies to O&M Simple Features Profile We use intensively PostGIS and GeoJSON is a flexible, easy-to-integrate format, already widely used It is preferable to solve the INSPIRE complexity at the root allowing simplified INSPIRE GML data models The INSPIRE feature catalog is a good framework for common understanding. Some respondents doubt the effectiveness of setting up single data models and schemas that would fit all purposes. Following the example of the Hydrography theme, we could agree on several (simple) data schemas for one theme according to the usage (mapping, spatial analysis and/or e-reporting) ESRI formats preferred but with rather mixed views from data providers. For raster data GeoTIFF was also suggested. Furthermore, ASCII format (e.g. marine data) was brought up as one preferred alternative.

Comments (FR implementers) GeoJSON enables massive interoperability. It should be the top priority I am even surprised to see ESRI Geodatabase in the list ?! Is there a "never ever" choice possible here ? How would that be possible without a full standard and respected specification available ? OSM XML a candidate - it is built into QGIS and many other software packages You are asking about encoding rules, but encoding rules for what ? storage formats (Postgis), exchange formats (GeoJSON), download formats (GeoPackage) ? Download services ? please be more explicit ! If we talk about WFS and related services, I think a simple REST (PUT, DELETE, POST, GET) API on the server side, with GeoJSON could deserve a go. That could be a GeoJSON v2 as well, to provide the complex features support it may lack of currently. For a straight download into an efficient, open, accessible format, pick GeoPackage ! OGC (open) formats should be the top priority over any proprietary format

Any questions? You can find me at @michellutz & michael.lutz@ec.europa.eu