You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, analytics.calitp.org)
Data (the warehouse)
JupyterHub
Metabase
analytics.calitp.org
Other (add detail)
Is your feature request related to a problem? Please describe.
On the camobilitymarketplace, we have a list of CA transit agencies that was assembled by hand back in 2019. Since then, much has changed and much of the data is stale / out of date. I've been working with various teams to scope a wishlist of the data we'd like to provide on the site and would like to review the list and determine a path forward.
Describe the solution you'd like
A review of the desired fields and some indication of:
what options we have for the specific field?
how often those options are refreshed?
the source of the data
any other editorial on the use of that data (eg, "5311 info is input by hand each August" for example) that could help us prioritize and plan operationalizing a view that meets our needs
Describe alternatives you've considered
An alternative is to create a one time export (which would still require review of the fields and development of a view) and host that static export on the site. This would be an improvement over the current export but requires regular updates and operational support.
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
,analytics.calitp.org
)Is your feature request related to a problem? Please describe.
On the camobilitymarketplace, we have a list of CA transit agencies that was assembled by hand back in 2019. Since then, much has changed and much of the data is stale / out of date. I've been working with various teams to scope a wishlist of the data we'd like to provide on the site and would like to review the list and determine a path forward.
Describe the solution you'd like
A review of the desired fields and some indication of:
Describe alternatives you've considered
An alternative is to create a one time export (which would still require review of the fields and development of a view) and host that static export on the site. This would be an improvement over the current export but requires regular updates and operational support.
Additional context
The wishlist is here: https://docs.google.com/spreadsheets/d/1RhCncjLSrcKVotwxsJdl24WpAdom8baIthM7y05BWjA/edit#gid=1086363224
The text was updated successfully, but these errors were encountered: