Claude
- Download the ZIP package.
- Enable code execution in Settings → Capabilities.
- Open Customize → Skills → + Create skill → Upload a skill.
- Upload, enable, and invoke it with a CAS ID and address.
An independent, public-data-only look at Columbus shared-scooter operations — 311 requests, published vehicle positions, and policy boundaries. Built from public sources only; not affiliated with or using data from any employer.
Allow browser notifications and this open dashboard will check the public 311 and GBFS files for a newer timestamp. No email address or personal information is collected.
Current snapshot signals
Review Ride Hub capacity signals, fleet distribution, municipal geography counts, vendor changes between snapshots, cross-vendor pile-ups, fleet cap compliance, or vehicle mix. Every relevant result can take you back to the map.
Compare empty and over-capacity proximity signals from the current GBFS snapshot.
Active devices inside the published Downtown CBD geography compared with each vendor’s active citywide devices.
Loading the Populus MDS geography export…
Active devices in each published opportunity-zone geography compared with each vendor’s active citywide fleet.
Loading the Populus MDS geography export…
This area is the municipality boundary. It denotes the area that can set policies for, and is provided to operators via the policy API. Percentage based deployment policies use this area to determine total deployment.
Calculating current published vehicle positions…
GBFS snapshot-to-snapshot
A perpetual record of fleet size, range, availability, and geographic concentration. Every committed comparison is retained; no 311 signals are used.
Point-in-time public GBFS observations; changes do not establish deployment intent, demand, service quality, or causation.
Known data limits: Veo’s GBFS feed does not report a battery percentage for any vehicle, so range trend (remaining published miles) is used here as the closest available proxy for charge level — it is not the same measurement. Spin’s vehicle IDs are reassigned on every pull, so movement and range trend can only be tracked for Veo; Spin devices do report a battery percentage but can’t be matched across snapshots to compute a trend.
Total active devices per operator against the City of Columbus / Populus.ai authorized cap.
Scooter vs. bike split of the active fleet, by operator.
Have an idea?
What would you like to know about Columbus micromobility data? Describe it below — submitting opens a pre-filled GitHub issue on this repo for you to post.
This opens github.com in a new tab with your suggestion pre-filled as an issue title and body. Nothing is sent anywhere until you sign in and click “Submit new issue” there yourself.
Open workflow · public portal
A portable, read-only workflow for finding a Columbus 311 case by address and CAS ID, then separating portal facts from vendor and accessibility evidence. Claude accepts the ZIP as a native custom skill; ChatGPT and Gemini use the same Markdown as reusable project or Gem context.
Review AI instruction packages before installing them. This workflow uses a public, read-only portal, requires no login, and should never submit, edit, or comment on a 311 request.
🧪 Urban Transit Mobility Lab
Add your home and a few frequent stops, log recent rides, and get a personalized Spin vs. Veo cost projection with nearby vehicle density from the public GBFS feed.
Separate reference collection
Forecast guides, source inventories, project cards, and comparable analysis charts now live in their own quieter reading space.