Research Request - Fix Certain Speeds #804
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: After flagging rows with zero in the
meters_elapsed
andsec_elapsed
and inspecting a few routes for some typical errors.Detailed description:
speeds_stop_segments_{analysis_date}
parquet (which is produced inB1_speeds_by_segment_trip
).stop_segments_{analysis_date}
, get the segment's length.meters_elapsed
columnmeters_elapsed/segment_length
pct
look ok? how many rows are we dropping if we setpct
>= 30%, 40%, 50%? we want to keep enough to get more stable values for speeds, not calculated over super portions of segments, and not throw away too many just to get a narrow distribution.How will this research be used?
Stakeholders & End-Users
Metrics
1: Vehicle positions that are too far from the segment shapes are not being joined (using
sjoin
) to the segment shapes. What percentage of the vehicle positions are we missing for each route, due to this?2: Some segments are short and only one vehicle position is captured for it. Therefore, there isn't a way to calculate the distance and time. Find a way to use time stamp in the next segment as a replacement to get a calculation.
3: Find length of segments and see how many rows are retained based on the threshold, aka how strict it is.
7/26/23 update: wait on above approach. tackle Newmark's spatial accuracy metric in Research Request - Spatial accuracy metric #820 .
Data sources
rt_segment_speeds
vp
vp_stop_segment
speeds_stop_segment
Deliverables:
Notebook and scripts.
Timeline of deliverables:
Estimated completion date
The text was updated successfully, but these errors were encountered: