-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proportion of trips on different route_types #107
Comments
I don't know if you still plan to implement this, but I am interested ! For now i use gtfs_traveltimes and the start and stop ids to extract the first and last leg modes of each trip. But I can't extract the exact time / distance breakdown by mode, and I am obviously missing modes (for trips with more than one transfer). |
@FlxPo Yes, definitely still planned. Unsure when, but if all goes well maybe soon. Let me know if it's a hold-up for you not having it, and i'll try to get it together sooner. Appreciate the interest 👍 |
It's not a hold-up but definitely something that we need, to compute accurate GHG emissions per trip in our Mobility project (https://github.com/mobility-team/mobility). |
Cool project! As an aside, let me know which French cities you'd like added to https://urbananalyst.city, and I'll happily do it. Plan for this issue is to incorporate measures of modal proportion in that platform too. |
The "routes" tables have a "route_type" column which specifies:
These values could be mapped on to the timetable used in all C++ routines, and the proportions of all trips in these categories calculated for each route (in time, not distance). Current routines return matrices with 3 columns: start times, durations, ntransfers. This would require one additional collumn for each route type, so would have to be restricted to something like the first four, and even that would more than double the size of the returned matrix. This could obviously only be implemented as an optional extra ability, and not in any default mode. Note also that these are strictly integer matrices, so values would have to be total times along each mode, which could later be converted to proportions by dividing by the first column of total duration.
Created on 2023-06-15 with reprex v2.0.2
Then just add extra code in the routing algorithms to aggregate those
route_type
values along each route, weighted by (arrival_time - departure_time).The text was updated successfully, but these errors were encountered: