dystonse dystonse-gtfs-data issues

dystonse / dystonse-gtfs-data

Read gtfs and gtfs-realtime data, write them into a database, perform and export analyses and make predictions based on them.

9 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Display info about the data sources with age and link(s)

#27 flauschzelle opened 3 years ago
0
Configurable long name for data source

#26 flauschzelle closed 3 years ago
0
Limit the amount of records to use in the analyses

#25 flauschzelle opened 3 years ago
0
Reload schedule when a new file appears

#24 lenaschimmel closed 3 years ago
1
Empty stop_pages due to mismatched trip_ids for every single prediction.

#23 lenaschimmel opened 4 years ago
0
Handling of multiple stops with similar names and/or locations is inconsistent

#22 lenaschimmel opened 4 years ago
3
Show walk arrival time on the stop page if a walk is needed to reach the vehicle

#21 lenaschimmel opened 4 years ago
0
Idea: Replace breadcrumb navigation by multiple lines for previous route components

#20 lenaschimmel opened 4 years ago
0
Group together multiple stop events for the same vehicle

#19 lenaschimmel opened 4 years ago
0
Duplicate departure entries

#18 lenaschimmel opened 4 years ago
2
Output predictions as enhanced GTFS realtime

#17 lenaschimmel opened 4 years ago
0
Integrate several, possibly overlapping, data sources into one monitor

#16 flauschzelle opened 4 years ago
0
Make the (info about the) data source configurable

#15 flauschzelle closed 3 years ago
1
Include a simple set of low-precision analyses to use until enough data is collected for better analysis quality.

#14 flauschzelle opened 4 years ago
2
Don't display trips from nearby stops that only go back to the current stop and end there.

#13 flauschzelle opened 4 years ago
0
Visually separate the top row (arrival) more clearly from the departure rows

#12 flauschzelle opened 4 years ago
1
Make tooltips touch-friendly

#11 flauschzelle opened 4 years ago
1
Overwrite schedule-based predictions daily, based on newest schedule

#10 flauschzelle closed 4 years ago
2
Show better error pages

#9 lenaschimmel opened 4 years ago
0
Add geolocation support to start journeys at any place

#8 lenaschimmel opened 4 years ago
0
Different percentage for the same boarding, even with the same times

#7 lenaschimmel opened 4 years ago
2
Different precision of the same prediction when viewed as stop page / trip page

#6 lenaschimmel opened 4 years ago
2
Handle canceled trips

#5 lenaschimmel opened 4 years ago
0
Add `start_time` to uniquely identify journeys.

#4 lenaschimmel closed 4 years ago
1
Log import errors into a table instead of log file

#3 lenaschimmel opened 4 years ago
0
Better error handling for db (connection) errors.

#2 lenaschimmel opened 4 years ago
0
Make dystonse-gtfs-importer a universal tool

#1 lenaschimmel closed 4 years ago
1