kentkart-duzce — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-08T01:57:16Z,
for the dataset file:///shared/kentkart-duzce_51359f08.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included


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

Counts


  • Agencies: 2
  • Blocks: 0
  • Routes: 63
  • Shapes: 116
  • Stops: 0
  • Trips: 5581

Specification Compliance report

6892 notices reported (18 errors, 6874 warnings, 0 infos)

Notice Code Severity Total
invalid_character ERROR 1

invalid_character

This field contains invalid characters, such as the replacement character ("�").

Check that text was properly encoded in UTF-8 as required by GTFS.

You can see more about this notice here.

filename (?) The name of the file containing the invalid characters. csvRowNumber (?) The row number in the CSV file where the invalid characters were found. fieldName (?) The name of the field containing the invalid characters. fieldValue (?) The value of the field containing the invalid characters.
"stops.txt" 293 "stop_name" "TOKİ MEHMET AKİF ORTA OKUL DURA��I"
missing_stop_name ERROR 1

missing_stop_name

stops.stop_name is required for location_type equal to 0, 1, or 2.

stops.stop_name is required for locations that are stops (location_type=0), stations (location_type=1) or entrances/exits (location_type=2).

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. locationType (?) `stops.location_type` of the faulty record. stopId (?) The `stops.stop_id` of the faulty record.
1084 "STOP" "10798"
start_and_end_range_out_of_order ERROR 16

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" 14362 "arrival_time" "10:40:11" "departure_time" "10:40:10"
"stop_times.txt" 14377 "arrival_time" "11:25:11" "departure_time" "11:25:10"
"stop_times.txt" 14392 "arrival_time" "12:10:11" "departure_time" "12:10:10"
"stop_times.txt" 14407 "arrival_time" "12:55:11" "departure_time" "12:55:10"
"stop_times.txt" 14422 "arrival_time" "13:40:11" "departure_time" "13:40:10"
"stop_times.txt" 14437 "arrival_time" "14:25:11" "departure_time" "14:25:10"
"stop_times.txt" 14452 "arrival_time" "15:10:11" "departure_time" "15:10:10"
"stop_times.txt" 14467 "arrival_time" "15:55:11" "departure_time" "15:55:10"
"stop_times.txt" 14482 "arrival_time" "16:25:11" "departure_time" "16:25:10"
"stop_times.txt" 14497 "arrival_time" "16:55:11" "departure_time" "16:55:10"
"stop_times.txt" 14512 "arrival_time" "17:30:11" "departure_time" "17:30:10"
"stop_times.txt" 14527 "arrival_time" "18:00:11" "departure_time" "18:00:10"
"stop_times.txt" 14542 "arrival_time" "18:30:11" "departure_time" "18:30:10"
"stop_times.txt" 14557 "arrival_time" "19:00:11" "departure_time" "19:00:10"
"stop_times.txt" 14572 "arrival_time" "19:30:11" "departure_time" "19:30:10"
"stop_times.txt" 14587 "arrival_time" "20:15:11" "departure_time" "20:15:10"
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 6864

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 6864 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.
"agency.txt" "agency_name" "DÜZCE BELEDİYESİ" 2
"agency.txt" "agency_name" "DÜZCE ULAŞIM AŞ" 3
"stops.txt" "stop_name" "LALEZAR KONAKLARI DURAĞI" 2
"stops.txt" "stop_name" "YENİKENT POLİS MERKEZİ DURAĞI" 3
"stops.txt" "stop_name" "ŞEHİR MEZARLIĞI DURAĞI" 4
"stops.txt" "stop_name" "İSMET PAŞA OKUL DURAĞI" 5
"stops.txt" "stop_name" "ŞEHİT CİHAN AKSARI" 6
"stops.txt" "stop_name" "ŞEHİT CİHAN AKSARI" 7
"stops.txt" "stop_name" "FÜPAŞ FİDANLIK" 8
"stops.txt" "stop_name" "FÜPAŞ FİDANLIK" 9
"stops.txt" "stop_name" "TÜRKOĞLU SİTESİ" 10
"stops.txt" "stop_name" "TÜRKOĞLU SİTESİ" 11
"stops.txt" "stop_name" "ZAFER HALI SAHA" 12
"stops.txt" "stop_name" "ZAFER HALI SAHA" 13
"stops.txt" "stop_name" "AZİZİYE 1050 BULVARI" 14
"stops.txt" "stop_name" "AZİZİYE 1050 BULVARI" 15
"stops.txt" "stop_name" "PAZARYERİ 1053. SOKAK DURAĞI" 16
"stops.txt" "stop_name" "ESKİ PAZARYERİ" 17
"stops.txt" "stop_name" "ESKİ PAZARYERİ" 18
"stops.txt" "stop_name" "ESKİ PAZARYERİ ORTASI" 19
"stops.txt" "stop_name" "MERGİÇ MEYDAN" 20
"stops.txt" "stop_name" "MERGİÇ MEYDAN" 21
"stops.txt" "stop_name" "MERGİÇ CAMİ" 22
"stops.txt" "stop_name" "MERGİÇ CAMİ" 23
"stops.txt" "stop_name" "MERGİÇ DEĞİRMEN" 24
"stops.txt" "stop_name" "MERGİÇ DEĞİRMEN" 25
"stops.txt" "stop_name" "MERGİÇ TALEBE YURDU" 26
"stops.txt" "stop_name" "MERGİÇ TALEBE YURDU" 27
"stops.txt" "stop_name" "KÜCÜK SANAYİ PETROL OFİSİ" 28
"stops.txt" "stop_name" "HAL DURAĞI" 29
"stops.txt" "stop_name" "HAL DURAĞI" 30
"stops.txt" "stop_name" "ESKİ HALK PAZARI" 31
"stops.txt" "stop_name" "ESKİ HALK PAZARI" 32
"stops.txt" "stop_name" "SOSYAL HİZMETLER DURAĞI" 33
"stops.txt" "stop_name" "SOSYAL HİZMETLER DURAĞI" 34
"stops.txt" "stop_name" "15 TEMMUZ LİSESİ" 35
"stops.txt" "stop_name" "HALK EĞİTİM" 36
"stops.txt" "stop_name" "15 TEMMUZ ANADOLU LİSESİ" 37
"stops.txt" "stop_name" "15 TEMMUZ ANADOLU LİSESİ" 38
"stops.txt" "stop_name" "DEVLET HASTANESİ ACİL" 39
"stops.txt" "stop_name" "DEVLET HASTANESİ ACİL" 40
"stops.txt" "stop_name" "GÜNLÜ CAMİ" 41
"stops.txt" "stop_name" "GÜNLÜ CAMİ" 42
"stops.txt" "stop_name" "DİŞ HASTANESİ" 43
"stops.txt" "stop_name" "DİŞ HASTANESİ" 44
"stops.txt" "stop_name" "AL GÜN SİTESİ" 45
"stops.txt" "stop_name" "AL GÜN SİTESİ" 46
"stops.txt" "stop_name" "BAĞDAT CAMİ" 47
"stops.txt" "stop_name" "BAĞDAT CAMİ" 48
"stops.txt" "stop_name" "GÜNLÜ PUSAT YAPI" 49
route_color_contrast WARNING 2

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.
"20053" 55 "#26FBFF" "#FFFFFF"
"20054" 56 "#68DEFF" "#FFFFFF"
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`.
"30010" 64 "C1" "C1 Gidiş-C1 Bitiş"
unused_shape WARNING 6

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"200150" 19313
"200151" 19315
"200190" 23719
"200191" 23898
"200180" 24096
"200181" 24252