Research Request - Use gtfs_segments
base nearest neighbors function in pipeline
#996
Labels
gtfs-rt
Work related to GTFS-Realtime
research request
Issues that serve as a request for research (summary and handoff)
Complete the below when receiving a research request, and continue to add to this issue as you receive additional details and produce deliverables. Be sure to also add the appropriate project-level label to this issue (eg gtfs-rt, DLA).
Research Question
Single sentence description:
gtfs-segments
in our pipeline? #988Detailed description:
gtfs_segments
package, we will use theircreate_segments
to get our stop segments. When we apply thatcreate_segments
function, it takes quite a bit longer ingeopandas
, but if we wrap it withdask.map_partitions
, it will be much faster to use.create_segments
relies on anearest_points
base function that usesscipy.spatial CKDTree
that we can use more broadly.shape_array_key
, then not every stop is reflected for that trip, only 1 variation. --> Where are the nearest vp to these more-easily-aggregated-segment cutoffs?rt_stop_times
table: We would want to reflect each trip-stop's location and the speed it took to get there. This might be a contributing factor / conceptual bug in why not all stops are monotonically increasing. --> Where are the nearest vp to these every stop for that trip, get stop arrival, and derive speed.Deliverables
gtfs_segments.nearest_points
in all portions of the analytics pipelineThe text was updated successfully, but these errors were encountered: