Arlington Performance Parking Project Real-Time Stall Status API

The Performance Parking Project has made the parking sensor real-time data available to developers to develop their own applications.

Access and Structure

The real-time data for all sensors is provided via a single API and returns a simple structure that provides a stall identifier, location and status for each sensor. The data is retrieved via an HTTP request:

GET https://api.exactpark.com/api/v2/arlington/status/zones

The Response returns a JSON structure.

{
    "version": "1.0",
    "timezone": "US/Eastern",
    "data": [
        {
            "stallID": 1,
            "stallName": "Lot1-1",
            "blockfaceID": "Lot1",
            "status": "occupied",
            "location": {
                "lat": 30.123456789012,
                "long": -70.123456789012
            },
            "payloadTimestamp": "2024-01-24 08:39:07"
        },
        {
            "stallID": 2,
            "stallName": "Lot1-2",
            "blockfaceID": "Lot1",
            "status": "vacant",
            "location": {
                "lat": 31.123456789012,
                "long": -71.123456789012
            },
            "payloadTimestamp": "2024-01-24 06:17:58"
        },
        {
            "stallID": 3,
            "stallName": "Lot3-1",
            "blockfaceID": "Lot3",
            "status": "vacant",
            "location": {
                "lat": 32.123456789012,
                "long": -72.123456789012
            },
            "payloadTimestamp": "2024-01-24 08:16:55"
        }
    ]
}

The response will contain the status of all stalls with a parking sensor in the parking project. There are over 4500 stalls in the parking project area. The number of sensors will vary due to other projects such as paving or construction which may remove or add sensors. At the time of release there were over 4200 sensors installed and returning data.

JSON field definitions

version API version number
timezone The time zone of Arlington County
stallID Unique numerical identifier
stallName Name of stall consists of the BlockFaceID and an assigned number
blockFaceID

A Block Face is the curb segment on one side of a street between two intersections. The BlockFaceID is unique in the project area. The BlockFaceID has a structure that describes the BlockFace:

The first letter is the area of the County, North or South. Next, first two letters of the street followed by the first two letters of an intersecting street and then the first letters of the other intersecting street. The last letter is the side of the street. North, South, East or West.

The exception is the parking lots which are BOZL, EADSL and VHP.

status Status of the stall, vacant or occupied by a vehicle
location Latitude and longitude of the stall
payloadTimestamp The date and time in the local timezone when the status packet was sent.

Connecting the data to the parking infrastructure

The developer may want to tie the stall status back into the County parking inventory. The parking meter data is available via the County GIS Open Data (https://gisdata-arlgis.opendata.arcgis.com). This data is free to download. The parking meter data contains meter identifiers, block number, full street, Metro Area as well as parking information such as time limits, pricing and other regulation information. The real-time data can be linked back to the meter data through the BlockFaceID. Each meter in the project area has a BlockFaceID in the meter data.