- Type
- not stated
- Format
- Multimodal-structured — geospatial curb inventory with regulation attributes, CDS-standard data feeds, API endpoints for curb rules, streaming occupancy and price events from parking-operator/app integrations, and camera-derived occupancy inputs
- Volume
- Large where deployed: a city such as Toronto implies on the order of 100K-1M discrete curb segments, each carrying full regulation attributes, plus continuous occupancy and pricing events from the parking-operator and parking-app integrations and camera-derived occupancy passes — so 10^5-10^6 inventory records per major city plus ongoing event streams
- Users
- Institutional, not consumer — 7 customer logos on the cities page including Toronto, with Dublin and Arlington County named in published case studies, plus airports and universities as stated customer classes; est. low double-digit deployed organizations, with seats for city planners and parking staff
- History
- 4 years
- Update frequency
- not stated
- Growth
- Active — live municipal case studies (Dublin kerbside logistics, Arlington County performance-parking pilot), a customer logo strip that grew over time (a 2024-added asset alongside 2023-era logos), a marketed API/integrations surface, and a recent logo refresh — current commercial build-out rather than a legacy product
- Launched
- ~2021-2023 — the Toronto venture appears in corporate records from ~early 2021, and the earliest customer and marketing assets on the public site date to mid-2023, which brackets the product's public launch
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated