The approach consisted of the following steps:
- establish requirements
- organize a High5 week with stakeholders in the week starting at June 21 2021
- Choose data sets (Dutch INSPIRE addresses and Statistical Units)
- Implement an OAPIF at the Geonovum testbed for OGC-API-Features
- start communication on Github
- report to INSPIRE community
- organize presentations
Stakeholders are:
- Geonovum as initiator and author of this document (https://www.geonovum.nl)
- PDOK (Publieke Dienstverlening op de Kaart, http://www.pdok.nl) as hosting organization for geoservices
- Dutch Kadaster and Statistics Netherlands as data providers
PDOK has used self developed software based on Go and PostgreSQL/Postgis. (https://github.com/PDOK/goaf). At the Geonovum testbed for OGC-API-Features we chose for Pygeoapi.
The test at PDOK used the As-is dataset for the addresses in a csv format. This data was mapped to GeoJSON with OGR modules in Goaf. This dataset was chosen, because a description of the GeoJSON encoding was already available at [[PUB-4]]. The harmonized data was not chosen, because it did not contain the actual addresses, but only a link. This is caused by the complexity of the INSPIRE model.
The test at the Geonovum testbed for OGC-API-Features used the WFS of the INSPIRE harmonized dataset for Statistical Units. This dataset was chosen, because the harmonized WFS returns simple GML, so we had no problems with complex GML.
The requirements are listed in detail in https://github.com/Geonovum/OAPIF-PDOK-INSPIRE/tree/main/requirements Below the most relevant requirements are listed:
| nr | requirement | priority | reference |
|---|---|---|---|
| 1 | OGC API Features Core | 1 | [[PUB-1]] |
| 2 | INPSIRE-MIF document: Setting up an INSPIRE Download service based on the OGC API-Features standard | 1 | [[PUB-2]] |
| 3 | multilinguality | 3 | [[PUB-2]] #82-requirements-class-inspire-multilinguality- |
| 4 | predefined download | 1 | [[PUB-2]] #req-pre-defined |
| 5 | GeoJSON | 1 | [[PUB-2]] #req-oapif-json |
| 6 | bulk download | 1 | [[PUB-2]] #req-bulk-download |
| 7 | CRS ETRS89 and WGS84 | 2 | [[PUB-5]] and [[PUB-2]] #req-crs |
| 8 | INSPIRE validated GML as input and output | 3 | https://inspire.ec.europa.eu/validator/about/ and [[PUB-1]] #_requirements_classes_for_encodings |
| 9 | Dutch API design rules | 1 | [[PUB-3]] |
| 10 | describing encoding | 1 | [[PUB-4]] |
| 11 | filtering | 2 | [[PUB-6]] |
| 12 | metadata links | 1 | [[PUB-1]] #rec_core_fc-md-descriptions and [[PUB-2]] #metadata-elements-of-the-data-set |
Relevant documentation is shown in appendix A