Columbus Micromobility — Observer View

Independent observer · public data only

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.

Buy me lunch Buy Me a Coffee Ko-fi Venmo Cash App
Snapshot, not live operations. Counts and timestamps describe public point-in-time data. Proximity, reports, and observations are review signals—not confirmed violations or vendor intent. Open “How to use this site” for methods and evidence boundaries.

Reader guide

How to use this site

Start with snapshot age, then use the map layers to ask a specific question. Every view is read-only and evidence-limited: proximity, distribution status, and reported conditions are review signals—not proof of a violation, enforcement action, or vendor intent.

1 · Check data age

The four summary cards show record counts, the last refresh timestamp, and relative age for the 311, GBFS, pile-up, and policy snapshots. Interpret every finding in the context of its collection time.

2 · Toggle map layers

On phones, select Layers & filters over the map to open the control sheet. On larger screens, the controls remain beside the map. Layers include 311 requests, GBFS vehicles, Ride Hubs, vendor review areas, pile-ups, policy boundaries, and published MDS geographies.

3 · Read map symbols

311 requests use priority-colored diamonds; GBFS vehicles use vendor-colored circles; Ride Hubs use signed markers with nearby-vehicle badges. Dashed circles mark vendor review areas, outlined rings mark pile-ups, dashed lines mark policy boundaries, and shaded polygons mark MDS geographies.

4 · Filter vehicles

Use Operator and Availability to narrow the GBFS positions shown on the map. Ride Hub counts and distribution tables continue to use the complete active snapshot, independent of those display filters.

5 · Review insights

Use the Ride Hubs, CBD distribution, Opportunity zones, Ohio State, Vendor changes, and Pile-ups tabs. Select a linked hub, geography, review area, or pile-up to enable its layer and return to the relevant map area.

6 · Read distribution status

CBD status uses a 30% maximum: red is above 30%, yellow is 27–30%, and green is below 27%. Opportunity-zone status uses the supplied 5% minimum: red is below 4.5%, yellow is 4.5% to under 5%, and green is 5% or more. These point-in-time indicators remain provisional; read the note below each table for timing and source limitations.

7 · Inspect Ride Hubs

Open the Ride Hub Status dashboard to compare empty and capacity-exceeding proximity signals. Select any row to enable the hub layer and jump to its map marker.

8 · Follow vendor changes

The perpetual observation history preserves every committed GBFS comparison for fleet size, published range, availability, and geographic concentration without using 311 reports. Each entry shows ↑ Up, ↓ Down, or — Unchanged; geographic entries also jump to their review area on the map.

9 · Research a 311 case

Select a 311 diamond for its CAS ID, address, status, source link, and a button that copies a complete case-lookup prompt for your AI tool.

10 · Install the lookup workflow

Below the Insights section, download the native Claude skill ZIP or portable Markdown instructions for a ChatGPT Project or Gemini Gem.

11 · Focus and share a view

Use a focus preset to select a purposeful layer combination. Copy view link preserves the active layers, vehicle filters, map center, and zoom so another reader can reopen the same workspace.

12 · Use research artifacts

Open the separate Research Library for downloadable forecast guides, inventories, project cards, and analysis charts with visible source provenance.

This is an independent public-data observer view—not a live dispatch system, official City record system, or confirmed-violation ledger. The site uses Google Analytics 4 and PostHog to measure aggregate usage and interaction patterns. PostHog person profiles and session replay are disabled, and its integration respects browser Do Not Track settings.

Columbus Ride Hubs · current GBFS proximity

Ride Hub status

Vehicle totals count public GBFS positions within 100 metres. “Empty” and “over capacity” are proximity signals—not proof that vehicles are physically parked inside a hub or that dock capacity applies to every nearby device.

Get a feed refresh alert

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.

Map — source-labeled, public-data only
Layers & filters
Focus preset
Legend
311 — critical (ADA ramp/entrance)
311 — high (ADA concern / sidewalk pile)
311 — standard
GBFS — Veo
GBFS — Spin
Columbus Ride Hub · badge = vehicles within 100 m
Vendor observation review area
Cross-vendor pile-up flag
Policy boundary
Populus MDS geography
The Ohio State University municipal boundary

Current snapshot signals

Insights

Review Ride Hub capacity signals, fleet distribution, municipal geography counts, vendor changes between snapshots, or cross-vendor pile-ups. Every relevant result can take you back to the map.

Ride Hub status dashboard

Compare empty and over-capacity proximity signals from the current GBFS snapshot.

Open workflow · public portal

Install the Columbus 311 case lookup

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.

Download skill · ZIP Download instructions · Markdown Read full installation guide

Claude

Native custom skill
  1. Download the ZIP package.
  2. Enable code execution in Settings → Capabilities.
  3. Open Customize → Skills → + Create skill → Upload a skill.
  4. Upload, enable, and invoke it with a CAS ID and address.

Claude’s official skill guide

ChatGPT

Project instructions + source
  1. Download the Markdown instructions.
  2. Create a Project and upload the file as a source.
  3. Add a Project instruction to follow the workflow for Columbus CAS IDs.
  4. Supply both the case ID and address; allow web access when asked.

OpenAI’s official Projects guide

Gemini

Gem instructions + knowledge
  1. Download the Markdown instructions.
  2. Open Gems → New Gem in the Gemini web app.
  3. Add the workflow to the Gem instructions and upload the file under Knowledge.
  4. Save, then supply both the case ID and address.

Google’s official Gems guide

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.

Separate reference collection

Research library

Forecast guides, source inventories, project cards, and comparable analysis charts now live in their own quieter reading space.

Open research library →