Quavsit redistributes open data published by transport authorities and operators. Their licences apply to what you build with the API.

Every response carries the applicable credits in meta.attribution. Display them wherever the data is shown. If the documentation and the API ever disagree, meta.attribution is the contract.

Addresses come from the Base Adresse Nationale under Licence Ouverte 2.0. The per-network table is at quavsit.quavern.com/docs/data-licences, and each Network carries a licence field linking to the text.

Reuse, modify and redistribute, including commercially, provided you credit the source and the date of the last update. No share-alike obligation — but that applies to those networks only, not to the API as a whole.

The Open Database Licence allows reuse and redistribution with attribution, but it is share-alike: if you publicly distribute a database derived from ODbL data — a merged stops file, an enriched timetable — that derived database must itself be offered under ODbL.

Producing a "produced work" such as an app, a map image or a display board is fine without releasing your code. What triggers share-alike is redistributing the data, or a database built from it, as data.

A response that mixes networks can mix licences, so a database you build from several networks inherits the obligations of every source in it. If you are unsure whether what you ship is a database or a produced work, ask a lawyer. Quavsit cannot advise you.

Île-de-France Mobilités' own licence. Reuse is free with attribution, and it adds obligations of accuracy — do not present the data as official IDFM information — and a commitment not to disrupt the service. Read the text on the PRIM portal before publishing a product built on it.

Quavsit's identifiers, its normalised model, its estimated vehicle positions and its router results are derived from those sources and carry their licences. Quavsit claims no additional rights over the data it serves.

Google Maps draws the map in the web application only. No Google data is served by the API.

Quavsit is not the official information service of any operator, and does not guarantee that a departure, a vehicle position, an alert or a journey is accurate or current.

Write to [email protected] with the networks involved and what you intend to publish. The answer will be about the licence, not legal advice.

Quavern help reference: quavsit-data-licences/en