Skip to content
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

Epic - HQTA Methodology Revisions #1230

Closed
2 tasks
edasmalchi opened this issue Sep 25, 2024 · 4 comments
Closed
2 tasks

Epic - HQTA Methodology Revisions #1230

edasmalchi opened this issue Sep 25, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request epic Representing research requests - large segments of work and their dependencies open-data Work related to publishing, ingesting open data

Comments

@edasmalchi
Copy link
Member

edasmalchi commented Sep 25, 2024

Epic Information - HQTA Methodology Revisions

Summary

  • We're having ongoing conversations with HCD and other State agencies and MPOs about HQTA/major transit stop methodology. The goal is to reach a consensus interpretation of the statutes, and align our dataset as closely to that interpretation as possible.
  • Additionally, PRC 21155 and 21064.3 have further diverged with the passing of AB2553, we will likely have to adjust our pipeline to treat each somewhat separately.
  • I (Eric) continue to prefer our segment/stop-based calculation for hq corridors interpreting PRC21155 "a corridor with fixed route bus service with service intervals no longer than 15 minutes".
  • However, PRC21064.3 does specifically include the word "route", so a single-route constraint may be appropriate for intersection-based major transit stops

Will do

  • implement a 20-minute standard for bus intersection major transit stops
  • revise bus intersection major transit stop buffer to 500ft
  • maintain 15-minute standard for hq bus corridors
  • move to fixed AM and PM peak periods (6a-9a, 3p-7p), averaging frequencies within each period

Should probably do

May consider

  • only counting frequencies from a single route+direction to meet major transit stop threshold (more likely)
  • only counting frequencies from a single route+direction to calculate hq corridors (less likely)

Notes, misc:

AB2553(passed):

SEC. 2. Section 21064.3 of the Public Resources Code is amended to read:
21064.3. “Major transit stop” means a site containing any of the following:
(a) An existing rail or bus rapid transit station.
(b) A ferry terminal served by either a bus or rail transit service.
(c) The intersection of two or more major bus routes with a frequency of service interval of 15 20 minutes or less during the morning and afternoon peak commute periods.

Reviewers [Stakeholders]

Issues

  • 1. #
  • 2. #

Deliverables

  • Notebooks, dashboards, narratives, presentation details.
@edasmalchi edasmalchi added the epic Representing research requests - large segments of work and their dependencies label Sep 25, 2024
@edasmalchi edasmalchi added enhancement New feature or request open-data Work related to publishing, ingesting open data labels Sep 25, 2024
@edasmalchi
Copy link
Member Author

edasmalchi commented Sep 25, 2024

intermediate column changes (roughly)

  • am col (now a 3hr average) 6-9am
  • pm col (now a 3hr average) 3-7pm

use additional rows (stop/route combos) to enable a shared intermediate for both definitions

@edasmalchi
Copy link
Member Author

Eric to give this a first pass!

@edasmalchi
Copy link
Member Author

We should also rename the dataset to make clear it includes major stops

@edasmalchi
Copy link
Member Author

PR merged but pending rerun early next week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request epic Representing research requests - large segments of work and their dependencies open-data Work related to publishing, ingesting open data
Projects
None yet
Development

No branches or pull requests

2 participants