evolity — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T11:21:44Z,
for the dataset file:///shared/evolity_1d8a77dd.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


  • evolity

Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Language:
Multiple languages
Feed Start Date:
2026-07-19
Feed End Date:
2027-06-11

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 16
  • Shapes: 45
  • Stops: 654
  • Trips: 1606

Specification Compliance report

298 notices reported (0 errors, 298 warnings, 0 infos)

Notice Code Severity Total
mixed_case_recommended_field WARNING 3

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.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"agency.txt" "agency_name" "evolity" 2
"stops.txt" "stop_name" "8mai" 492
"stops.txt" "stop_name" "8mai2" 510
non_ascii_or_non_printable_char WARNING 283

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

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

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"calendar_dates.txt" 385 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 386 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 387 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 388 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 389 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 390 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 391 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 392 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 393 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 394 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 395 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 396 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 397 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 398 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 399 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 400 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 401 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 402 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 403 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 404 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 405 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 406 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 407 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 408 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 409 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 410 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 411 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 412 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 413 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 414 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 415 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 416 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 417 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 418 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 419 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 420 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 421 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 422 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 423 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 424 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 425 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 426 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 427 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 428 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 429 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 430 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 431 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 432 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 433 "service_id" "100899-40100339-AFF_LÀV"
"calendar_dates.txt" 434 "service_id" "100899-40100339-AFF_LÀV"
stop_too_far_from_shape WARNING 7

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
447 "100899-0401_10600" "100899-401106000001" 15058 "100899-GLGV" "Gare Tgv" [47.584672,6.896230000000001] 168.69322251102207
405 "100899-0401_10651" "100899-401106510001" 14748 "100899-GLGV" "Gare Tgv" [47.584516,6.896259] 171.1726299834075
488 "100899-0403_10586" "100899-403105860025" 15451 "100899-LBLO2" "LA Blongeotte" [47.474145193805754,6.770719974353947] 125.63008648679364
488 "100899-0403_10586" "100899-403105860025" 15452 "100899-LFON2" "LES Fontaines" [47.476304566027245,6.772437319120749] 155.97501499683648
488 "100899-0403_10586" "100899-403105860025" 15453 "100899-BOUT2" "Boutonniers" [47.47890994441257,6.775456421165509] 214.58455003070318
488 "100899-0403_10586" "100899-403105860025" 15454 "100899-FONT2" "Fontenotte" [47.480936519862134,6.779468794148074] 177.75961943513954
450 "100899-0401_10598" "100899-401106480032" 15101 "100899-GLGV" "Gare Tgv" [47.584524,6.896266000000001] 170.39730559391882
stops_match_shape_out_of_order WARNING 4

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
1301 "100899-0409_10655" "100899-409106550001" 52964 "100899-BOUF2" "Bourguignon LES Forges" [47.40616261355316,6.769211645454493] 52963 "100899-BOUR2" "Bourguignon" [47.392722,6.774506]
102 "100899-0398_10624" "100899-398106240001" 4683 "100899-LMOT" "LA Montagne" [47.50255642180817,6.855287954446925] 4682 "100899-LMON2" "LA Montagne" [47.50217534110048,6.85512050891379]
1299 "100899-0409_10606" "100899-409106060004" 52888 "100899-BOUF2" "Bourguignon LES Forges" [47.40616261355316,6.769211645454493] 52887 "100899-BOUR2" "Bourguignon" [47.392733,6.774511999999999]
59 "100899-0398_10579" "100899-398106230001" 2678 "100899-LMOT" "LA Montagne" [47.50253938709876,6.855276943304423] 2677 "100899-LMON2" "LA Montagne" [47.50253300000001,6.855273]
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260801" "20260817" "20270611"