pt-transportasi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-22T00:09:46Z,
for the dataset file:///shared/pt-transportasi_be76476a.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. fare_attributes.txt
  4. fare_rules.txt
  5. frequencies.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. ticketing_deep_links.txt
  11. ticketing_identifiers.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 240
  • Shapes: 700
  • Stops: 8091
  • Trips: 700

Specification Compliance report

4069 notices reported (0 errors, 4062 warnings, 7 infos)

Notice Code Severity Total
expired_calendar WARNING 2

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.
7 "HJ"
8 "X"
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"
missing_timepoint_value WARNING 4038

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "10A-L02" 0
3 "10A-L02" 1
4 "10A-L02" 2
5 "10A-L02" 3
6 "10A-L02" 4
11 "10A-L02" 9
14 "10A-L02" 12
31 "10A-L02" 29
35 "10A-L02" 33
62 "10A-R01" 0
63 "10A-R01" 1
64 "10A-R01" 2
65 "10A-R01" 3
66 "10A-R01" 4
71 "10A-R01" 9
74 "10A-R01" 12
91 "10A-R01" 29
95 "10A-R01" 33
106 "10B-R01" 0
107 "10B-R01" 1
108 "10B-R01" 2
109 "10B-R01" 3
110 "10B-R02" 0
111 "10B-R02" 1
112 "10B-R02" 2
113 "10B-R02" 3
114 "10B-R02" 4
115 "10B-R02" 5
116 "10B-R02" 6
381 "11C-L03" 0
383 "11C-L03" 2
384 "11C-L03" 3
389 "11C-L03" 8
391 "11C-L03" 10
393 "11C-L03" 12
401 "11D-R04" 0
402 "11D-R04" 1
403 "11D-R04" 2
404 "11D-R04" 3
412 "11D-R04" 11
413 "11D-R04" 12
414 "11D-R04" 13
415 "11D-R04" 14
416 "11D-R04" 15
417 "11D-R04" 16
418 "11D-R04" 17
419 "11D-R04" 18
420 "11D-R04" 19
421 "11D-R04" 20
422 "11D-R04" 21
mixed_case_recommended_field WARNING 18

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" "UPT. LLHD 1" 94
"stops.txt" "stop_name" "UPT. LLHD 2" 95
"stops.txt" "stop_name" "DPP FPI" 260
"stops.txt" "stop_name" "DPR MPR 1" 261
"stops.txt" "stop_name" "DPR MPR 2" 262
"stops.txt" "stop_name" "LPP RRI 1" 1807
"stops.txt" "stop_name" "LPP RRI 2" 1808
"stops.txt" "stop_name" "RS PIK" 2643
"stops.txt" "stop_name" "RS PIK 2" 2644
"stops.txt" "stop_name" "SIT I-II PIK" 4379
"stops.txt" "stop_name" "SIT III PIK" 4380
"stops.txt" "stop_name" "SMP PGRI 9" 4471
"stops.txt" "stop_name" "STT PLN" 4617
"stops.txt" "stop_name" "STIE IBEK" 4647
"stops.txt" "stop_name" "SDN CBU 1" 6152
"stops.txt" "stop_name" "SDN CBU 10" 6154
"stops.txt" "stop_name" "SMK PGRI 35" 6703
"stops.txt" "stop_name" "IKEA JGC" 7729
stops_match_shape_out_of_order WARNING 3

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
415 "JAK.27-R01_shp" "JAK.27-R01" 17414 "B02143P" "Lion Metal 2" [-6.185841015262161,106.95209308501389] 17413 "B02142P" "Lion Metal 1" [-6.185959403305619,106.95275253703693]
505 "JAK.30-R01_shp" "JAK.30-R01" 17791 "B04635P" "Sekolah Katolik Abdi Siswa" [-6.181619065993717,106.77982803624388] 17790 "B05053P" "Simpang Patra Kepa" [-6.182972623531195,106.77993831344442]
416 "2o29" "JAK.27-L01" 17321 "B00615P" "Gempol Baru 2" [-6.186331037650249,106.95470418183822] 17320 "B02143P" "Lion Metal 2" [-6.1859415125171,106.95207721948228]
unknown_column INFO 5

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"agency.txt" "ticketing_deep_link_id" 8
"routes.txt" "ticketing_deep_link_id" 11
"stop_times.txt" "ticketing_type" 13
"trips.txt" "ticketing_trip_id" 11
"trips.txt" "ticketing_type" 12
unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"ticketing_deep_links.txt"
"ticketing_identifiers.txt"