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

Establish between 1-3 Standardized Naming Schemas for Zone Names #148

Open
rneubauer opened this issue Sep 24, 2024 · 0 comments
Open

Establish between 1-3 Standardized Naming Schemas for Zone Names #148

rneubauer opened this issue Sep 24, 2024 · 0 comments
Labels
Curbs API SMART Collaborative Idea coming from the OMF USDOT SMART grant collaborative.

Comments

@rneubauer
Copy link
Contributor

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

The current Name field is optional in the CDS curbs API and when "CDS" is implemented at scale, it makes it very hard to remember Zone Names when manually created, and using the UUID is next to impossible.

Describe the solution you'd like

We would like to establish a few different naming Schemas that utilize various curb zone variables in CDS to generate the name. This would include the type of Zone (Parking, No Parking, Bus, Commercial, etc.) as well as the compass direction, cross streets, etc. The idea would be that you could look at the name of the zone and understand the type of zone, and where it is located. This would help in when looking at the zones on a map as well as making it much easier to read in reporting and analytics.

We are also factoring in the zone updating, deleting and creation rules in the Curbs rules so that when number of spaces are changed or the policy is changed, the name will reflect those changes according to the update rules.

Is this a breaking change

  • No, not breaking - The "Name" field is Optional, and we are simply providing this as a recommended way for cities to name curbs at scale and still make them understandable and manageable.

For which spec is this feature being requested?

Curbs

Describe alternatives you've considered

We have tried a few simple ways to name the zones but when done at scale it is next to impossible to keep them unique and understand what purpose they serve when done at scale.

@mplsmitch mplsmitch added Curbs API SMART Collaborative Idea coming from the OMF USDOT SMART grant collaborative. labels Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Curbs API SMART Collaborative Idea coming from the OMF USDOT SMART grant collaborative.
Projects
None yet
Development

No branches or pull requests

2 participants