Tevis Engineering Solutions Tevis EngineeringSolutions
LOGIN
Free Public Tool · Cuyahoga County Open Data

Cleveland Geo Visualizer Every Public Dataset, One Map

What houses are worth and who has been buying them. Which parcels are tax-delinquent, condemned or in foreclosure. Building permits, code violations, vacant structures. Police reports from eight departments, Cleveland’s live dispatch stream, and about 1,300 license-plate cameras. All of it from county and city open data, on one map, on one timeline you can scrub through ten years of. Free, no sign-up, and refreshed every night.

The point is not any one layer. It is that you can stack any of them on top of each other, drag one timeline, and see what lines up. Pick a question and go find out.

Open the Map Ideas to Try Suggest a Dataset

The map itself is on this page. Best on a desktop. Everything on it comes from a public agency; police reports can lag the department by days and this is not an official source. Jump to the map.

Try it — the map, live

Start in Explore and click through the guided views. When one of them makes you curious, press Open in Analyze, add a second dataset from the catalog, and drag the timeline. Click any dot or parcel to read the record behind it.

What you are looking at is real. County and city data fetched live as you pan, and police reports as each department published them. Sensitive reports are shown at the block, never the house — see how names and addresses are handled. If the frame is cramped, open it in its own tab.

Open full screen
ExploreGuided views, one click each. No controls to learn.
AnalyzeThe full stacking tool: any layers, one legend, one timeline.
ProAdds the workbench: trends, correlation, overlap, repeat locations, county rankings.

What you can put on the map

More than 150 live layers from 21 public publishers, plus a nightly police-report feed. Every one of them stacks with every other. A few of the groups:

Property and real estate

Every parcel colored against its own city’s median value. A year of sales, colored by whether the buyer was a person, a company, a trust or a bank. Tax delinquency, foreclosure, forfeited land, condemned structures. Comparable sales, appeal candidates and rent yield by street, from any parcel’s dossier.

License-plate cameras

About 1,300 automated readers county-wide, each with the direction it faces and when it went in, from a public crowd-sourced register. Filter to a city, then lay the net over anything else and see what the cameras face and what they miss.

Police reports

Every published report from eight departments, colored by its most serious offense. Ten years deep for Cleveland Heights. Search by street, offense, report number or officer. Cleveland itself publishes calls for service instead, so its police, fire and EMS dispatch is on the map live.

Permits, code and housing

Building and demolition permits, code violation notices, vacant structures, rental registrations, lead-safe certificates, land bank lots, tax abatement areas. Where a block is turning, and which way.

Streets and crashes

Traffic crashes countywide and in detail for Cleveland, pedestrian and bicycle crashes, traffic counts, the street safety priority index, transit reach, the bike network as it is and as it is planned.

Context

Census tracts and block groups, poverty rate, food access, jobs reachable by transit, the 1940 HOLC redlining grades, zoning, ward and precinct lines. The denominator for everything else, so a count can become a rate.

Street-level view of Cleveland Heights with every parcel drawn as a dot colored purple below, white at, and green above the city's residential median of 182,500 dollars, over a dark street map with the property-value legend at the right.
PropertyEvery parcel against its own city’s median. Live from the county, drawn as you pan. Click one for the full dossier: sales, taxes, owner of record, the lot, comparable sales.
Cuyahoga County with roughly 1,300 license-plate reader cameras mapped as purple clusters along the major roads from Avon Lake to Solon, with a timeline of install dates below.
CamerasAbout 1,300 license-plate readers, county-wide. Where they are and which way each one faces. The timeline below is their install dates, so you can watch the net grow.
Ten years of Cleveland Heights reports as a heat surface: a yellow-to-red gradient concentrated along the main corridors, with purple license-plate camera cones overlaid, and the full 2016 to 2026 timeline below.
Two layers stackedTen years of reports as a heat surface, with the camera net over it. This is the whole idea in one picture: two unrelated public datasets, one map, and a question you can now answer.
A month of Cleveland Heights police reports on a dark map: numbered clusters colored red for violent, orange for serious, yellow for property and green for disorder, inside the city boundary, with the guided-views panel on the left and the ten-year timeline below.
This monthA guided view in Explore. Every report from the last 30 days, colored by severity. The picker at the top switches between the eight departments.
The Analyze view: a severity panel listing violent, serious, property, disorder and traffic counts with offense-type chips, the Cleveland Heights map clustered by severity, and the timeline brushed to a 90-day window from June to September 2026.
AnalyzeThe timeline is shared by every layer. Drag a window and every dataset on the map filters to it together. Click a category to hide it, click a chip to keep only that kind. Add another layer and it joins the same timeline.

Stacks worth trying

Nobody has looked at most of these combinations before, because the data has never been in one place. Here are a few to start with. Every one takes about a minute in Analyze, and none of them needs an account.

Who is buying the distressed blocks

A year of sales colored by buyer type, over tax delinquency and foreclosure. Watch where the LLCs and trusts cluster, and whether that matches where the individual buyers are.

What the cameras face

The license-plate net over ten years of police reports as a heat surface. Where the readers are and where the harm is are two different maps, and the overlap tab will tell you how different.

Calls are not crimes

Cleveland’s live dispatch stream against confirmed reports next door. Most calls are never founded, and a map of calls looks nothing like a map of what actually happened.

Where a block is turning

Building permits over vacant structures and land bank lots, with the timeline dragged back a few years. Investment shows up in permits first, long before it shows up in prices.

Rentals and code enforcement

Rental registrations over code violation notices and lead-safe certificates. Whether the blocks with the most rentals are the blocks getting inspected.

The Cleveland Vibe

A guided view that tests eighteen bad theories properly: whether a Browns blowout, a full moon, a snow day or Friday the 13th moves the numbers at all, and by how much. See which ones survive.

Then make your own. Everything a guided view sets up can be taken apart in Analyze with one click, and every layer in the catalog joins the same legend and timeline. When you find a stack that says something, use the suggestion box and tell us. The good ones become guided views.

Police reports: which departments are covered

The police-report layer is the one part of the map we build ourselves rather than read live. Only departments that publish their reports to a public portal can be on it, and only from the date their portal starts. This table is read from the live feed, so it says what the map says.

DepartmentReports mappedCovered
Cleveland Heights42,9082016-12 → 2026-09
Euclid12,0602014-01 → 2026-09
North Olmsted6,6402017-01 → 2026-08
Shaker Heights3,0722004-04 → 2026-09
Richmond Heights2,3312005-01 → 2026-03
Solon1,9002013-04 → 2026-01
Parma Heights1,2602021-01 → 2026-08
North Randall6252022-01 → 2026-09

70,796 reports across 8 departments. Feed built 2026-09-14.

Not on the list? Cleveland itself publishes calls for service rather than reports; those are on the map as a live dispatch layer. If your department publishes reports somewhere public and is not here, tell us where in the suggestion box and we will look.

How names and addresses are handled

The source is public. That does not make every detail in it something a map should repeat.

Tell us what to add

A dataset you wish was on the map. A department whose reports we should be reading. A stack you built that says something. A feature that would make your own analysis easier. This box goes straight to the engineer who builds it.

No account needed. Nothing you type is published; it goes to us by email.

The same engine, on your data

Nothing here is specific to Cleveland, or to any one kind of data. The map reads any open-data service, puts it on a shared timeline, and stacks it with everything else. What changes is whose data, and what question it is built to answer.

Cities and counties

An open-data portal residents actually use. Permits, code cases, service requests and dispatch on one map, on your own domain, with the privacy rules written down and enforced in the export.

Realtors and investors

Parcels against the local median, a year of sales colored by who bought them, tax-delinquency and appeal candidates, rent yield by street. The property record for a whole county, filtered to a block.

Newsrooms

An embeddable, self-updating map for a beat: housing, development, public safety. Guided views written for the story, the raw layers one click below them, and a data feed your readers can check.

Law firms and insurers

Crash and incident geography by corridor and by month, with the public record behind each dot. Where the same intersection keeps coming up, and when.

Community groups

A neighborhood’s own view of its own data, kept current without anyone maintaining a spreadsheet. Print a month for the meeting; link the map for everyone who could not come.

You own it

A fixed-price build you keep, or a hosted service we run. No per-seat licensing, no per-view metering. The feed format is documented so your data is never locked inside our tool.

How a custom build works

Sources audit

We find what your city, county or agency already publishes, what it would take to read it, and what in it must not reach a map. You get that in writing before anything is built.

Data contract

Which fields, at what precision, refreshed how often, with which categories masked or withheld. The rules this map runs on, adapted to yours.

Build and privacy review

The map, the guided views written for your questions, and an export that refuses to publish anything the contract forbids. Checked twice, by two separate audits, before every refresh.

Hand-off or hosting

On your domain, refreshing on its own with no one on duty. Yours to keep, or ours to run for you, with an alert to a human only when something breaks.

What it is not. It is not a way to reach people named in public records. There is no contact information in it and no lead list comes out of it. It shows what a public agency has already published, on a map, with the parts that identify private individuals taken out.

Common questions

Is this a crime map?
Police reports are one layer of it, and for a few cities they are the deepest layer, but they are a small part of what is on the map. Most of the catalog is property, housing, permits, streets and demographic context from county and city open data. Use it for whatever question you have; the crime layer is there if the question needs it.
Where does the data come from?
Two places. Almost everything, such as parcels, sales, permits, code cases, dispatch calls and camera locations, comes live from the open-data services run by Cuyahoga County, the City of Cleveland and the surrounding municipalities, fetched by your browser at the moment you look and never stored by us. The police-report layer is the exception: it is read nightly from each department’s own public report portal by our software, and the coverage table above lists every department and the dates covered.
How do I do my own analysis?
Switch to Analyze from the top bar, open the catalog, and add any layers you like. They all share one legend and one timeline, so dragging a window filters every dataset on the map together, and clicking a category hides or isolates it. Pro adds a workbench with trend detection, pairwise correlation, hot-spot overlap, repeat locations and a county-wide ranking of any layer. Everything a guided view sets up can be opened in Analyze and changed.
Is any of this official?
No. It is an independent tool built by Tevis Engineering Solutions from data that public agencies publish themselves. The live layers are as current as the agency that runs them. Police reports can lag the department by days, and a report is a record that somebody called and an officer wrote it up, not a conviction. For anything that matters, confirm it with the agency itself.
How current is it?
The live county and city layers are fetched at the moment you look, so they are as current as the agency that publishes them. The police-report feed rebuilds every night, and the date it was last built is shown inside the map. New reports typically appear within a day or two of a department publishing them.
Why do some reports show a block instead of an address?
Sexual-offense and domestic reports are shown at the hundred block, such as 24XX Noble Rd, with the dot placed within about a hundred meters rather than on the house. A precise dot on that kind of report would identify the victim at their own front door, and nothing about a map needs that. Every other report keeps the address as the department published it, and civilian names are never on the map in any category.
Can I suggest a dataset or a feature?
Yes, and please do. The suggestion box on this page goes straight to the engineer who builds the tool. Datasets that a public agency already publishes to an open-data service can usually be added quickly; a police department is added when its reports are published somewhere public we can read. Good stacks that people send in become guided views.
Can I embed the map or get the data?
Yes to both. The map can be embedded in an iframe on your own site, as it is on this page, and the police feed is a documented JSON format we can point you at. Use the request form below and say what you have in mind.
Can you build something like this for us?
That is what this page is for. The same engine runs on any open-data source: your city’s permits and code cases, a county’s parcels and transfers, a dispatch feed, a set of inspection records. We scope it, build it, review it for privacy the way this one was, and hand it over as a fixed-price build you own or a hosted service we run for you. Ask for a quote and you will get a number, not a sales call.

Build one for your city, newsroom or firm

Tell us whose data it is and the question it should answer. We will look at what is already published, show you what it would look like on the map, and come back with a fixed number. Straight to the engineer, one-business-day reply.