Waiting time by train connecting to Saint-Pierre-des-Corps from/to Tours

Open data API in a single place

Provided by Fnaut Centre-Val de Loire

Get early access to Waiting time by train connecting to Saint-Pierre-des-Corps from/to Tours API!

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

Dataset information

Country of origin
Updated
2025.12.15 22:35
Created
2025.12.10
Available languages
English
Keywords
fnaut, adtt, sncf, transport, train, saint-pierre-des-corps, navette, temps-theorique, attente, transports, tours, correspondance
Quality scoring

Dataset description

### Problem Studyed This dataset lists all trains departing or arriving from Saint-Pierre-des-Corps over a day, and highlights the waiting time with trains to or from Tours. #### Scenario Go The one-way scenario considers the situation where the passenger departs from Tours and makes a connection to Saint-Pierre-des-Corps for another train, i.e.: ![Schedule of a first train from Tours to Saint-Pierre-des-Corps, then a connection to another destination in Saint-Pierre-des-Corps](https://www.data.gouv.fr/api/1/datasets/r/4deaf275-eb24-4f90-973f-58bfb374ee23) 1. Take a train from Tours to Saint-Pierre-des-Corps (called "train liaison" in the dataset) 2. Waiting at Saint-Pierre des Corps 3. Take another train (called "target train") from Saint-Pierre-des-Corps to another destination, except for trains in reverse that serve Tours We then calculate the waiting time with the *last* connecting train (shuttle, TGV or TER) arriving in Saint-Pierre-des-Corps at least 5 minutes before the departure of the target train (15 minutes before the departure of the target train for Ouigo or Ouigo Train Classique), in accordance with the waiting times proposed on the approved booking sites (1.2.Train, SNCF Connect, etc.). > Example: > > I want to take an INOUI TGV in Saint-Pierre-des-Corps at 09:05 for Bordeaux.\ > I leave Tours and my TGV INOUI does not go through Tours.\ > What is the last train from Tours to Saint-Pierre-des-Corps arriving at least 5 minutes before the departure of my TGV INOUI? (i.e. arriving at 09:00 at the latest)\ > In Saint-Pierre-des-Corps, what will be my waiting time between the arrival of my train from Tours and the departure of my INOUI TGV to Bordeaux? #### Scenario Back The return scenario considers the case where the passenger takes any train arriving at Saint-Pierre-des-Corps, and changes to Saint-Pierre-des-Corps for a train to Tours, more specifically: ![Schema of a first train arriving in Saint-Pierre-des-Corps of any origin, then a train connecting Saint-Pierre-des-Corps to Tours](https://www.data.gouv.fr/api/1/datasets/r/c2d733f0-617d-4443-b48f-d812c44b92ec) 1. Take a target train from any origin and serving Saint-Pierre-des-Corps, except trains from Tours 2. Waiting at Saint-Pierre des Corps 3. Take a "link" train to Tours We then calculate the waiting time between the arrival of the target train at Saint-Pierre-des-Corps, and the departure of the *first* link train for Tours leaving at least 5 minutes after the arrival of the target train. > Example: > > I take a TGV INOUI from La Rochelle which arrives in Saint-Pierre-des-Corps at 12:00.\ > I want to go to Tours.\ > What is the first train from Saint-Pierre-des-Corps to Tours leaving at least 5 minutes after the arrival of my TGV INOUI? (from 12:05)\ > In Saint-Pierre-des-Corps, what will be my waiting time between the arrival of my INOUI TGV from La Rochelle and the departure of my train to Tours? ### Documentation The data is cut by file for different days of the week and in each direction (outward or return). Each line in the file lists the trains departing (meaning "outbound") or arriving (meaning "return") from Saint-Pierre-des-Corps, and the associated connecting train to connect Saint-Pierre-des-Corps and Tours.\ In addition to train information (number, direction, line, network, timetables), the file contains the following fields: * **Correspondence time (minutes):** the waiting time between the arrival of the connecting train at Saint-Pierre-des-Corps, and the departure of the target train (or vice versa) * **Travel type** **:** Several possible values: * **Correspondence** **:** A change is required at Saint-Pierre-des-Corps station * **Direct** **:** If the target train leaves or arrives from Tours via Saint-Pierre-des-Corps, there is no need to make a connection at Saint-Pierre-des-Corps. (The 5-minute constraint does not apply) * **No Train Link:** There is no train that allows you to reach Saint-Pierre-des-Corps (meaning to go, in the morning) or to leave Saint-Pierre-des-Corps (meaning to return, in the evening). This situation does not currently appear in the case of Tours - Saint-Pierre-des-Corps ### Data source These data were calculated by a Python script (forthcoming publication) from train departure and arrival data provided by [API SNCF](https://www.data.gouv.fr/datasets/api-theoretical-and-time-reel-sncf/). Data from the SNCF API are published under an Open License.
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