GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-20T02:34:11Z,
for the dataset file:///shared/marchiquitasrl_6901d441.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Mar Chiquita SRL.

Feed Info

Publisher Name:
ADCO
Publisher URL:
http://adco.tk
Feed Email:
N/A
Feed Language:
Spanish

Files included

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

Counts

  • Agencies: 0
  • Blocks: 0
  • Routes: 3
  • Shapes: 12
  • Stops: 22
  • Trips: 29

Specification Compliance report

69 notices reported (0 errors, 67 warnings, 2 infos)

Notice Code Severity Total
expired_calendar WARNING 6

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.
2 "1"
3 "2"
4 "3"
5 "4"
6 "5"
7 "6"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 47

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.
"agency.txt" 2 "agency_id"
"feed_info.txt" 2 "feed_start_date"
"feed_info.txt" 2 "feed_end_date"
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
"fare_attributes.txt" 5 "agency_id"
"fare_attributes.txt" 6 "agency_id"
"fare_attributes.txt" 7 "agency_id"
"fare_attributes.txt" 8 "agency_id"
"fare_attributes.txt" 9 "agency_id"
"fare_attributes.txt" 10 "agency_id"
"fare_attributes.txt" 11 "agency_id"
"fare_attributes.txt" 12 "agency_id"
"fare_attributes.txt" 13 "agency_id"
"fare_attributes.txt" 14 "agency_id"
"fare_attributes.txt" 15 "agency_id"
"fare_attributes.txt" 16 "agency_id"
"fare_attributes.txt" 17 "agency_id"
"fare_attributes.txt" 18 "agency_id"
"fare_attributes.txt" 19 "agency_id"
"fare_attributes.txt" 20 "agency_id"
"fare_attributes.txt" 21 "agency_id"
"fare_attributes.txt" 22 "agency_id"
"fare_attributes.txt" 23 "agency_id"
"fare_attributes.txt" 24 "agency_id"
"fare_attributes.txt" 25 "agency_id"
"fare_attributes.txt" 26 "agency_id"
"fare_attributes.txt" 27 "agency_id"
"fare_attributes.txt" 28 "agency_id"
"fare_attributes.txt" 29 "agency_id"
"fare_attributes.txt" 30 "agency_id"
"fare_attributes.txt" 31 "agency_id"
"fare_attributes.txt" 32 "agency_id"
"fare_attributes.txt" 33 "agency_id"
"fare_attributes.txt" 34 "agency_id"
"fare_attributes.txt" 35 "agency_id"
"fare_attributes.txt" 36 "agency_id"
"fare_attributes.txt" 37 "agency_id"
"fare_attributes.txt" 38 "agency_id"
"fare_attributes.txt" 39 "agency_id"
"fare_attributes.txt" 40 "agency_id"
"fare_attributes.txt" 41 "agency_id"
"fare_attributes.txt" 42 "agency_id"
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
mixed_case_recommended_field WARNING 12

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.
"trips.txt" "trip_short_name" "DIRECTO diario" 2
"trips.txt" "trip_short_name" "DIRECTO diario" 3
"trips.txt" "trip_short_name" "DIRECTO diario" 4
"trips.txt" "trip_short_name" "INTERMEDIO diario" 6
"trips.txt" "trip_short_name" "INTERMEDIO diario" 7
"trips.txt" "trip_short_name" "INTERMEDIO diario" 8
"trips.txt" "trip_short_name" "INTERMEDIO diario" 9
"trips.txt" "trip_short_name" "INTERMEDIO diario" 10
"trips.txt" "trip_short_name" "INTERMEDIO diario" 15
"trips.txt" "trip_short_name" "INTERMEDIO diario" 16
"trips.txt" "trip_short_name" "INTERMEDIO diario" 17
"trips.txt" "trip_short_name" "INTERMEDIO diario" 18
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.
"20260620" "20170101" "20171231"
trip_headsign_matches_intermediate_stop INFO 1

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
30 "029" "Córdoba" "00" 3 "01"
trip_with_shape_dist_traveled_but_no_shape_distances INFO 1

trip_with_shape_dist_traveled_but_no_shape_distances

A trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt.

When stop times define distance values but the shape does not carry matching distances on every point, consumers cannot use those distances to align stops to the shape geometry reliably. This inconsistency may cause incorrect routing or display behaviour.

Note: Only the first stop time carrying a shape_dist_traveled value is referenced in the notice; this is a representative row rather than an exhaustive list.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record in trips.txt. tripId (?) The trip_id of the faulty trip. shapeId (?) The shape_id referenced by the trip. stopTimeCsvRowNumber (?) The row number of the first stop_times.txt record for this trip that contains a shape_dist_traveled value. Provided as a representative location; other stop times for the same trip may also carry distance values.
20 "019" "5" 22