Feb open data #1029
Merged
Feb open data #1029
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tiffanychu90
force-pushed
the
feb-open-data
branch
from
edc2a8b to
9416e29
Compare
added 7 commits
February 21, 2024 00:54
tiffanychu90
force-pushed
the
feb-open-data
branch
from
017dc45 to
090b699
Compare
|
nbviewer URLs for impacted notebooks: |
|
nbviewer URLs for impacted notebooks: |
5 similar comments
|
nbviewer URLs for impacted notebooks: |
|
nbviewer URLs for impacted notebooks: |
|
nbviewer URLs for impacted notebooks: |
|
nbviewer URLs for impacted notebooks: |
|
nbviewer URLs for impacted notebooks: |
|
nbviewer URLs for impacted notebooks: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
open data
segment speeds
stop_geometry.to_crs("EPSG:3310")because we leave some nearest neighbors inputs as "EPSG:4326". Also renamegeometrytovp_geometryfor clarity.select_stop_segments, we create a segments df to use...but then we never call it anywhere. use it innearest_vp_to_stopwhen we construct ourstop_timestable.interpolate_stop_arrivals,stop_arrivals_to_speed, andaverage_speedssteps for all dates.29_speed_cutoffsnotebook and look at distributions ofmeters_elapsed,sec_elapsedand implement 2 cutoffs for trip averages to be rolled up into route-dir averages: (a) 10 minute minimum to match what our usable vps are, (b) 180 min / 3 hr maximum for 1 trip duration. any longer, these might be erroneously calculated. This affects a lot of the very low speeds (<1 mph average)utils_to_add, these are now incalitp_data_analysis.utilsgtfs_segmentsbase nearest neighbors function in pipeline #996segment_speed_utils.time_series_utilsto help concatenategtfs digest
route_id-direction_idand use line charts fortime_periodso we can see all the routes at onceMakefileshould use$(eval export site = route_speeds)shared_utils
rt_datesand includey2024_dates,y2023_dates,oct_week, andapr_week...dates with vp data that we use for speeds. Easier to refer to when we need to run through a bunch of dates.