Cartographie des aires de stationnement de Lorient Agglomération

Open data API in a single place

Provided by Lorient Agglomération

Get early access to Cartographie des aires de stationnement de Lorient Agglomération API!

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

Dataset information

Country of origin
Updated
2026.03.01 23:00
Created
Available languages
English
Keywords
mobiltes, stationnements-velos, aire-de-stationnement, pave, donnees-ouvertes, mobilite-transport-autres, accessibilite, deplacements, pdu, stationnements, mobilite-transport-stationnement, places-pmr, transports
Quality scoring

Dataset description

Ces données recensent toutes les aires de stationnement du territoire de Lorient Agglomération **Contexte de collecte** Données relevées dans le cadre du projet Handicap Innovation Territoire (HIT). Pôle Transformation Responsable du Territoire - Mission Système d'Information Géographique Territorial. **Méthode de collecte** Travail à partir de photo aérienne. Récupération de données provenant des communes. **Attributs** | Champ | Alias | Type | | --- | --- | --- | | `id_airstat` | identifiant aire de stationnement | `int4` | | `lib_aire` | libellé aire de stationnement | `varchar` | | `date_crea` | date de création | `date` | | `date_modif` | date de modification | `date` | | `nbpl` | nombre de place | `int4` | | `nbplpmr` | nombre de place PMR | `int4` | | `park_priv` | parking privé | `bool` | | `park_publi` | parking public | `bool` | | `covoitu` | covoiturage | `bool` | | `sousterrain` | | `bool` | | `nbplvelo` | nombre de place vélo | `int4` | | `nbplelec` | nombre de place voiture élec | `int4` | | `eclairage` | éclairage | `bool` | | `sanitaires` | | `bool` | | `id_troncon` | identifiant tronçon | `int4` | | `lib_dep` | département | `varchar` | | `insee` | insee | `varchar` | | `nom_voie_d` | nom voie droite | `varchar` | | `id_typ_surf` | identifiant type de surface | `int4` | | `lib_type_surface` | revêtement | `varchar` | | `id_etage` | identifiant étage | `int4` | | `etages_lib_l` | étage | `varchar` | | `pmr_1` | | `varchar` | | `pmr1_id_typsta` | | `int4` | | `pmr1_lib_typsta` | | `varchar` | | `pmr1_id_degrad` | | `int4` | | `pmr1_lib_degrad` | | `varchar` | | `pmr1_signalpmr` | | `bool` | | `pmr1_marqsol` | | `bool` | | `pmr1_latsecu` | | `bool` | | `pmr1_longueur` | | `float8` | | `pmr1_largeur` | | `float8` | | `pmr1_pente` | | `float8` | | `pmr1_devers` | | `float8` | | `pmr1_x` | | `float8` | | `pmr1_y` | | `float8` | | `pmr1_lat` | | `float8` | | `pmr1_long` | | `float8` | | `pmr_2` | | `varchar` | | `pmr_2_id_typsta` | | `int4` | | `pmr_2_lib_typsta` | | `varchar` | | `pmr_2_id_degrad` | | `int4` | | `pmr_2_lib_degrad` | | `varchar` | | `pmr_2_signalpmr` | | `bool` | | `pmr_2_marqsol` | | `bool` | | `pmr_2_latsecu` | | `bool` | | `pmr_2_longueur` | | `float8` | | `pmr_2_largeur` | | `float8` | | `pmr_2_pente` | | `float8` | | `pmr_2_devers` | | `float8` | | `pmr_2_x` | | `float8` | | `pmr_2_y` | | `float8` | | `pmr_2_lat` | | `float8` | | `pmr_2_long` | | `float8` | | `pmr_3` | | `varchar` | | `pmr_3_id_typsta` | | `int4` | | `pmr_3_lib_typsta` | | `varchar` | | `pmr_3_id_degrad` | | `int4` | | `pmr_3_lib_degrad` | | `varchar` | | `pmr_3_signalpmr` | | `bool` | | `pmr_3_marqsol` | | `bool` | | `pmr_3_latsecu` | | `bool` | | `pmr_3_longueur` | | `float8` | | `pmr_3_largeur` | | `float8` | | `pmr_3_pente` | | `float8` | | `pmr_3_devers` | | `float8` | | `pmr_3_x` | | `float8` | | `pmr_3_y` | | `float8` | | `pmr_3_lat` | | `float8` | | `pmr_3_long` | | `float8` | | `pmr_4` | | `varchar` | | `pmr_4_id_typsta` | | `int4` | | `pmr_4_lib_typsta` | | `varchar` | | `pmr_4_id_degrad` | | `int4` | | `pmr_4_lib_degrad` | | `varchar` | | `pmr_4_signalpmr` | | `bool` | | `pmr_4_marqsol` | | `bool` | | `pmr_4_latsecu` | | `bool` | | `pmr_4_longueur` | | `float8` | | `pmr_4_largeur` | | `float8` | | `pmr_4_pente` | | `float8` | | `pmr_4_devers` | | `float8` | | `pmr_4_x` | | `float8` | | `pmr_4_y` | | `float8` | | `pmr_4_lat` | | `float8` | | `pmr_4_long` | | `float8` | | `pmr_5` | | `varchar` | | `pmr_5_id_typsta` | | `int4` | | `pmr_5_lib_typsta` | | `varchar` | | `pmr_5_id_degrad` | | `int4` | | `pmr_5_lib_degrad` | | `varchar` | | `pmr_5_signalpmr` | | `bool` | | `pmr_5_marqsol` | | `bool` | | `pmr_5_latsecu` | | `bool` | | `pmr_5_longueur` | | `float8` | | `pmr_5_largeur` | | `float8` | | `pmr_5_pente` | | `float8` | | `pmr_5_devers` | | `float8` | | `pmr_5_x` | | `float8` | | `pmr_5_y` | | `float8` | | `pmr_5_lat` | | `float8` | | `pmr_5_long` | | `float8` | | `pmr_6` | | `varchar` | | `pmr_6_id_typsta` | | `int4` | | `pmr_6_lib_typsta` | | `varchar` | | `pmr_6_id_degrad` | | `int4` | | `pmr_6_lib_degrad` | | `varchar` | | `pmr_6_signalpmr` | | `bool` | | `pmr_6_marqsol` | | `bool` | | `pmr_6_latsecu` | | `bool` | | `pmr_6_longueur` | | `float8` | | `pmr_6_largeur` | | `float8` | | `pmr_6_pente` | | `float8` | | `pmr_6_devers` | | `float8` | | `pmr_6_x` | | `float8` | | `pmr_6_y` | | `float8` | | `pmr_6_lat` | | `float8` | | `pmr_6_long` | | `float8` | | `nom_com` | | `varchar` | Pour plus d’informations, consultez [la métadonnée sur le catalogue Isogeo](https://open.isogeo.com/s/0bd17a2a330842c68ec4a412d1df6824/AiCyPK6W8fg012l-vHV0s5tPry5b0/r/5617bb73738e40f1951be372590f9a2f).
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