pleven-bg — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-20T04:29:03Z,
for the dataset file:///shared/pleven-bg_32a39c18.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


  • "Тролейбусен транспорт" ЕООД - Плевен

Feed Info


Publisher Name:
Тролейбусен транспорт ЕООД - Плевен
Feed Email:
troleipleven@gmail.com
Feed Language:
Bulgarian
Feed Start Date:
2026-01-01
Feed End Date:
2026-12-31

Files included


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

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 45
  • Shapes: 45
  • Stops: 186
  • Trips: 2389

Specification Compliance report

2408 notices reported (0 errors, 22 warnings, 2386 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.
4 "1.1A"
5 "1.2A"
45 "20.1"
46 "20.2"
69 "44.3"
70 "44.4"
missing_recommended_field WARNING 1

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_version"
mixed_case_recommended_field WARNING 14

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.
"stops.txt" "stop_name" "ПМЗ (PMZ)" 21
"stops.txt" "stop_name" "ПМЗ (PMZ)" 22
"stops.txt" "stop_name" "ОКС (OKS)" 36
"stops.txt" "stop_name" "ОКС (OKS)" 37
"stops.txt" "stop_name" "бл. 311 (bl. 311)" 70
"stops.txt" "stop_name" "бл. 311 (bl. 311)" 71
"stops.txt" "stop_name" "бл. 313 (bl. 313)" 72
"stops.txt" "stop_name" "бл. 313 (bl. 313)" 73
"stops.txt" "stop_name" "бл. 324 (bl. 324)" 74
"stops.txt" "stop_name" "бл. 324 (bl. 324)" 75
"stops.txt" "stop_name" "бл. 335 (bl. 335)" 82
"stops.txt" "stop_name" "бл. 335 (bl. 335)" 83
"stops.txt" "stop_name" "бл. 314 (bl. 314)" 93
"stops.txt" "stop_name" "бл. 345 (bl. 345)" 159
non_ascii_or_non_printable_char WARNING 1

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"fare_attributes.txt" 2 "fare_id" "билет (ticket)"
unsorted_stop_times INFO 2386

unsorted_stop_times

Stop times are not sorted by trip_id and stop_sequence.

'stop_times.txt' entries for a given trip are not sorted by stop_sequence, or are not contiguous in the file.

You can see more about this notice here.

Only the first 50 of 2386 affected records are displayed below.

tripId (?) The faulty record's trip_id. startCsvRowNumber (?) CSV row number of the first stop_times entry for this trip. endCsvRowNumber (?) CSV row number of the last stop_times entry for this trip.
"52050" 3448 4852
"12003AA" 34346 34430
"52051" 3449 4853
"76020" 11214 11970
"52054" 3452 4856
"76021" 11215 11971
"52055" 3453 4857
"76022" 11216 11972
"52052" 3450 4854
"76023" 11217 11973
"52053" 3451 4855
"76024" 11218 11974
"52058" 3456 4860
"76025" 11219 11975
"52059" 3457 4861
"76026" 11220 11976
"52056" 3454 4858
"76027" 11221 11977
"52057" 3455 4859
"76028" 11222 11978
"76029" 11223 11979
"11013A" 32982 33080
"52061" 3459 4863
"52062" 3460 4864
"52060" 3458 4862
"52065" 3463 4867
"76010" 11204 11960
"442024" 27340 27775
"913009" 29439 29649
"192002" 31325 31775
"52066" 3464 4868
"76011" 11205 11961
"442025" 27341 27776
"192003" 31326 31776
"52063" 3461 4865
"76012" 11206 11962
"442026" 27342 27777
"913007" 29437 29647
"192004" 31327 31777
"52064" 3462 4866
"76013" 11207 11963
"442027" 27343 27778
"913008" 29438 29648
"192005" 31328 31778
"52069" 3467 4871
"76014" 11208 11964
"442028" 27344 27779
"913005" 29435 29645
"192006" 31329 31779
"76015" 11209 11965