Document toolboxDocument toolbox

Open data - public API

Owned by oliver.may
Last updated: yesterday at 10:57 pm by Bert Lerno
2 min read

Public Geo-information

Introduction

A subset of the GIPOD data is published as open data by Digitaal Vlaanderen, consisting of several WMS views, a WFS, API Features service and through Geopunt.

What is published?

The dataset consists of all public domain occupancies (groundworks, works and events) that are concretely planned and all resulting mobility hindrances that are validated by local governments.

The dataset is temporally bound to all occupancies and mobilityhindrances that occur today and during the next 6 months.

How is it published?

Web Map Service (WMS)

Service endpoint: https://geo.api.vlaanderen.be/GIPOD/wms ( more information)

Web Feature Service (WFS)

Service endpoint: https://geo.api.vlaanderen.be/GIPOD/wfs ( more information)

OGC API Features

Service endpoint: https://geo.api.vlaanderen.be/GIPOD/ogc/features ( more information)

Example usage of the API features (source code)

Geopunt Hinder in kaart

The data is also published in the Flemish Government mapviewer “Geopunt Hinder in Kaart”.

Linked Open Data

GIPOD uses the “Inname openbaar domein” application profile, which has been developed within the GIPOD project as Linked Open Data and allows for the creation and disclosure of occupancies, mobility measures, and obstructions in the public domain in a linked manner.

MobilityHindrance LDES

Linked Data Event Streams (LDES) represent a framework for publishing, sharing, and linking real-time event data on the web, enhancing the interoperability and accessibility of dynamic information across diverse applications and domains.

The GIPOD planned MobilityHindrance is published as an LDES.

More information about the endpoints can be found in the GIPOD swagger documentation (look for Ldes).

See also: metadata

Taxonomies

Different concepts such as statuses, types, specifiations, etc. used in GIPOD are published trough our taxonomy API. This can come in handy to interpret data or build code lists.

More information about the taxonomies can be found in the GIPOD swagger documentation (look for Taxonomies).

Support

Communication to the outside world about the public API will be done through a github repository. You are also welcome to do suggestions or ask questions. If you wish you can add code examples on using this API to this repository using pull requests, or provide links.

Legacy services

Disclaimer

We don't offer any SLA on service, data, performance or response times of the API’s, if you require such service levels, please contact us at gipod@athumi.eu.