Skip to content

Latest commit

 

History

History
105 lines (83 loc) · 4.57 KB

deployment-nrwde.md

File metadata and controls

105 lines (83 loc) · 4.57 KB
Raw

Deployments in North-Rhine Westphalia

1. Data provider

Datasets from multiple data providers from North-Rhine Westphalia, Germany.

2. Thematic scope

The following datasets are available:

  • Mining permits (Bergbauberechtigungen), data theme AM
  • Fire brigade control centres (Feuerwehrleitstellen), data theme US
  • Child care facilities (Kindertageseinrichtungen), data theme US
  • Hospitals (Krankenhäuser), data theme US
  • Various agricultural datasets relevant in the context of the Integrated Administration and Control System (IACS), data themes LC/LU
  • Low emission zones (Umweltzonen), data theme AM

In addition, extensions to the INSPIRE codelists are published in another API. This currently declares the item type as "features", but it is planned to migrate this in the future to OGC API Records.

3. Envisaged use

The APIs are in production since November 2020.

4. Requirements classes

From the draft Good Practice:

  • Requirements class "INSPIRE-pre-defined-data-set-download-OAPIF"
  • Requirements class "INSPIRE-multilinguality"
    • The implementation meets the requirements, but language selection only affects text generated by the API (html and link titles), not text in the data. All text in the data is always in German.
  • Requirements class "INSPIRE-OAPIF-GeoJSON"
    • There are some differences to the "INSPIRE UML-to-GeoJSON encoding rule" that we will document.
  • Requirements class "INSPIRE-bulk-download"
    • This requirements class is implemented for most APIs, typically linking to a CSV file and/or Shapefile archive.

The current development deployment supports the following OGC API requirements classes:

  • OGC API - Features - Part 1: Core 1.0
    • Core (required by INSPIRE)
    • OpenAPI 3.0 (required by INSPIRE)
    • GeoJSON (required by INSPIRE)
    • HTML
  • OGC API - Features - Part 2: Coordinate Reference Systems by Reference Release Candidate (in approval vote)
    • Coordinate Reference Systems by Reference
  • OGC API - Features - Part 3: Filtering and the Common Query Language (CQL) DRAFT
    • Filter
    • Features Filter
    • Simple CQL
    • CQL Text encoding
    • CQL JSON encoding
  • OGC API - Tiles - Part 1: Core DRAFT
    • Tile Set
    • Tile Sets
    • Dataset Tile Sets
    • Geodata Resource Selection
    • Geodata Resource Tile Sets
  • OGC API - Tiles - Part 2: Tile Matrix Sets DRAFT
    • Tile Matrix Sets
  • OGC API - Styles DRAFT
    • Core
    • HTML
    • Mapbox Styles
    • Queryables
    • Style Info
    • Resources (only, if the style needs symbols)

5. Server-side technology

The deployment uses XtraServer Web API from interactive instruments GmbH, which integrates ldproxy. ldproxy is available under the Mozilla Public License 2.0.

6. Endpoints and client applications

Landing page of the deployment: https://ogc-api.nrw.de/

APIs:

7. Issues

All issues with respect to the requirements in the Good Practice document were resolved as part of the work on the Good Practice specification.

It would be good, if other INSPIRE service types could also be provided using current Web APIs. For example, see the issue on INSPIRE View Services.