Resource details

File name: Horaires temps-réel du réseau Sitac - Calais (GTFS-RT)
Format: gtfs-rt

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

Download availability

2025-04-06
100%
2025-04-07
100%
2025-04-08
99.3%
2025-04-09
100%
2025-04-10
99.9%
2025-04-11
100%
2025-04-12
100%
2025-04-13
100%
2025-04-14
100%
2025-04-15
100%
2025-04-16
100%
2025-04-17
100%
2025-04-18
100%
2025-04-19
100%
2025-04-20
100%
2025-04-21
100%
2025-04-22
100%
2025-04-23
100%
2025-04-24
100%
2025-04-25
100%
2025-04-26
100%
2025-04-27
100%
2025-04-28
100%
2025-04-29
100%
2025-04-30
100%
2025-05-01
100%
2025-05-02
100%
2025-05-03
100%
2025-05-04
100%
2025-05-05
99.2%
2025-05-06
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.

Validation details

794 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-05-05 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 63 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id zenbus:Vehicle:327000002:LOC trip_id 4830834000396288:7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4830834000396288:7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id zenbus:Vehicle:315400001:LOC trip_id 4824153916964864:6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4824153916964864:6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id zenbus:Vehicle:313360002:LOC trip_id 4865908817264640:5 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 63 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • vehicle_id zenbus:Vehicle:327000002:LOC route_id zenbus:Line:577450010:LOC does not exist in the GTFS data routes.txt
  • route_id zenbus:Line:577450010:LOC does not exist in the GTFS data routes.txt
  • vehicle_id zenbus:Vehicle:315400001:LOC route_id zenbus:Line:577450010:LOC does not exist in the GTFS data routes.txt
  • route_id zenbus:Line:577450010:LOC does not exist in the GTFS data routes.txt
  • vehicle_id zenbus:Vehicle:313360002:LOC route_id zenbus:Line:577450010:LOC does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 667 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • vehicle_id zenbus:Vehicle:327000002:LOC stop_id zenbus:StopPoint:SP:6256559103410176:LOC does not exist in GTFS data stops.txt
  • trip_id 4830834000396288:7 stop_id zenbus:StopPoint:SP:5182330673037312:LOC does not exist in GTFS data stops.txt
  • trip_id 4830834000396288:7 stop_id zenbus:StopPoint:SP:585300009:LOC does not exist in GTFS data stops.txt
  • trip_id 4830834000396288:7 stop_id zenbus:StopPoint:SP:6256559103410176:LOC does not exist in GTFS data stops.txt
  • trip_id 4830834000396288:7 stop_id zenbus:StopPoint:SP:5169274308001792:LOC does not exist in GTFS data stops.txt

GTFS-rt agency_id does not exist in GTFS data E034 1 error

All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt

Sample errors
  • alert ID 5727348410286080 agency_id sitac does not exist in the GTFS data agency.txt

Warnings

vehicle_id not populated W002 3 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5981551503343616:7 does not have a vehicle_id
  • trip_id 5016223847809024:2 does not have a vehicle_id
  • trip_id 4789653879128064:3 does not have a vehicle_id

ID in one feed missing from the other W003 3 errors

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 4789653879128064:3 is in TripUpdates but not in VehiclePositions feed
  • trip_id 5016223847809024:2 is in TripUpdates but not in VehiclePositions feed
  • trip_id 5981551503343616:7 is in TripUpdates but not in VehiclePositions feed
Validate this GTFS-RT now

Previous validations

Here is a recap of all the error types encountered over the last 30 days.

Error ID Description Errors count Number of occurences
E034 All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt 30 30 times (100 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 1 323 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 1 323 24 times (80 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 14 067 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 31 20 times (67 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 31 20 times (67 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-05-06 at 04:25 Europe/Paris.

service_alerts (1) vehicle_positions (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2025-05-06 at 04:25 Europe/Paris.

EVENT Unknown effect

VOTRE AVIS NOUS INTÉRESSE ✨ Vous aimez l’application ? 💌 N’hésitez pas à nous le dire en laissant votre avis sur App Store https://apps.apple.com/fr/app/zenbus/id808231328 ou Google Play https://play.google.com/store/apps/details?id=com.byjoul.code.zenbus.android&gl=FR ! Ce sont vos bons et nombreux avis qui nous aide à nous déployer sur davantage de lignes ! 😉 Bon voyage avec Zenbus 🚌

From 2022-03-02 at 04:00 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-05-06 at 04:25 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "active_period": [ { "start": "1646190000" } ], "cause": "OTHER_CAUSE", "description_text": { "translation": [ { "text": "VOTRE AVIS NOUS INTÉRESSE ✨\r\nVous aimez l’application ? 💌 \r\nN’hésitez pas à nous le dire en laissant votre avis sur App Store https://apps.apple.com/fr/app/zenbus/id808231328 ou Google Play https://play.google.com/store/apps/details?id=com.byjoul.code.zenbus.android&gl=FR ! \r\nCe sont vos bons et nombreux avis qui nous aide à nous déployer sur davantage de lignes ! 😉\r\nBon voyage avec Zenbus 🚌" } ] }, "header_text": { "translation": [ { "text": "EVENT" } ] }, "informed_entity": [ { "agency_id": "sitac" } ] }, "id": "5727348410286080" } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1746498334" } }