kentkart-adana — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-08T01:46:48Z,
for the dataset file:///shared/kentkart-adana_e1a34489.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: 15
  • Blocks: 0
  • Routes: 291
  • Shapes: 0
  • Stops: 0
  • Trips: 32808

Specification Compliance report

33971 notices reported (5 errors, 33966 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" 2223 "stop_name" "G��KÇELER MAH. 1A"
invalid_float ERROR 4

invalid_float

A field cannot be parsed as a floating point number.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"shapes.txt" 564 "shape_pt_lat" "null"
"shapes.txt" 564 "shape_pt_lon" "null"
"shapes.txt" 565 "shape_pt_lat" "null"
"shapes.txt" 565 "shape_pt_lon" "null"
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 33963

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 33963 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.
"stops.txt" "stop_name" "PERON GİRİŞ" 40
"stops.txt" "stop_name" "00ZİYAPASA BUL.-4" 41
"stops.txt" "stop_name" "11ZİYAPASA BUL.-7" 42
"stops.txt" "stop_name" "G178 - ESKİ TOPEL" 46
"stops.txt" "stop_name" "G178 - GÖKKUŞAĞI GERİSİ" 48
"stops.txt" "stop_name" "G178 - TO CAMİ" 49
"stops.txt" "stop_name" "G178 - 100. yıl giriş" 50
"stops.txt" "stop_name" "8/B eski karakol" 51
"stops.txt" "stop_name" "ATATÜRK CADDESİ 5B" 55
"stops.txt" "stop_name" "M.KEMAL PAŞA BULVARI 7. DURAK" 56
"stops.txt" "stop_name" "M.KEMAL PAŞA BULVARI 11. DURAK ( ASKİ )" 57
"stops.txt" "stop_name" "ATATÜRK CADDESİ 2. DURAK" 58
"stops.txt" "stop_name" "DÖRTYOL GİRİŞ" 59
"stops.txt" "stop_name" "MERKEZ CAMİ" 60
"stops.txt" "stop_name" "FUZULİ CADDESİ 1. DURAK" 61
"stops.txt" "stop_name" "M.KEMAL PAŞA BULVARI 10. DURAK" 62
"stops.txt" "stop_name" "M.KEMAL PAŞA BULVARI 5. DURAK (YÜREĞİR DEVLET HASTANESİ)" 63
"stops.txt" "stop_name" "BALCALI HASTANESİ 1A" 64
"stops.txt" "stop_name" "CAN ÖZŞAHİNOĞLU BLV. 1A" 65
"stops.txt" "stop_name" "CAN ÖZŞAHİNOĞLU BLV. 2A" 66
"stops.txt" "stop_name" "GÜNEY KAMPÜS BLV. 4B" 67
"stops.txt" "stop_name" "GÜNEY KAMPÜS BLV. 3B" 68
"stops.txt" "stop_name" "SARIÇAM ERKEK ÖĞRENCİ YURDU. 1" 69
"stops.txt" "stop_name" "YURTLAR ÖNÜ 1A" 70
"stops.txt" "stop_name" "DR. MİTHAT ÖZSAN BLV. 6A" 71
"stops.txt" "stop_name" "GÜNEY KAMPÜS BLV. 3A" 72
"stops.txt" "stop_name" "GÜNEY KAMPÜS BLV. 4A" 73
"stops.txt" "stop_name" "GÜNEY KAMPÜS BLV. 5A" 74
"stops.txt" "stop_name" "BALCALI HASTANESİ 2A" 75
"stops.txt" "stop_name" "BALCALI HASTANESİ 3A" 76
"stops.txt" "stop_name" "BALCALI HASTANESİ 4A" 77
"stops.txt" "stop_name" "BALCALI HASTANESİ 1B" 78
"stops.txt" "stop_name" "GÜNEY KAMPÜS BLV. 6A" 87
"stops.txt" "stop_name" "CAN ÖZŞAHİNOĞLU BLV. 3A" 88
"stops.txt" "stop_name" "ÇATALAN CADDESİ 1B" 89
"stops.txt" "stop_name" "STADYUM DÖNÜŞ DURAĞI" 90
"stops.txt" "stop_name" "ÇATALAN CADDESİ 3B" 91
"stops.txt" "stop_name" "ÇATALAN CADDESİ 4B" 92
"stops.txt" "stop_name" "ÇATALAN CADDESİ 5B" 93
"stops.txt" "stop_name" "ÇATALAN CADDESİ 7B" 94
"stops.txt" "stop_name" "ÇATALAN CADDESİ 8B" 95
"stops.txt" "stop_name" "ÇATALAN CADDESİ 9B" 96
"stops.txt" "stop_name" "ÇATALAN CADDESİ 9A" 97
"stops.txt" "stop_name" "ÇATALAN CADDESİ 8A" 98
"stops.txt" "stop_name" "ÇATALAN CADDESİ 7A" 99
"stops.txt" "stop_name" "ÇATALAN CADDESİ 6A" 100
"stops.txt" "stop_name" "ÇATALAN CADDESİ 5A" 101
"stops.txt" "stop_name" "ÇATALAN CADDESİ 4A" 102
"stops.txt" "stop_name" "ÇATALAN CADDESİ 3A" 103
"stops.txt" "stop_name" "ÇATALAN CADDESİ 2A" 104
route_long_name_contains_short_name WARNING 2

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`.
"00114" 12 "114" "114 A Optimum Avm-Real Avm"
"00119" 17 "119" "119 A - Eski Vilayet-Yeniyayla"