consider adding route/id to the information on stop/successors
carocad opened this issue · comments
right now we just create a link between two stops, however this means that each time we lookup a src-dst connection we have to loop over all trips and stop-times to see if there is any connection.
We could filter out some trips by storing the route/id inside the stop/successor such that only the trips of those routes are taken into account
NOTE: for this we would need to have "edge" entities (see #258 )