Open data and attribution
Where the data comes from
The parking facilities shown on this map are derived from OpenStreetMap. © OpenStreetMap contributors.
Share-alike
The derived database we produce (the tileset used by this map and by the app) is offered under the same ODbL 1.0 licence as the source data.
User-contributed facts
Factual corrections sent from the app (for example “this car park is free”) are OpenStreetMap-type data: our intent is to push them upstream to OpenStreetMap.
These facts live in a separate database and are distributed through a separate channel. When they are baked into a tile set, each one carries its provenance attribute: the distributed tile set itself states what comes from OpenStreetMap and what does not. They remain separable at any time. A pure OpenStreetMap database can be regenerated on demand, and the provenance mode is written into the produced tile set's metadata and then verified by our quality gate: a tile set announced as pure that would not be cannot be published.
Ratings and photos: a separate database, outside this offer
The scores and experience tags left in the app are NOT covered by the offer above. They form a distinct database, and the tileset offered above contains none of it.
The reason fits in one sentence: this data does not come from OpenStreetMap and could not live there. OpenStreetMap describes the world, it does not collect opinions. A score therefore derives from no tag, no OpenStreetMap population of the same type can mix with ours, and share-alike does not apply. The only thing a rating borrows from OpenStreetMap is the identifier of the place it points at: it POINTS to OpenStreetMap, it CONTAINS nothing of it.
Photographs uploaded in the app follow exactly the same reasoning, and here it is even clearer: OpenStreetMap does not host images. A photo derives from no tag, it mixes with no OpenStreetMap data of the same type, and the only thing it borrows from the map is the identifier of the place it shows. It is not covered by the offer above.
External sources
Some of the information shown does not come from OpenStreetMap but from datasets published under licence by their publishers. Each one is credited below with its licence and the date of the snapshot used. On the map, these values carry the name of their source.
Indigo Open Data Parkings
- Publisher
- INDIGO PARK
- Licence
- ODbL 1.0
- Snapshot date
- Publication regime
- ODbL 1.0, like the rest of our derived database. Share-alike applies to these values, and the offer above covers them.
Indigo Open Data Parkings (Belgique)
- Publisher
- INDIGO PARK BELGIUM
- Licence
- ODbL 1.0
- Snapshot date
- Publication regime
- ODbL 1.0, like the rest of our derived database. Share-alike applies to these values, and the offer above covers them.
Base nationale consolidée des points de recharge (IRVE, données statiques)
- Publisher
- Point d'Accès National transport.data.gouv.fr
- Licence
- Licence Ouverte 2.0
- Snapshot date
- Publication regime
- ODbL 1.0, like the rest of our derived database. Share-alike applies to these values, and the offer above covers them.
Référentiel parkings Saemes
- Publisher
- Saemes
- Licence
- Licence Ouverte 1.0
- Snapshot date
- Publication regime
- ODbL 1.0, like the rest of our derived database. Share-alike applies to these values, and the offer above covers them.
A source can be withdrawn from display at any time. It then disappears from the map details on the next load. On a device that never reconnects, values already downloaded remain visible.
Regenerating a pure OpenStreetMap database
The production pipeline accepts a mode that forbids any injection of contributed facts:
NO_OVERLAY=1 pipeline/bin/run_daily.shThe provenance mode is stamped into the produced tileset's metadata (the “overlay” and “external” tokens) and checked by the quality gate: a database claimed to be pure but that is not cannot be published.