Parking access

Description

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

Data Model

The data model is defined as shown below:

  • id : Unique identifier.

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

  • source : A sequence of characters giving the source of the entity data.

    • Attribute type: Text or URL
    • Optional
  • dataProvider : Specifies the URL to information about the provider of this information

    • Attribute type: URL
    • Optional
  • location : Geolocation of the access point represented by a GeoJSON Point.

    • Attribute type: Text or URL
    • Optional
  • dataProvider : Specifies the URL to information about the provider of this information

    • Attribute type: URL
    • Optional
  • 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 https://schema.org/Text
    • 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 https://schema.org/Text
    • Allowed values: Those specified by the DATEX II essEquipmentEnum 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

Normalized Example

Normalized NGSI response

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

key-value pairs Example

Sample uses simplified representation for data consumers ?options=keyValues

{
    "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