GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T19:22:50Z,
for the dataset file:///shared/bali-transit-project_89d73596.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
N/A
Feed Language:
Indonesian
Feed Start Date:
2025-01-01
Feed End Date:
2027-12-31

Files included

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

Counts

  • Agencies: 3
  • Blocks: 0
  • Routes: 7
  • Shapes: 12
  • Stops: 272
  • Trips: 12

Specification Compliance report

376 notices reported (0 errors, 376 warnings, 0 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 5

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"K2B-d1" 4423 17172.0 753 4422 17172.0 752 0.5510454305510735
"K5B-d1" 10592 12767.0 370 10591 12767.0 369 0.5510454305510735
"K1B-d0" 1255 30267.0 1253 1254 30267.0 1252 0.8039660544872096
"K1B-d1" 1435 2433.0 119 1434 2433.0 118 0.3869767599792428
"TS1-d0" 10855 5720.0 225 10854 5720.0 224 0.4936117399839285
equal_shape_distance_same_coordinates WARNING 2

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"K1B-d1" 1730 9451.0 414 1729 9451.0 413
"K3B-d0" 5154 10678.0 487 5153 10678.0 486
missing_timepoint_value WARNING 367

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 367 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 "K1B-d0-ref" 0
3 "K1B-d0-ref" 1
4 "K1B-d0-ref" 2
5 "K1B-d0-ref" 3
6 "K1B-d0-ref" 4
7 "K1B-d0-ref" 5
8 "K1B-d0-ref" 6
9 "K1B-d0-ref" 7
10 "K1B-d0-ref" 8
11 "K1B-d0-ref" 9
12 "K1B-d0-ref" 10
13 "K1B-d0-ref" 11
14 "K1B-d0-ref" 12
15 "K1B-d0-ref" 13
16 "K1B-d0-ref" 14
17 "K1B-d0-ref" 15
18 "K1B-d0-ref" 16
19 "K1B-d0-ref" 17
20 "K1B-d0-ref" 18
21 "K1B-d0-ref" 19
22 "K1B-d0-ref" 20
23 "K1B-d0-ref" 21
24 "K1B-d0-ref" 22
25 "K1B-d0-ref" 23
26 "K1B-d0-ref" 24
27 "K1B-d0-ref" 25
28 "K1B-d0-ref" 26
29 "K1B-d0-ref" 27
30 "K1B-d0-ref" 28
31 "K1B-d0-ref" 29
32 "K1B-d0-ref" 30
33 "K1B-d0-ref" 31
34 "K1B-d0-ref" 32
35 "K1B-d0-ref" 33
36 "K1B-d0-ref" 34
37 "K1B-d0-ref" 35
38 "K1B-d0-ref" 36
39 "K1B-d0-ref" 37
40 "K1B-d0-ref" 38
41 "K1B-d0-ref" 39
42 "K1B-d1-ref" 0
43 "K1B-d1-ref" 1
44 "K1B-d1-ref" 2
45 "K1B-d1-ref" 3
46 "K1B-d1-ref" 4
47 "K1B-d1-ref" 5
48 "K1B-d1-ref" 6
49 "K1B-d1-ref" 7
50 "K1B-d1-ref" 8
51 "K1B-d1-ref" 9
stop_too_far_from_shape WARNING 1

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
7 "K3B-d1" "K3B-d1-ref" 166 "node_10600339104" "Gatsu 1" [-8.636596007503611,115.21842906510184] 100.0820526346376
stops_match_shape_out_of_order WARNING 1

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.
6 "K3B-d0" "K3B-d0-ref" 160 "node_10600262560" "Gatsu Barat" [-8.637327129492546,115.17558840173395] 159 "node_10600262558" "Simpang Gunung Catur" [-8.636408341643492,115.19067984442063]