Search
  1. Home
  2. Cyprus Feeds
  3. lpt
  4. Source Data Validation Report

lpt — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-25T06:22:26Z,
for the dataset file:///shared/lpt_a0fb100e.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: 133
  • Shapes: 89
  • Stops: 1038
  • Trips: 2930

Specification Compliance report

63 notices reported (19 errors, 44 warnings, 0 infos)

Notice Code Severity Total
foreign_key_violation ERROR 19

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20000021" 4
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20000031" 5
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20050022" 17
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20070041" 24
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20080011" 26
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20080012" 27
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20080031" 29
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20100011" 34
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20100012" 35
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20120011" 39
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20120012" 40
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20170021" 55
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20260021" 72
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20260022" 73
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20310011" 84
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20310012" 85
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20370031" 104
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20400011" 122
"fare_rules.txt" "route_id" "routes.txt" "route_id" "20400012" 123
duplicate_route_name WARNING 18

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
3 "20000012" 4 "20000032" "430" "Pervolia - Kiti - Dromoloxia - Airport - Larnaca statio" 3 "10"
17 "20070011" 19 "20070021" "420" "Larnaca Station - Kamares - Kalo Chorio" 3 "10"
20 "20070022" 21 "20070042" "420" "Kalo Chorio - Kamares - (Lyceem) - Larnaca Station" 3 "10"
25 "20090022" 26 "20090032" "422" "Kamares 2 -Zinonas-Vergina-New Hospital - Larnaca St." 3 "10"
31 "20120022" 32 "20120032" "424" "Pyla - CTO - Larnaca Station" 3 "10"
66 "20300011" 68 "20300021" "405" "Vavatsinia - Pano Lefkara - Kato Lefkara - Skarinou - K" 3 "10"
78 "20360011" 82 "20360031" "409" "Larnaca St. - Lympia - Dali - Pera Chorio - Alampra St." 3 "10"
79 "20360012" 83 "20360032" "409" "Alampra Station Pera Chorio - Dali - Lympia - Larnaca S" 3 "10"
87 "20370022" 88 "20370032" "410" "Delikipos-Kornos-Kalo Chorio-Vergina Lyceum- Larnaca St" 3 "10"
89 "20380011" 93 "20380031" "412" "Larnaca Station - Alethriko - Anglisides - Anafotia - A" 3 "10"
91 "20380021" 95 "20380041" "412" "Larnaca Station - Kofinou Station" 3 "10"
92 "20380022" 96 "20380042" "412" "Kofinou Station - Larnaca Station" 3 "10"
91 "20380021" 97 "20380051" "412" "Larnaca Station - Kofinou Station" 3 "10"
92 "20380022" 98 "20380052" "412" "Kofinou Station - Larnaca Station" 3 "10"
103 "20390031" 105 "20390051" "413" "Kofinou Station - Larnaca Station" 3 "10"
104 "20390032" 106 "20390052" "413" "Larnaca Station - Kofinou Station" 3 "10"
109 "20410011" 113 "20410031" "415" "Athienou - Avdellero - Aradippou - Larnaca Station" 3 "10"
110 "20410012" 114 "20410032" "415" "Larnaca Station - Aradippou - Avdellero - Athienou" 3 "10"
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"
same_name_and_description_for_stop WARNING 22

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`.
57 "4637" "Delikipos"
186 "6137" "Oktagono"
289 "6250" "Poseidonio"
290 "6251" "Poseidonio"
429 "6410" "Debenhams"
506 "6491" "Istiklal"
519 "6507" "Makenzy"
526 "6514" "Kyrineias"
527 "6515" "Makenzy"
530 "6519" "Kastalias"
560 "6551" "Istampoul"
624 "6619" "Keryneias"
717 "6715" "Keryneias"
730 "6738" "Papaflessa"
764 "6776" "Spetson"
782 "6794" "Leonidou"
825 "6846" "Syneseio"
936 "6972" "Lageia"
937 "6973" "Lageia"
1035 "7843" "Everest"
1036 "7844" "Pigasou"
1037 "7845" "Alpeon"