Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

  • Information Frontier Agent
  • Vendor Management Agent
  • Product Tour
  • Pricing

Solutions

  • All Solutions
  • Atlas
  • Wayfinder
  • Horizon

Suppliers

  • Sell Your Data
  • Start Onboarding
  • Programmatic Data License

Community

  • Public Index
  • Signals
  • Blog

Company

  • About
  • Team
  • Careers
  • Brand

Connect

  • LinkedIn
  • X
PrivacyTermsCookies

© 2026 Brickroad

/Index/Curbiq/Curbiq
C

Curbiq

CURBIQManage supplier listing

A centralized, continuously maintained curb database built by integrating parking-operator feeds, traffic-camera data and municipal records into one inventory: per-zone curb rules (time-of-day restrictions, loading zones, parking, pickup/drop-off designations), real-time occupancy and adaptive-pricing signals from the HOTSPOT parking-app integration, curb rules exposed through a rules API and a regulation converter, survey-grade curb-level digitization in CDS format, and custom policy-impact analyses for cities, airports and universities

Open buyer room →
Curbiq/Curbiq
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Curbiq and files the sample in your catalog — private to you.

Start 7-day trial→Nothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry
Application SoftwareTransportation Services
Instruments
equities
Categories
Geospatial
Reference
Alternative
Supply Chain
Regions
USOther
Sample tickers
ARIS.ASSPGCUBEUBERLYFTGOOGLAMZNFDXUPSTKCYY
Dataset card
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

supplier index read from their site

Curbiq has not added their own details yet. Not yet on file:

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling