GTFS Transport open dataset - Description du TAD zonal (GTFS-Flex) - réseau AXO for Réseau urbain AXO

Resource details

File name: Description du TAD zonal (GTFS-Flex) - réseau AXO

Format: GTFS

Size: 4.85 KB

Download

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

This resource file is part of the dataset Réseau urbain AXO.

network : AXO - Agglo Creil Sud Oise
transport mode : bus
number of routes: 10
number of stop points: 83
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`	✅	83
Trip accessibility	`trips.txt` — `wheelchair_accessible`	❌	0
Line short name or line number	`routes.txt` — `route_short_name`	✅	10
Line long name	`routes.txt` — `route_long_name`	✅	10
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*

* 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 15 hours and 48 minutes ago.

Download availability

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 15 hours and 48 minutes ago.

Validation report

Object type	Object ID	Object name	Details
Trip	241	route id: 132, service id: 241	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	248	route id: 139, service id: 248	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	244	route id: 134, service id: 244	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	245	route id: 136, service id: 245	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	246	route id: 137, service id: 246	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	247	route id: 138, service id: 247	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	240	route id: 131, service id: 240	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	242	route id: 133, service id: 242	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	243	route id: 135, service id: 243	The first and last stop time of a trip cannot have empty departure/arrivals as they cannot be interpolated
Trip	239	route id: 130, service id: 239	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:10 Europe/Paris using the PAN GTFS validator.

Resource details

Download availability

Stops and routes visualization of the GTFS file

Validation report

Other resources