Data & pipelines
det.land is built on public datasets, kept current by automated pipelines and joined into a single graph — so every number on the site can be traced back to where it came from. The goal is simple: reliable, lineage-tracked civic data across many datasets, at scale.
A connected graph
Underneath every page is one graph. Parcels, buildings, owners, permits, court cases, and boundaries are linked through shared keys — a parcel, a building, a resolved owner. That shared spine is what lets a single eviction case carry its property, its owner, its compliance status, and its neighborhood at once.
Open, official sources
Everything comes from public data — the City of Detroit, Wayne County, HUD, the courts, and other open publishers. We don't invent data; we collect it, geocode it, and connect it. Each dataset below names its publisher and links to the original.
Automated & fresh
Pipelines run on their own schedules — some daily, some weekly — with no manual exports and no stale snapshots posing as current. The table below shows when each source last refreshed and how fresh the underlying data is.
Reliability & lineage
Refreshes are guarded so a bad run can't silently wipe or truncate a table, and we try to be honest about limits — what each dataset can and can't tell you. Every claim on the site should trace back to a source here.
Data Sources
| Source | Publisher | Frequency | Portal updated | det.land refresh | Data freshness | Rows | Status |
|---|
Glossary
Terms, abbreviations and reading rules used across det.land — parcel profiles, boundary panels, and the topic pages, whose figures link back to the entry that defines them.