Home
France Feeds
reseau-de-transport-en-commun-trans-agglo-de-dlva
Source Data Validation Report

reseau-de-transport-en-commun-trans-agglo-de-dlva — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-04T02:11:00Z,
for the dataset file:///shared/reseau-de-transport-en-commun-trans-agglo-de-dlva_27f3cfb6.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

TRANSAGGLO
- website: https://mobilite.dlva.fr/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2024-05-01 to 2026-12-31 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
attributions.txt
calendar.txt
calendar_dates.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 41
Shapes: 155
Stops: 263
Trips: 635

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types Continuous Stops

Specification Compliance report

909 notices reported (23 errors, 886 warnings, 0 infos)

Notice Code Severity Total

start_and_end_range_out_of_order ERROR 21

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row number of the faulty record.	startFieldName (?) The start value's field name.	startValue (?) The start value.	endFieldName (?) The end value's field name.	endValue (?) The end value.
"stop_times.txt"	61	"arrival_time"	"13:17:00"	"departure_time"	"13:15:00"
"stop_times.txt"	91	"arrival_time"	"13:47:00"	"departure_time"	"13:45:00"
"stop_times.txt"	121	"arrival_time"	"14:47:00"	"departure_time"	"14:45:00"
"stop_times.txt"	301	"arrival_time"	"07:42:00"	"departure_time"	"07:40:00"
"stop_times.txt"	331	"arrival_time"	"09:17:00"	"departure_time"	"09:15:00"
"stop_times.txt"	451	"arrival_time"	"09:22:00"	"departure_time"	"09:20:00"
"stop_times.txt"	571	"arrival_time"	"15:12:00"	"departure_time"	"15:10:00"
"stop_times.txt"	751	"arrival_time"	"11:52:00"	"departure_time"	"11:50:00"
"stop_times.txt"	781	"arrival_time"	"12:17:00"	"departure_time"	"12:15:00"
"stop_times.txt"	837	"arrival_time"	"12:35:15"	"departure_time"	"12:35:00"
"stop_times.txt"	4362	"arrival_time"	"10:13:00"	"departure_time"	"10:10:00"
"stop_times.txt"	4437	"arrival_time"	"14:15:14"	"departure_time"	"14:15:00"
"stop_times.txt"	4734	"arrival_time"	"15:02:02"	"departure_time"	"15:02:00"
"stop_times.txt"	4748	"arrival_time"	"16:59:00"	"departure_time"	"16:38:00"
"stop_times.txt"	6153	"arrival_time"	"09:32:00"	"departure_time"	"09:31:00"
"stop_times.txt"	7121	"arrival_time"	"18:45:59"	"departure_time"	"18:45:00"
"stop_times.txt"	7212	"arrival_time"	"11:22:00"	"departure_time"	"11:21:00"
"stop_times.txt"	7236	"arrival_time"	"08:55:00"	"departure_time"	"08:54:00"
"stop_times.txt"	9125	"arrival_time"	"09:30:00"	"departure_time"	"09:29:00"
"stop_times.txt"	9126	"arrival_time"	"09:30:00"	"departure_time"	"09:29:00"
"stop_times.txt"	9127	"arrival_time"	"09:30:00"	"departure_time"	"09:29:00"

stop_time_with_arrival_before_previous_departure_time ERROR 2

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	prevCsvRowNumber (?) The row of the previous stop time.	tripId (?) The trip_id associated to the faulty record.	arrivalTime (?) Arrival time at the faulty record.	departureTime (?) Departure time at the previous stop time.
4754	4753	"112R3\|20220901\|42"	"16:37:00"	"16:45:00"
2340	2339	"125R01\|20160308\|2"	"19:29:00"	"19:30:00"

expired_calendar WARNING 2

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
22	"SUPPR 20 P VAC LMMJVS (113 ptes vacances)"
25	"SUPPR ETE LMMJVS"

leading_or_trailing_whitespaces WARNING 15

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"trips.txt"	181	"service_id"	"137 JS "
"trips.txt"	182	"service_id"	"137 JS "
"trips.txt"	183	"service_id"	"137 JS "
"trips.txt"	184	"service_id"	"137 JS "
"trips.txt"	558	"trip_short_name"	"131 A "
"stops.txt"	187	"stop_name"	"ÉCOLE oraison "
"stops.txt"	250	"stop_name"	"ECOLE st martin de brome "
"calendar.txt"	18	"service_id"	"137 JS "
"calendar.txt"	25	"service_id"	"SUPPR ETE LMMJVS "
"calendar_dates.txt"	3235	"service_id"	"137 JS "
"calendar_dates.txt"	3236	"service_id"	"137 JS "
"calendar_dates.txt"	3237	"service_id"	"137 JS "
"calendar_dates.txt"	3238	"service_id"	"137 JS "
"calendar_dates.txt"	3239	"service_id"	"137 JS "
"calendar_dates.txt"	3240	"service_id"	"137 JS "

missing_recommended_field WARNING 2

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"routes.txt"	41	"agency_id"
"routes.txt"	42	"agency_id"

missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"

mixed_case_recommended_field WARNING 855

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
`Field Text`	`Dataset`
"Schwerin, Hauptbahnhof"	Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin"	NYC Ferry
"Campo Grande Norte"	Carris

Bad examples:
`Field Text`
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

Only the first 50 of 855 affected records are displayed below.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"routes.txt"	"route_short_name"	"111 DLVA"	2
"routes.txt"	"route_long_name"	"MANOSQUE PRES COMBAUX-CENTRE VILLE"	2
"routes.txt"	"route_short_name"	"112 DLVA"	3
"routes.txt"	"route_long_name"	"MANOSQUE THOMASSINE - QUINTRANDS"	3
"routes.txt"	"route_short_name"	"113 DLVA"	4
"routes.txt"	"route_long_name"	"MANOSQUE REPASSE - VANNADES"	4
"routes.txt"	"route_short_name"	"114 DLVA"	5
"routes.txt"	"route_long_name"	"MANOSQUE ROCHETTE - TECHNOPARC"	5
"routes.txt"	"route_short_name"	"120 DLVA"	6
"routes.txt"	"route_long_name"	"ORAISON-LA BRILLANNE-VILLENEUVE-VOLX-MQE"	6
"routes.txt"	"route_short_name"	"123 DLVA"	7
"routes.txt"	"route_long_name"	"CORBIERES - SAINTE TULLE - MANOSQUE"	7
"routes.txt"	"route_short_name"	"124 DLVA"	8
"routes.txt"	"route_long_name"	"PIERREVERT - MANOSQUE"	8
"routes.txt"	"route_short_name"	"124 TAD"	9
"routes.txt"	"route_long_name"	"TAD PIERREVERT - MANOSQUE"	9
"routes.txt"	"route_short_name"	"125 TAD"	10
"routes.txt"	"route_long_name"	"BRUNET-ENTREVENNES-PUIMICHEL-LE CASTELLET-ORAISON"	10
"routes.txt"	"route_short_name"	"127 TAD"	11
"routes.txt"	"route_long_name"	"MONTFURON-MANOSQUE"	11
"routes.txt"	"route_short_name"	"131 DLVA"	12
"routes.txt"	"route_long_name"	"GREOUX - VINON - MANOSQUE"	12
"routes.txt"	"route_short_name"	"132 DLVA"	13
"routes.txt"	"route_long_name"	"RIEZ - GREOUX - MANOSQUE"	13
"routes.txt"	"route_short_name"	"133 DLVA"	14
"routes.txt"	"route_long_name"	"VALENSOLE - MANOSQUE"	14
"routes.txt"	"route_short_name"	"134 TAD"	15
"routes.txt"	"route_long_name"	"ESPARRON-QUINSON-ST LAURENT-MONTAGNAC-RIEZ"	15
"routes.txt"	"route_long_name"	"PUIMOISSON - ROUMOULES - RIEZ"	16
"routes.txt"	"route_short_name"	"136 DLVA"	17
"routes.txt"	"route_short_name"	"137 TAD"	18
"routes.txt"	"route_long_name"	"ALBIOSC - ESPARRON"	18
"routes.txt"	"route_long_name"	"VALENSOLE - BRUNET - PUIMOISSON - RIEZ"	19
"routes.txt"	"route_long_name"	"ESPARRON - RIEZ"	20
"routes.txt"	"route_long_name"	"MONTPEZAT - MONTAGNAC - RIEZ"	21
"routes.txt"	"route_long_name"	"QUINSON - ST LAURENT - QUINSON - RIEZ"	22
"routes.txt"	"route_long_name"	"ST MARTIN - ALLEMAGNE - RIEZ"	23
"routes.txt"	"route_long_name"	"VINON - VINON"	24
"routes.txt"	"route_long_name"	"LES CHABRANDS - MANOSQUE"	25
"routes.txt"	"route_long_name"	"VILLENEUVE-VOLX-MANOSQUE"	26
"routes.txt"	"route_long_name"	"ORAISON-LA BRILLANNE-MANOSQUE"	27
"routes.txt"	"route_long_name"	"VILLENEUVE - VOLX"	28
"routes.txt"	"route_long_name"	"PIERREVERT - STE TULLE"	29
"routes.txt"	"route_long_name"	"MONTFURON-MANOSQUE"	30
"routes.txt"	"route_long_name"	"ENTREVENNES - ORAISON"	31
"routes.txt"	"route_long_name"	"LA BRILLANNE - ORAISON"	32
"routes.txt"	"route_long_name"	"VALLEE DE L'ASSE - ORAISON"	33
"routes.txt"	"route_long_name"	"CORBIERES - STE TULLE"	34
"routes.txt"	"route_short_name"	"181 RPI"	35
"routes.txt"	"route_long_name"	"ALLEMAGNE - MONTAGNAC - ALLEMAGNE"	35

route_color_contrast WARNING 3

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"133 DLVA\|20190502"	14	"#0033CC"	"#000000"
"134\|20160308"	15	"#2B2E7D"	"#000000"
"135\|20160309"	16	"#851D28"	"#000000"

route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"PMR\|20190707"	40	"PMR"	"PMR"

stop_without_stop_time WARNING 7

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
119	"STOPPOINT:00549"	"DR P. JOUBERT"
185	"STOPPOINT:00691"	"LYC. DES ISCLES"
191	"STOPPOINT:102"	"PINÈDE"
251	"STP-004"	"HÔPITAL L. RAFFALLI"
252	"STP-005"	"L. L. ZAMENHOF"
253	"STP-006"	"Dr R. MATHOULIN"
254	"STP-007"	"CENTRE AQUALUDIQUE"