Routes of the STAR network of Rennes Métropole

Open data API in a single place

Provided by Rennes Métropole

Get early access to Routes of the STAR network of Rennes Métropole API!

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

Dataset information

Country of origin
Updated
2024.12.10 23:00
Created
2024.12.10
Available languages
English
Keywords
metro, transport-de-voyageurs, systeme-de-transport, politique-du-transport, mobilite-transport, autobus, vehicule-de-transport-en-commun, transport-en-commun
Quality scoring

Dataset description

A line route corresponds to the actual route a bus takes on a line. For a line, we will therefore have at least 2 routes described in the direction of traffic A (North to South or East to West) and the direction of circulation B (South to North or West to East). In addition, there may be variations on the main routes. The route code is therefore constructed as follows: \- line code \- indication of meaning: A or B \- TIMEO code of the physical stop of departure \- possibly: code(s) of intermediate physical stops \- TIMEO code of physical termination terminus Example: “0072-A-1315-4708”, “0072-A-1534-3901-2272-2749”. This multiline layer is constructed by aggregating the basic sections by grouping on the route code. These sections of the routes are seated on the tracks of the Référentiel Voies et Adresses (RVA) of Rennes Métropole. The “star_itineraries” layer contains the history of routes since 2017. To facilitate operation and view only the active network, only the view “v_star_itineraries_active” is published. To view row history, prefer to use the “star_line_archives” layer.
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