GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-06-19T15:55:14Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Ministry of Transport Communication and Works
Publisher URL:
http://www.mcw.gov.cy/
Feed Email:
N/A
Feed Language:
English

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 57
  • Shapes: 48
  • Stops: 122
  • Trips: 775

Specification Compliance report

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

Notice Code Severity Total
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 3

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.
"feed_info.txt" 2 "feed_start_date"
"feed_info.txt" 2 "feed_end_date"
"feed_info.txt" 2 "feed_version"
mixed_case_recommended_field WARNING 114

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 114 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.
"trips.txt" "trip_headsign" "NORTH LIMASSOL" 3
"trips.txt" "trip_headsign" "NORTH LIMASSOL" 5
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 7
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 9
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 10
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 12
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 14
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 27
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 29
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 31
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 59
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 61
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 79
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 81
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 103
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 105
"trips.txt" "trip_headsign" "CUT-PAFOS" 130
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 132
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 134
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 148
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 150
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 152
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 154
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 156
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 159
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 161
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 172
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 174
"trips.txt" "trip_headsign" "NORTH LIMASSOL" 178
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 190
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 202
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 204
"trips.txt" "trip_headsign" "EAC-PAFOS" 213
"trips.txt" "trip_headsign" "L. AKRITA (NIC)" 215
"trips.txt" "trip_headsign" "CUT-PAFOS" 216
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 218
"trips.txt" "trip_headsign" "L. AKRITA (NIC)" 225
"trips.txt" "trip_headsign" "CUT-PAFOS" 239
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 244
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 259
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 261
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 263
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 266
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 268
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 270
"trips.txt" "trip_headsign" "LARNACA (ST GEO.)" 278
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 312
"trips.txt" "trip_headsign" "AG.NAPA-PARALIMNI" 314
"trips.txt" "trip_headsign" "NORTH LIMASSOL" 323
"trips.txt" "trip_headsign" "CUT-PAFOS" 327
same_name_and_description_for_stop WARNING 1

same_name_and_description_for_stop

Same name and description for stop.

The GTFS spec defines stops.txt stop_description as:

Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty record. stopDesc (?) The faulty record's `stop_desc`.
79 "6101" "Dimitras"