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
Is your feature request related to a problem? Please describe.
It is beneficial to have all cities provide curb zone (and curb object) locations with a standard LRS to streamline data consumption. It will be great if OMF can provide guidance and/or a convertor to turn spatial data into LRS.
Describe the solution you'd like
Currently SMFTA's digital curb project partner provided LRS data from OpenLR. But
Is this a breaking change
A breaking change would require consumers or implementors of an API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).
No, not breaking
Impacted Spec
For which spec is this feature being requested?
Curbs
Events (maybe)
Metrics (maybe)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It is beneficial to have all cities provide curb zone (and curb object) locations with a standard LRS to streamline data consumption. It will be great if OMF can provide guidance and/or a convertor to turn spatial data into LRS.
Describe the solution you'd like
Currently SMFTA's digital curb project partner provided LRS data from OpenLR. But
Is this a breaking change
A breaking change would require consumers or implementors of an API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).
Impacted Spec
For which spec is this feature being requested?
Curbs
Events
(maybe)Metrics
(maybe)Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: