Skip to content

US city eviction-filing pressure (weekly)

License unclearFresh
Query in workbench

Follow this dataset

Get a notice in your feed when a new snapshot is published. Optionally, we also POST it to your webhook.

Must be a public https address. We never follow redirects.

The full snapshot isn't published yet — check back after the next refresh.Download sample CSVDownload sample JSONSample rows only (up to 20) — not the complete dataset.

Weekly eviction-filing pressure intelligence for 43 US cities/regions from the keyless Princeton Eviction Lab Eviction Tracking System (court filing counts aggregated from census tract / ZIP rows, 2019-12-29 onward). Method: resolve the 43 ETS site labels to city/state/ISO codes via a closed dict (unknown sites fail loudly), sum tract filings to city-weeks, and derive filings vs the publisher's prepandemic baseline average (``filings_vs_baseline``, null where a site has no baseline), a 4-week moving average with 4-week momentum, a documented 0-100 ``eviction_pressure_score`` (100 * clip(ratio,0,2)/2), and fixed-cut pressure tiers (subdued/normal/elevated/severe). Caveats: the most recent ~3 weeks are undercounted from court processing delays (publisher footnote; flagged ``preliminary_flag`` = 1 — filter to 0 for stable signals); the prepandemic-baseline variant is unpublished for 4 sites (Atlanta, Oklahoma City, Other Oregon Counties, Toledo); 'sealed' GEOID rows are real filings with unresolvable tracts, kept in city totals. Units: filing counts per week; ratios unitless; score 0-100. Original aggregation of openly published court-record counts; commercial reuse status unclear — attribution required, see license. Sources: Eviction Lab, Princeton University, Eviction Tracking System v3.0.

Source
Rows
14,807
Columns
26
Source cadence
Weekly
Last refreshed
Sep 30, 2026
Theme
housing

Use your own AI key

Once today's free allowance is used up, AI features can run on your own provider account.

Kept in this browser tab only (cleared when you close it) and sent with each AI request. Our servers use it for that request and never store or log it.