SAS bike and turn-to-right – Angers

Open data API in a single place

Provided by Angers Loire Métropole

Get early access to SAS bike and turn-to-right – Angers API!

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

Dataset information

Country of origin
Updated
2026.03.31 20:00
Created
2026.03.31
Available languages
English
Keywords
transports-deplacements, catalogue-sig, velo
Quality scoring

Dataset description

List of SAS and bike tour-to-right for the territory of the city of Angers * * * * **Definition of SAS**: Layout, inscribed in the road code since 1998, the bicycle or bicycle lock (the regulatory term) is a demarcated space, which, at a crossroads with a traffic light, allows bicycles to be placed between the stop line of the cars and the pedestrian crossing, and to the right or left of the airlock if they want to turn. **Definition of turn-to-right**: Signage entirely dedicated to cyclists. Placed at a red light, it allows them to continue their path without having to mark the stop even if the light is red. This authorisation is permitted only for the direction(s) indicated by an arrow on the sign ([conditional crossing authorisation sign M12](https://www.legifrance.gouv.fr/loda/id/JORFTEXT000031285676)), and the cyclist must always give priority to other users, including pedestrians. * * * * **Description of certain fields in the dataset**: VEL_TAD: Presence of a tour-to-right cyclist VEL_SAS: Presence of a bicycle lock POST: panel support > FEUX (automotive tricolor lamp); Velo (tricolor fire on bike layout); Tram (Tricolor light on Tram line) ID_VOIE: track ID. This identifier makes it possible to join with the [referential Tronçons des voie d’Angers Loire Métropole](https://data.angers.fr/explore/dataset/troncons-de-voies-angers-loire-metropole)
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