Counting up passengers on Transilien trains per hour. These manual counts are carried out every three to four years and count the number of amounts for:
* Each train on a Transilien line at each station served
* Every typical day (JOB, Saturday and Sunday), excluding school work and holidays
Explanation of the wording used:
* Station name: Name of station
* Station code: UIC code. It is unique and allows the station to be identified.
* Day type: Specifies the day of counting: Saturday, Sunday or JOB (Tuesday or Thursday)
* Date of counting: Specifies the date of counting
* Line: Specifies the line of the train concerned when counting as some stations are served by more than one line. In this case, details are given, as in the example of the Juvisy railway station.
* Time slot: Time slot associated with the arrival time of the train at the station
* Amounts: Indicates the number of amounts in trains according to the above criteria
Last update of the file: 24 March 2020
On each update, we cancel and replace the database: There is no history of counting.
For a particular station, there may be several counting dates:
\ — Two lines passing through the same station are not necessarily counted on the same day;
\ — t/or there may be catch-up days if the first day of counting is incomplete.
Thus, in order to have the number of reference amounts, it is necessary to keep all the data in order to obtain the completeness of the counts.
Points of Attention:
\ — Line C was interrupted on Saturdays and Sundays of Line D in Juvisy. The amounts of Line D at Juvisy station on Saturdays and Sundays are therefore increased by carry-overs of amounts from Line C.
\ — Add a ‘Axis’ column identifying axes in the same row that would not have been counted on the same date
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.