Constructions in progress in OpenStreetMap

Open data API in a single place

Provided by magellium

Get early access to Constructions in progress in OpenStreetMap API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.10.30 08:45
Created
2020.07.17
Available languages
English
Keywords
construction-neuve, construction, magosm, travaux, chantier, wfs, travaux-publics, openstreetmap, wms, chantiers, osm, wmts, constructions
Quality scoring

Dataset description

Daily extract of **constructions** in metropolitan France present in the OpenStreetMap (OSM) open and collaborative database [1]. The layer is available in [MAGOSM](https://magosm.magellium.com/) — accessible via public WMS and WFS services — viewable, searchable and downloadable via the portal — analysable over the last 30 days via the Change Tracking Portal **Data model** The OSM attributes used to filter the data are: * **construction**=VALUE **+** KEY=**construction** — in the evolution logic of OSM objects **common life cycle** [2] * **construction:** KEY=VALUE — in the evolution logic of OSM objects **life cycle prefix** [3] The metadata of the layer of two attributes named ‘const_key’ and ‘const_value’ are variables created in order to retrieve keys and values in objects tagged with prefixes [3] EX:the construction:aerialway=gondola tag will return const_key = ‘aerialway’ as key and const_value = ‘gondola’ as value (without retaining the prefix). We find in the layer all the objects concerned whether they are mapped in the form of a node, path or relationship in OSM.For polygons and multi-polygons, the geometry provided corresponds to the centroid, the original geometry is available in EWKT format via the attribute ‘osm_original_geom’ and the original type in a column ‘osm_type’. Additional OSM attributes have been selected to enrich the main tags. All attributes prefixed by “osm” (e.g. osm_user, osm_id...) are common properties similar to meta-data on the OSM object. More information about: * the **different life cycle concepts in OSM** on the OSM Wiki page — EN: Comparison of life cycle concepts [2] * the **data model specific to the use of prefixes** on the Wiki page OSM — FR:Prefix life cycle [3]. * the **construction-specific data model** on the Wiki page OSM — FR:Key:construction[4]. * the **general OSM data model** is documented on the OSM Wiki page — Map Elements [5]. * the **modes and frequencies of use and combination of different attributes** within the OSM community on the TagInfo France service [6] [1] https://wiki.openstreetmap.org/wiki/FR:Page_principale [2] https://wiki.openstreetmap.org/wiki/FR:Comparaison_des_concepts_de_cycle_de_vie [3] https://wiki.openstreetmap.org/wiki/FR:Pr%C3%A9fixe_cycle_de_vie [4] https://wiki.openstreetmap.org/wiki/FR:Key:construction [5] https://wiki.openstreetmap.org/wiki/FR:%C3%89l%C3%A9ments_cartographiques [7] https://taginfo.openstreetmap.fr **Credits** © OpenStreetMap contributors http://www.openstreetmap.org/copyright This data is produced collaboratively under ODbL license which requires identical sharing and attribution mention “© OpenStreetMap contributors under ODbL license” in accordance with http://osm.org/copyright
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks