InMyCity

Trust Center

Data & transparency

How we ingest, reconcile, and publish civic data — live coverage, source freshness, and links to methodology and our public accuracy track record.

Geographic coverage

Live block counts and city tiers from the warehouse — active cities have incident-level feeds where available; candidate cities ship block grid, assessments, demographics, and FBI UCR crime benchmarks when no open feed exists.

Loading coverage snapshot…

Coverage by metro

Boston metro

Active: Boston, Cambridge

  • Full civic spine: crime, fire, FIO, 311, permits, EMS, inspections, business licenses, assessments.

Chicago metro

Active: Chicago

  • Crime, 311, permits, and Cook County parcels.

Atlanta metro

Active: Atlanta

Candidate: Decatur, Sandy Springs, Marietta, Brookhaven, Roswell, Alpharetta, Dunwoody, Smyrna, Johns Creek, Peachtree Corners, Tucker

  • Atlanta: Fulton County Socrata crime incidents (~100k rows) plus county parcel assessors.
  • Decatur: FBI UCR crime benchmark + DeKalb County parcel assessments; other spine domains not published as open data.
  • Suburbs: Census block grid, county parcels (Fulton, DeKalb, Cobb, Gwinnett, Douglas), ACS demographics, Atlanta-metro economy series.
  • Where a city lacks an open incident feed, crime metrics use FBI Crime Data Explorer agency UCR benchmarks with an explicit UI caveat — not block-level precision.
  • Roswell: ArcGIS Part 1 crimes connector (rolling ~30-day window) when the publisher feed has records.

Cincinnati metro

Active: Cincinnati

  • Full civic spine: crime, fire, FIO, 311, permits, EMS, inspections, business licenses, and Hamilton County parcel assessments (CAGIS).

Other metros

Active: Seattle, Austin

  • Partial domain coverage varies by city — see the live source catalog below.

How we handle data

  • Source fidelity. Every record carries jurisdiction and source metadata so you can trace it back to the reporting agency.
  • Metro-aware catalogs. Source freshness, domain availability, and economy labels resolve per city — Boston feeds are not reused for Atlanta or Chicago.
  • Multi-domain spine. Crime, fire, 311, permits, assessments, and economy metrics join through the same geography — block to nation — so comparisons are apples-to-apples within a metro.
  • Benchmark fallback. When a city has no open incident-level crime feed, we surface FBI Crime Data Explorer agency UCR annual estimates with an explicit caveat — never as fake block-level counts.
  • No enrichment for sale. We geocode and join to Census geography for analysis — we do not resell or broker individual records.
  • Tier-based history. Free accounts see the last 90 days; Explorer Plus includes 12 months; Analyst Solo and Analyst Team include full warehouse history.
  • Sensitive domains. FIO and similar datasets include explicit caveats in the UI and are handled with care in aggregations.
  • Transparent limits. API rate limits and query windows are enforced server-side and reflected in responses when data is clamped.
  • Oracle acceptable use. Permitted and prohibited uses for Oracle API and MCP consumers, plus an appeal path.

Source catalog & warehouse freshness

Live status from dim_source — latest data date, last load, and whether each connector is within its expected cadence. This is the canonical list of ingested publishers (Boston, Atlanta metro, Chicago, federal benchmarks, and county parcel feeds).

Loading warehouse freshness…

Fleet operations

Scheduled connector ingestion, run history, and SLA adherence across the source catalog.

Loading fleet status…

Cross-source reconciliation

When two authorities report the same metric, we compare them side-by-side with a confidence score and an explanation for any gap — lag, definition, coverage, or genuine anomaly.

No cross-source comparisons are published yet for this environment.

Federal & reference layers

  • FBI Crime Data Explorer (agency UCR benchmarks)
  • U.S. Census Bureau — TIGER/Line & ACS 5-Year
  • U.S. Bureau of Labor Statistics — LAUS, QCEW, CPI
  • NOAA weather grid (block-linked where available)

Model transparency

What each intelligence surface in the product is for, what we will not use it for, and whether it currently meets our evaluation standards.

Questions or corrections

If you believe a record is incorrect, contact the originating agency — we mirror their published data. For product or attribution questions, reach us through your dashboard or at hello@inmycity.app. Methodology for derived scores is in the Methodology section of our Trust Center. Model track record lives on Accuracy.