UserClasses.md

About user classifications

A regulation often contains a curb rule that is applied differently to different road users. For example, street parking may be allowed but only for vehicles displaying a resident parking permit with a specific zone number. Or, a section of curb may be reserved for pick-up and drop-off by vehicles providing rideshare services ("TNCs").

A UserClass can define a type of vehicle, permit, or service for which a rule may be applied. CurbLR provides a list of well-known values for user classes. However, each jurisdiction will determine how they want to differentiate between types of road users (i.e. what constitutes a rideshare vehicle or what type of handicap permit is required (this varies by country)).

A given vehicle may fall into multiple user classes depending on activity and circumstance (for example, a car may be operated as a rideshare vehicle and display a resident parking permit).

Definition

A GeoJSON feature may include UserClasses made up of the following fields. The UserClass(es) are always expressed as an array in order to provide a consistent format regardless of whether a given regulation has a single or multiple UserClasses. Multiple UserClasses are only necessary when there are multiple classes and at least one subclass that does not apply to all of the classes.

Field name	Importance	Type	Description	Example
classes	Optional	array of string Suggested values; see below	The identifier of a user class, which may define a type of vehicle, permit, purpose, or service. This field is an array in order to accommodate single or multiple values in a consistent way.	[food truck]
subclasses	Optional	array of string	Optional secondary identifiers for a class of user. Useful for subdividing permit holders by zone or other designation	[zone 4, zone 5]
maxHeight	Optional	float	If the classes or subclasses indicates that there is a vehicle height, length, or weight restriction, use an additional key:value pair to indicate the number, in local units. (Local units may be specified in the manifest.)	maxHeight:6
minHeight	Optional	float	If the classes or subclasses indicates that there is a vehicle height, length, or weight restriction, use an additional key:value pair to indicate the number, in local units. (Local units may be specified in the manifest.)	minHeight:3
maxLength	Optional	float	If the classes or subclasses indicates that there is a vehicle height, length, or weight restriction, use an additional key:value pair to indicate the number, in local units. (Local units may be specified in the manifest.)	maxLength:20
minLength	Optional	float	If the classes or subclasses indicates that there is a vehicle height, length, or weight restriction, use an additional key:value pair to indicate the number, in local units. (Local units may be specified in the manifest.)	minLength:10
maxWeight	Optional	float	If the classes or subclasses indicates that there is a vehicle height, length, or weight restriction, use an additional key:value pair to indicate the number, in local units. (Local units may be specified in the manifest.)	maxWeight:5
minWeight	Optional	float	If the classes or subclasses indicates that there is a vehicle height, length, or weight restriction, use an additional key:value pair to indicate the number, in local units. (Local units may be specified in the manifest.)	minWeight:2

Data fields should generally be considered case insensitive since they are used programmatically; we use lower-case in our examples, except for fields that would be used for display purposes (such as a street name or agency name). e

If a regulation does not specify userClasses properties, it will be assumed to apply to all curb users.

It is possible for a given curb segment to have multiple regulations that apply, during the same time period, to different user classes. However, only one of those regulations may have an empty userClasses field; otherwise they will conflict with one another. When evaluating which regulation applies to a specific user class, the regulation without userClasses will be considered the default if no other regulations apply to the user.

Classes: well-known values

The following is a suggested but not exhaustive list of values for classes. It is up to a particular jurisdiction to define exactly which vehicles, user, purposes, or permits are required for each value. Multiple values may be specified in an array. If multiple well-known values apply, the most descriptive should be used (e.g. for food truck parking, food truck should be used rather than truck)

• bicycle
• bikeshare
• bus
• car share
• carpool
• commercial
• compact
• construction
• diplomat
• electric
• emergency
• food truck
• handicap
• micromobility
• motorcycle
• official
• passenger
• permit
• police
• rideshare
• staff
• student
• taxi
• truck
• visitor

Numeric restrictions (height, length, width)

Numeric restrictions, Optional, are entered as key:value pairs in the local measurement unit (e.g. feet and pounds in USA, metres and kilograms in UK). Measurement units may be specified in the manifest. Available keys include:

• maxHeight
• maxLength
• maxWeight
• minHeight
• minLength
• minWeight

Examples

Link	Description
Examples of simple regulations	Simple regulatory scenarios typically involving one or two basic restrictions
Examples of complex regulations	Complex regulatory scenarios typically involving several restrictions
Sample of downtown Portland's parking regulations	Contains data for about 3 miles of parking regulations, surveyed in November 2019. This can also be viewed at demo.curblr.org

Food truck

Defines a parking zone for vehicles operating as food trucks

{
  "regulation": {
    "rule": {
      "activity": "parking",
      "priorityCategory": "parking"
    },
    "userClasses": [
        {
        "classes": ["food truck"]
      }
    ]
  }  
}

Zoned resident-only parking

Defines a parking zone for vehicles displaying a Zone 4 or Zone 5 Resident Permit.

{
  "regulation": {
    "rule": {
      "activity": "parking",
      "priorityCategory": "parking"
    },
    "userClasses": [
      {
        "classes": ["permit"],
        "subclasses": ["zone 4", "zone 5"]
      }
    ]
  }  
}

Truck length limit

Defines a parking regulation for large trucks that does not apply to smaller trucks (or any other class).

{
  "regulation": {
    "rule": {
      "activity": "no parking",
      "priorityCategory": "no parking"
    },
    "userClasses": [
      {
        "classes": ["truck"],
        "maxLength": 25
      }
    ]
  }  
}

Vehicle height limit

Defines a parking space for vehicles no more than 6 feet tall.

{
  "regulation": {
    "rule": {
      "activity": "parking",
      "priorityCategory": "parking"
    },
    "userClasses": [
      {
        "maxHeight": 6
      }
    ]
  }  
}

Car share

Defines car share spaces with subclasses for specific operations. This would allow for certain spaces to be reserved for specific operators while also allowing the creation of floating car share spaces to be used by any operator.

Denotes the userClass for Zipcar spaces:

{
  "classes": ["car share"],
  "subclasses": ["Zipcar"]
}

Denotes the userClass for Car2Go spaces:

{
  "classes": ["car share"],
  "subclasses": ["Car2Go"]
}

Denotes the userClass for floating spaces:

{
  "classes": ["car share"]
}