Tronçons de voies - Bayonne

Open data API in a single place

Provided by Ville de Bayonne

Get early access to Tronçons de voies - Bayonne API!

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

Dataset information

Country of origin
Updated
2025.11.20 23:00
Created
Available languages
English
Keywords
toponymie, vitesse, donnees-ouvertes, voirie, gascon, base-adresse-locale, basque, limitations-de-vitesse, odonymie, euskara
Quality scoring

Dataset description

These are linear lines representing the Bayonne track axes. For the same track, there are several sections (division at each intersection). Each section is attached to a track in the track chart. **Collection context** The tracks are appointed by deliberation of the city council, on the proposal of the toponymy commission. The deliberation is sent to the DGFiP, which then creates a fancy code (rivoli). The track is then added to the GIS in the track table and then each section is created. **Method of collection** Entry at the axis of the track, on the aerial photo in the case of an already existing track, or on the basis of the project plan in the case of a track to be created. **Attributes** | Field | Alias | Type | | --- | --- | --- | | `ogc _fid` | Unique identifier | `int4` | | `name _voie` | Track name | `varchar` | | `address _debut _droite` | Address at the beginning right | `int4` | | `address _fin _droite` | Right-end address | `int4` | | `address _debut _left` | Early left | `int4` | | `address _fin _left` | Left-end address | `int4` | | `display` | Display | `varchar` | | `reference` | Reference | `varchar` | | `nbre _voie` | Number of lanes | `int4` | | `_insee code` | INSEE code | `int4` | | "Manager" | Manager | "varchar" | | `sens` | Sens | `varchar` | | `type _voie` | Track type | `varchar` | | `name _voie _basque` | Track name in Basque | `varchar` | | `display _basque` | Display in Basque | `varchar` | | `lim _speed` | Speed | `varchar` | | ʻidmanagerʼ | | ʻint4ʼ | | `idlim _speed` | | `int4` | | `idsens` | | `int4` | | `idtype _voie` | | `int4` | | `idnom _voie` | | `int4` | | `date _saisie` | Date of seizure | `timestamp` | | `date _maj` | Update date | `timestamp` | | "length" | Length | "numeric" | | `id _kadri` | former id oracle -> used for Kadri | `int4` | | `date _deletion` | Deletion date | `date` | For more information, see [the Isogeo catalogue metadata](https://open.isogeo.com/s/dfea79f9daa941fbb7fc9248309dc1c4/THU _tcV6SuOT _DsWqcQNzDenuhTV0/r/e319dd3893a34c6299b9ccaaf3017594).
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