This topic documents the
parkingSegment response data type supported by the On-Street Parking API resources.
parkingSegment defines the following attributes:
|id||Always included |
The unique identifier of the parking segment. The scope of a specific identifier is only within the current response (i.e. the id is not stable across responses).
|maxHeight||Not always included |
The max vehicle height (cm) that can park at the on-street parking segment.
|capacity||Not always included |
The maximum number of vehicles that can be parked on this parking segment.
|paymentInfo||Not always included |
Information on the method for paying parking fees.
|priceSchema||Not always included |
Information on the costs, maximum stay and applicable period for parking fees.
|segmentAnchor||Not always included |
Information on the HERE Map topology segments that the parking segment relates to.
Only included when the geometryType selector is set to "segmentAnchor".
|address||Not always included |
Information on the address of the parking segment, with Country Code adhering to ISO-3166-1.
|features||Not always included |
List of Features (String)
An on-street parking segment can have one or more of the following features:
|parkingRestrictions||Not always included |
List of parkingRestrictions
Information on the restrictions for parking on particular segments.
|contactInfo||Not always included |
Categorized contact details (e.g. phone, email).
|info||Not always included |
List of Strings
Additional information for this parking segment.
|tpegOpenLR||Not always included |
A segment location reference, based on the ISO/TS 21219-22:2017 (TPEG2-OLR) specification.
Only included when the geometryType selector is set to "tpegOpenLR" or empty.
|availability||Not always included |
Real time availability information, such as free spaces, trend and last updated timestamp.
|probability||Not always included |
Probability to find at least one parking spot on given segment.