issues
search
MobilityData
/
gtfs-realtime-validator
Java-based tool that validates General Transit Feed Specification (GTFS)-realtime feeds
Other
41
stars
10
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
trip_id not provided for blocks with reoccurring stop_ids
#36
barbeau
opened
2 years ago
0
Trips with the same vehicle_id should belong to the same block
#35
barbeau
opened
2 years ago
0
start_time for frequency-based trips exact_times=0 is immutable
#34
barbeau
opened
2 years ago
3
Speed up gtfs-validator component build
#33
barbeau
opened
2 years ago
3
Move StopLocationTypeValidator to gtfs-validator library
#32
barbeau
opened
2 years ago
0
Optimize fetching feeds - compression and HTTP header "if modified"
#31
barbeau
opened
2 years ago
3
Add tests for big feeds
#30
barbeau
opened
2 years ago
8
GTFS-rt feed should meet a minimum HTTP request success rate
#29
barbeau
opened
2 years ago
3
Should early arrivals/departures be propagated across timepoints?
#28
barbeau
opened
2 years ago
0
Should StopTimeUpdates be propagated across trips in the same block?
#27
barbeau
opened
2 years ago
17
How long should TripUpdates appear before start of trip?
#26
barbeau
opened
2 years ago
2
Should Service Alert IDs change when alert content changes?
#25
barbeau
opened
2 years ago
0
Check whether trips that are predicted to be over are included in the feed
#24
barbeau
opened
2 years ago
0
Check that the delay field is consistent with difference between the scheduled and predicted times
#23
barbeau
opened
2 years ago
4
VehiclePositions - Check that there is at most one vehicle assigned to each trip
#22
barbeau
opened
2 years ago
4
Check that there is at most one StopTimeUpdate for each stop in a trip
#21
barbeau
opened
2 years ago
1
Check that there is at most one TripUpdate per scheduled trip_id
#20
barbeau
opened
2 years ago
3
New rule - Check Alert EntitySelector field integrity
#19
barbeau
opened
2 years ago
7
Per stop predictions - providers shouldn't drop arrivals until after the bus passes the stop
#18
barbeau
opened
2 years ago
2
Per stop predictions - providers shouldn't drop arrivals until after the bus passes the stop
#17
barbeau
closed
2 years ago
0
Per stop predictions - providers shouldn't drop arrivals until after the bus passes the stop
#16
barbeau
closed
2 years ago
2
VehiclePositions - Check that there is at most one vehicle assigned to each trip
#15
barbeau
closed
2 years ago
4
Check that there is at most one StopTimeUpdate for each stop in a trip
#14
barbeau
closed
2 years ago
1
Check that there is at most one TripUpdate per scheduled trip_id
#13
barbeau
closed
2 years ago
3
New rule - Check Alert EntitySelector field integrity
#12
barbeau
closed
2 years ago
7
Per stop predictions - providers shouldn't drop arrivals until after the bus passes the stop
#11
barbeau
closed
2 years ago
2
VehiclePositions - Check that there is at most one vehicle assigned to each trip
#10
barbeau
closed
2 years ago
4
Check that there is at most one StopTimeUpdate for each stop in a trip
#9
barbeau
closed
2 years ago
1
Check that there is at most one TripUpdate per scheduled trip_id
#8
barbeau
closed
2 years ago
3
New rule - Check Alert EntitySelector field integrity
#7
barbeau
closed
2 years ago
7
Per stop predictions - providers shouldn't drop arrivals until after the bus passes the stop
#6
barbeau
closed
2 years ago
2
VehiclePositions - Check that there is at most one vehicle assigned to each trip
#5
barbeau
closed
2 years ago
4
Check that there is at most one StopTimeUpdate for each stop in a trip
#4
barbeau
closed
2 years ago
1
Check that there is at most one TripUpdate per scheduled trip_id
#3
barbeau
closed
2 years ago
3
New rule - Check Alert EntitySelector field integrity
#2
barbeau
closed
2 years ago
7
Per stop predictions - providers shouldn't drop arrivals until after the bus passes the stop
#1
barbeau
closed
2 years ago
2
Previous