Add a jurisdiction element to Curb Zones in the Curbs API

[sfmta0kw]

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

Streets open to public access but maintained by private entities may not have curb assets updated with the same cadence as publicly maintained streets. Additionally, curb regulations on private roadways may have different regulations and restrictions from those on publicly maintained streets. Currently, there is no element in the Curbs API to identify whether the curb on a publicly accessible street is in public or private ownership.

Describe the solution you'd like

We propose adding an element to identify the entity responsible for operating (e.g. roadway owner) and managing a Curb Zone.

Name, Type, Required/Optional, Description
curb_zone_jurisdiction String, Optional, Ownership of the Curb Zone (street).
The string for this new optional element is proposed to have a value of either "public" for a street and curb zone maintained by a public sector agency (City, County, etc.) or "private" for a street and curb zone maintained by a private entity (e.g. Developer, Home Owners Association, University Campus, etc.).

Adding an optional table of values for public and private owner would help data users determine who is responsible for curb policies and updates. This could be expressed by a value set such as "public, name of jurisdiction"

• Public, CCSF or City and County of San Francisco
• Public, Presidio Trust (Federal agency that governs Presidio National Park in the City and County of San Francisco. As a Federal agency the Presido Trust has sole regulatory authority over public roads in Presido Trust jurisdiction)

Is this a breaking change

• No, not breaking

Impacted Spec

For which spec is this feature being requested?

• Curbs API

Describe alternatives you've considered

There is no existing element that could accommodate this information. Potentially the entity owning and managing a Curb Zone could be listed as in a new description field that could be added that related to "Zone Name" element as described under Issues #148 and #163.

Additional context

For the example of two adjacent public agencies - CCSF and Presidio Trust, see this maps from the San Francisco Public Works street mapping system that illustrates how public roadways cross different public jurisdictional boundaries within one city:

[schnuerle]

I think adding two new fields, curb_zone_jurisdiction (public, private, etc) and curb_zone_owner (SFMTA, CCSF, Presidio Trust, etc), should cover your needs here (vs making a table of values to reference) for each Curb Zone. Does that sound right to you?

[schnuerle]

What do you think about my 2 field proposal? Will that be enough? Or we can go down the route of what MDS does, which is a whole Jurisdiction API that connects to other parts of the spec.

[schnuerle]

I think adding two new fields, curb_zone_jurisdiction (public, private, etc) and curb_zone_owner (SFMTA, CCSF, Presidio Trust, etc), should cover your needs here (vs making a table of values to reference) for each Curb Zone. Does that sound right to you?

@sfmta0kw Do you think these 2 fields would be enough? If so we could get them into 1.1, but let me know by the end of the week.

[schnuerle]

Added jurisdiction_type and owner_name fields to Curbs object with #194.