A Location for Custom Attributes in Curb Zones. #177
Description
Is your feature request related to a problem? Please describe.
Several cities we are working with are open to using CDS, or are actively adopting it, however they have several legacy attributes that they want to carry over that don't perfectly 'fit' into the spec. This could include extra IDs, specific measurements of the curb, or other miscellaneous information. This is also causing some vendors to not be able to ingest this CDS data as these extra fields are 'breaking' the API.
Describe the solution you'd like
Having a location to 'dump' these extra attributes that could be unique to each city data feed without disrupting or breaking the spec, could be very beneficial. This could exist as a "custom attributes" field that could then have a collection of key-value pairs with the unique attributes and associated values.
Is this a breaking change
- No, not breaking - in theory this is just an extra attribute that can be ignored, so no not breaking.
Impacted Spec
For which spec is this feature being requested?
Curbs
Describe alternatives you've considered
Trying to fit these attributes into CDS fields can work to an extent, but cities often want to easily look up these values.
Additional context
We have explored implementing this field in CurbIQ's CDS API feed alongside the City of Seattle and it has proved effective.