Feature Request: Add additional data to CA Transit Stops open dataset

[evansiroky]

Where does your feature apply?
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 - Open Data

Is your feature request related to a problem? Please describe.

In order to provide helpful data for Caltrans Staff and members of the public, it would be great to add additional data about stops that is being calculated or will be calculated within the pipeline. Specifically two items would be helpful. The first is whether a stop is near the state highway network which was added in cal-itp/data-infra#3397. Also, at some point, the Caltrans District may also be added in cal-itp/data-infra#3577.

Describe the solution you'd like

The CA Transit Stops dataset should have data added about whether a stop is near the SHS and what Caltrans District the stop is within.

Describe alternatives you've considered

Manually calculating this data and manually delivering the data to district staff.

Additional context

none at this time.

[tiffanychu90]

@evansiroky: I left a note in #1182 (the earliest version of when would have been done), and I think the question stands. State highways are CA-centric...so how do we want to address the fact that there will be stops outside of CA that are not on it (False is fine, but ultimately isn't a numeric column like meters_to_shn more useful than boolean)?

My original consideration was that if we flagged it as being on the SHN, users would necessarily ask, what does "on" mean, how close is it, and what if I want a stop that is 100 meters away rather than 50 meters, and now I don't have a way to discern? But I haven't been able to reconcile how to deal with outside CA stops from highways that are CA-centric with numeric vs not giving users flexibility in filtering