CurbLR is a data standard for describing curb regulations. It uses a simple structure to store complex restrictions and conditions regarding where different users can park, load, or stop their vehicles at different days and times. The CurbLR specification exists to help government agencies effectively manage and regulate the curbside, and to support public and private users of city streets.

CurbLR is a common language on which many things can be built, including rules engines, query APIs, consumer notification services, mapping tools, and analytic models. It uses linear referencing to link regulation information back to the street, making it easy for government agencies and third parties to use this data with their own maps.

Why do we need a data standard for curbs?

  • Government agencies

    Demand for access to the curbside has skyrocketed in urban areas. CurbLR provides a template for cities to create a digital inventory of their curb regulations, which can be used to analyze the present and reimagine the future of this public space.

  • Developers

    The CurbLR specification enables engineers to ingest curbside inventory data from any city in the world, preventing the need to build custom tools or services for different jurisdictions.

  • Transportation services

    It's no secret that the curbside can be chaotic. A standardized curb inventory allows mobility operators, TNCs, delivery services, and parking payment companies to build services that make it seamless for their users to find and use curbspace.


Curb regulations are communicated by physical assets like parking signs, meters, and curb paint. These have a specific set of coordinates and are easy to map. But the concepts they convey are more difficult. For example, a pair of parking signs are more than just two independent points; they represent an invisible rule that applies to a specific section of a particular edge of a specific street. Curb regulations are regulatory geometries, not physical geometries.

To handle this, CurbLR uses point-based asset data as the building blocks for the spec, but supplements that with additional location information and structure. First, CurbLR includes linear references that relate assets to their location along a street, using the SharedStreets Referencing System. In addition, it provides a template to store structured data about the curb rule itself, including what is being restricted or allowed, when a rule applies and for whom, how it is applied, and how it relates to overlapping regulations. This makes it easy to map curb regulations anywhere in the world.

Data model

A CurbLR feed is a JSON file that contains:

  1. A manifest, which includes metadata about when the CurbLR feed was created and updated, the relevant timezone and local authority, and what measurement units are used.
  2. A GeoJSON Feature Collection, which includes each section of curb and the regulations that apply to it. Each GeoJSON feature in the collection must be a LineString that includes the following:
  • The GeoJSON feature geometry
  • Location properties, which include the SharedStreets Reference ID, location start and end, side of street, marker type, and other pertinent location information.
  • Regulations, which contain the structured properties about any regulations that apply to that section of the curbside. A regulation is comprised of a rule (what is permitted or restricted), as well as any applicable restrictions about user classes (including modes, permits, vehicle dimensions, or user types), time spans when the rule is in effect, and payment terms. Each regulation also includes a priority level, which indicates which regulation takes precedence if there are others overlapping it.

The links below provide more information about the data model and show real-world signs that have been translated into CurbLR format.

CurbLR tools

A range of open-source tools help facilitate the creation and use of curb regulation data in the CurbLR specification, including:

Get involved

There are a variety of ways to get involved with CurbLR, such as providing input on the spec, building tools, or testing out methods. We strive to be open and collaborative. The button below will take you to the CurbLR GitHub page, where you can create an issue to let us know about requests, suggestions, or problems. You can also reach out to the SharedStreets team for more specific or private inquiries.