Bug: HQTA unintentional multi-route frequency segments #1838
Description
Where did the bug occur?
Select from the below, and be sure to affix the appropriate label to this issue (e.g. dataset, jupyterhub, metabase, analysis.calitp.org)
- Data (the warehouse)
- JupyterHub
- Metabase
- analysis.calitp.org
- Other (add detail)
Describe the bug
We currently screen at the route/stop level whether or not to aggregate frequencies at a particular stop. However, it's possible that after that step segments from routes not part of the collinearity screen use those combined frequencies to determine if a segment is an HQTC or major stop precursor.
Look into tightening this up to only assign multi-route frequencies to routes screened in in the previous step, see if this creates other unexpected behavior.
To Reproduce
See Foothill Transit near Cal Poly Pomona
