Vagrancy/Loitering — Philadelphia, full monthly history
Philadelphia Police Dept · INCT incident system Live · Carto SQL API

Monthly logged incidents coded Vagrancy / Loitering in Philadelphia, from the earliest record in the table through the latest available month. Pulled live at load; toggle the sibling public-order codes to test whether the offense was reclassified rather than abandoned.

Peak year
 
Latest full year
 
Current year, YTD
 
Querying phl.carto.com …

2026, day by day

Vagrancy/Loitering incidents this calendar year at daily resolution — shown as bars with a 7-day rolling average — now with Disorderly Conduct and Public Drunkenness overlaid as their own rolling lines. Hover any day for all three totals.

Vagrancy/Loitering, YTD
 
Busiest single day
 
Busiest month
 
Querying phl.carto.com …

April 1 to now, day by day

The spring crackdown window at daily resolution — Vagrancy/Loitering incidents from April 1 through the latest available date, as bars with a 7-day rolling average, with Disorderly Conduct and Public Drunkenness overlaid as rolling lines. Hover any day for all three totals.

Vagrancy/Loitering, since Apr 1
 
Busiest single day
 
Busiest month
 
Querying phl.carto.com …

4 year comparison

Weekly counts for the low-level offenses most often cited against unhoused people, four seasons stacked on the same axis so the years read against each other. Three winters hold a flat baseline; 2026 breaks the pattern. Live from the incidents table — switch the category, toggle years, and flip the window.

Category
Window Years
y · incidents per week
Querying phl.carto.com …

Weeks are anchored to a shared Dec 29 start so every season lines up. 2026 runs only through the latest reported week, so its line stops where the data does — in full-year mode the prior years continue and 2026 does not. As with the panels above, "All" sums the five listed offense codes as they appear in the incident table.

Read this before you cite it. These are logged incidents the PPD coded with a given text_general_code — not the full universe of street enforcement. A falling line means fewer records of that label entered INCT. Two very different things can produce it: the conduct was recoded into a sibling label (watch for a rise that mirrors the fall — turn on the overlays), or enforcement moved to a channel this table never captures (Code Violation Notices, outreach "resolutions"), in which case every line can fall at once. The most recent month or two are provisional and lag-prone. Counted labels: checking…

Source & exact query
Source: City of Philadelphia, incidents_part1_part2, via the Carto SQL API at phl.carto.com. Context markers: COVID onset (Mar 2020); the FBI's mandatory SRS→NIBRS cutover (Jan 2021), which merged vagrancy into a combined Curfew/Loitering/Vagrancy class and could shift local coding; Grants Pass v. Johnson (Jun 2024).