Model Transformation Rules for Streamlined INSPIRE Esri GDB - Alternative Encodings

[jsaligoe]

Dear Team,
Thank you for your efforts toward simplifying and mainstreaming the technical requirements of the INSPIRE Directive supporting the MIG Work Programme 2021-2024. As a private sector (ad-hoc) member of the INSPIRE community, we seek to support these efforts with de facto standard web applications and existing out-of-the-box SW/SaaS.

Per the guidance provided in Action 2017.2, we have developed streamlined INSPIRE Esri Geodatabase templates (GDB/fGDB) wherein end-to-end workflows are supported to publish the streamlined GDBs using open standards and specifications via GeoServices REST API, OGC WMTS, and OGC API Features, compliant INSPIRE Metadata, and automatic federation through DCAT-AP to support related open data initiatives. We use our demonstration hub to review and test proposed good practices, such as the candidate GP on Data and Service Linking Simplification.

We have established an 'INSPIRE Open Data' repository that provides open access to:

• generic, encoding agnostic model transformation rules
• publicly available encoding rules used to encode spatial data and that explain how (and under which conditions) the encoding meets the requirements of the IRs
• streamlined INSPIRE GDB Templates following Alternative Encoding rules documented herein
• explore the live ArcGIS INSPIRE Open Data demonstration Hub

I welcome your comments and suggestions for other ways we might register this open collection of Model Transformation Rules.
Best regards, Jill Saligoe-Simmel, Esri Product Manager