Skip to content

openmobilityfoundation/curb-data-specification

View on GitHub ↗Related repositories →

A data specification to help cities manage their curb zone programs and surrounding areas, and measure the utilization and impact.

active 2023-08-152026-05-14 (UTC)

Complete coverage26,770 / 26,770 hourly files (100%) · 2 absent upstream2023-08-152026-09-03 (UTC)
Events
1K
Pushes
134
Pull requests
54
Issues
75
Stars
23
Forks
7

Activity over time

Daily event counts in the loaded window

Line chart, 1004 days from 2023-08-15 to 2026-05-14. Pushes: 134 total, peak 9 in a day. Pull requests: 54 total, peak 3 in a day. Issues: 75 total, peak 7 in a day. Comments: 354 total, peak 20 in a day. Stars: 23 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#198schnuerle2025-09-12 17:10
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy_rule property
  • Issue#198schnuerle2025-09-12 17:10
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy_rule property
  • Issue comment#198schnuerle2025-09-11 02:09
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy_rule property
  • Issue comment#198stefyperezg2025-09-10 20:49
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy_rule property
  • Issue comment#198jacobmalleau2025-09-10 14:45
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy_rule property
  • Issue comment#198schnuerle2025-09-09 15:30
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy_rule property
  • Issue#183schnuerle2025-09-09 15:24
    Make Event Location Optional
  • Issue comment#197schnuerle2025-09-04 02:58
    Draft of CDS 1.1 Release
  • Issue comment#149schnuerle2025-09-04 02:40
    Provide double parking event locations
  • Issue comment#173schnuerle2025-09-04 02:40
    New Event Types to Handle Additional Curb Demand Sources - citations
  • Issue#173schnuerle2025-09-04 02:40
    New Event Types to Handle Additional Curb Demand Sources - citations
  • Issue comment#174schnuerle2025-09-04 02:40
    New Metric Type to Handle Additional Demand Sources
  • Issue#174schnuerle2025-09-04 02:40
    New Metric Type to Handle Additional Demand Sources
  • Pull request#199schnuerle2025-09-04 02:38
  • Issue comment#179schnuerle2025-08-22 20:09
    Adding Enforcement Attributes to Demand Data
  • Issue#146schnuerle2025-08-22 20:07
    Add Additional Field to Events API for Computer-Vision based systems
  • Issue comment#146schnuerle2025-08-22 20:07
    Add Additional Field to Events API for Computer-Vision based systems
  • Pull request#196schnuerle2025-08-22 20:07
  • Issue comment#168schnuerle2025-08-22 20:04
    Add Zone Color to Zones in the Curbs API
  • Issue#168schnuerle2025-08-22 20:04
    Add Zone Color to Zones in the Curbs API
  • Issue#157schnuerle2025-08-22 20:03
    Add a payment method field to CDS Events
  • Pull request#158schnuerle2025-08-22 20:03
  • Issue#198stefyperezg2025-08-21 21:37
    Unclear logic of User Classes of type Purpose - consider moving purpose as a separate policy property
  • Issue comment#179kenyaw2025-08-20 22:09
    Adding Enforcement Attributes to Demand Data
  • Issue comment#158jiffyclub2025-08-20 20:02
    Add Payment Channel and Method to Curb Events

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 23 stars here means stars gained during the window, not the repo's star count.