transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: Description du TAD zonal (GTFS-Flex) - réseau Corolis
Format: GTFS
Size: 11.13 KB
Download

Fichier GTFS-Flex décrivant l’offre TAD zonal du réseau de transport public du Beauvaisis.

This resource file is part of the dataset Réseau interurbain Corolis.

  • network : Corolis C.A. du Beauvaisis - Interurbain
  • transport mode : bus
  • number of routes: 20
  • number of stop points: 122
  • number of stop areas: 0

The following table displays if the file/field is present in the GTFS.

Description File or field Status Quantity
Stop accessibility stops.txt — wheelchair_boarding ✅ 122
Trip accessibility trips.txt — wheelchair_accessible ❌ 0
Line short name or line number routes.txt — route_short_name ✅ 20
Line long name routes.txt — route_long_name ✅ 20
Line color routes.txt — route_color ❌ 0
Trip headsign trips.txt — trip_headsign ❌ 0
The possibility of carrying a bicycle in the vehicle trips.txt — bikes_allowed ❌ 0
Trip shapes shapes.txt ❌ 0
Fare attributes fare_attributes.txt ❌ 0
Fare rules fare_rules.txt ❌ 0
Fare products fare_products.txt ❌ 0
Fare media fare_media.txt ❌ 0
Transfers transfers.txt ❌ 0
On-demand transport stop_times.txt — pickup_type, drop_off_type ✅
This resource is also available in the following formats: * GeoJSON format contains only the spatial information of the resource (stops coordinates, eventually lines shapes) It corresponds to the data you can see on the map below. This GeoJSON was up-to-date with the GTFS resource 11 hours and 2 minutes ago.

Download availability

2025-09-13
100%
2025-09-14
100%
2025-09-15
100%
2025-09-16
100%
2025-09-17
99.6%
2025-09-18
100%
2025-09-19
100%
2025-09-20
100%
2025-09-21
100%
2025-09-22
100%
2025-09-23
99.1%
2025-09-24
100%
2025-09-25
100%
2025-09-26
100%
2025-09-27
100%
2025-09-28
100%
2025-09-29
100%
2025-09-30
100%
2025-10-01
100%
2025-10-02
100%
2025-10-03
100%
2025-10-04
100%
2025-10-05
100%
2025-10-06
100%
2025-10-07
100%
2025-10-08
100%
2025-10-09
100%
2025-10-10
100%
2025-10-11
100%
2025-10-12
100%
2025-10-13
100%
Learn more
We test this resource download availability every hour by making an HTTP HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.

For SIRI and SIRI Lite feeds, we perform a GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Stops and routes visualization of the GTFS file

Visualization up-to-date 11 hours and 2 minutes ago.

Validation report

Object type Object ID Object name Related object ID Details
Trip 355 route id: 228, service id: 355
    		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
    Trip 393 route id: 247, service id: 393
      		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
      Trip 361 route id: 231, service id: 361
        		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
        Trip 396 route id: 250, service id: 396
          		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
          Trip 368 route id: 236, service id: 368
            		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
            Trip 363 route id: 232, service id: 363
              		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
              Trip 365 route id: 233, service id: 365
                		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                Trip 353 route id: 227, service id: 353
                  		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                  Trip 370 route id: 238, service id: 370
                    		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                    Trip 466 route id: 305, service id: 466
                      		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                      Trip 369 route id: 237, service id: 369
                        		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                        Trip 366 route id: 234, service id: 366
                          		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                          Trip 467 route id: 307, service id: 467
                            		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                            Trip 395 route id: 248, service id: 395
                              		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                              Trip 357 route id: 229, service id: 357
                                		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                                Trip 359 route id: 230, service id: 359
                                  		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                                  Trip 397 route id: 249, service id: 397
                                    		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                                    Trip 367 route id: 235, service id: 367
                                      		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                                      Trip 352 route id: 226, service id: 352
                                        		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
                                        Trip 351 route id: 225, service id: 351
                                          		The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated

                                          Validation carried out using the current GTFS file the 2025-10-03 at 02:12 Europe/Paris using the PAN GTFS validator.

                                          Other resources