Parking access


Represents an access point to a parking site, normally an offstreet parking.

Data Model

  • id : Unique identifier.

  • type : Entity type. It must be equal to ParkingAccess.

  • location : Geolocation of the access point represented by a GeoJSON Point.

  • address : Registered civic address of the access point.

  • name : Name given to the access point.

  • description : Description of the access point.

  • category : Category of the access point (entrance, exit, etc.)

    • Attribute type: List of
    • Allowed values: Those specificed by the DATEX II AccessCategoryEnum.
      • Other values meaningful to the application.
    • Mandatory
  • refOffStreetParking : The offstreet parking site this access point gives access to.

  • features : Equipment or facilities provided by the access point.

    • Attribute type: List of
    • Allowed values: Those specified by the DATEX II AccessEquipmentEnum and by AccessibilityEnum.
      • Other values meaningful to the application.
    • Optional
  • image : A URL containing a photo of this access point.

  • width : Width of the access point.

  • height : Height of the access point.

  • slope : Slope of the access point (in relative terms).

    • Attribute Type: Number
    • Attribute Value: A number between 0 and 1.
    • Optional

Note: JSON Schemas only capture the NGSI simplified representation, this means that to test the JSON schema examples with a FIWARE NGSI version 2 API implementation, you need to use the keyValues mode (options=keyValues).

Examples of use

  "id": "accesspoint-trinidade-1",
  "type": "ParkingAccess",
  "name": "Trinidade main entrance",
  "location": {
    "coordinates": [-8.60961198807, 41.150691773],
    "type": "Point"
  "category": ["vehicleEntrance"],
  "refOffStreetParking": "porto-OffStreetParking-23889",
  "features": ["barrier"]

## Test it with a real service

## Open issues