Near West Side: All categories · 06:00–12:00 — Pothole requests

• Exploratory description, not a forecast, causal explanation or proof of a change.
• Approximate 95% factor intervals assume independent, constant-variance log residuals and fixed boundaries. They do not account for boundary search, serial dependence or source revisions.
• Confirmed zeros are treated as 1 only for fitting and its diagnostics. Raw counts stay zero; low-count results depend on this convention.
• Independent phase lines may jump at boundaries. Every observation belongs to exactly one phase.
• Reporting, classifications and seasonality can change. Counts are not population-adjusted; a level shift without a slope change is not the target of this search.
• Uses dated last-good cached data, not newly verified source counts.
• Boundary ranges show near-optimal models within 2 BIC units, not confidence intervals. They can be narrow even when the model is uncertain.
• 311 status is its value at retrieval, not at request creation. Newer cohorts have had less time to close; Open/Canceled comparisons can reflect workflow or cohort age rather than changing request volume.
• Current-system 311 coverage starts in 2019. Early phases may reflect adoption/reporting ramp-up; request counts are not completed work or incident prevalence.
• Many dependent filter conditions were searched. No multiple-testing-adjusted significance or causal attribution is claimed.
• Frequency compares fixed equal-length windows of raw counts, not population risk or a celeration-factor ratio. Reporting, classifications and exposure may have changed.

Intervals assume fixed boundaries and independent log residuals. They are not adjusted for the phase or filter search. Near-optimal boundary ranges are not confidence intervals.

Near-optimal boundary range: December 2020–December 2020.

Near-optimal boundary range: January 2022–January 2022.

Newest first. Unknown coverage is not a zero. These are the original saved observations, not fitted or rounded predictions.

Publisher dataset

311 Service Requests · City of Chicago

Source retrieved

2026-11-06T17:28:32.885Z

Publisher update

2026-11-06T15:33:29.000Z

Covered months

January 2019–September 2026

Source note

Source v6vf-nfxy. Joint day/category/hour/applicable-flag/ward/status counts; no addresses, coordinates or incident identifiers. Each year's cells reconcile with an independent source total. Reads are not an atomic publisher snapshot. Current 311 system only, legacy_record=false; includes duplicate requests, not completed work. Status is as currently published, grouped by creation date—not historical status or completion date. Prepared daily community-area snapshot; scheduled rebuild at 06:00 America/Chicago. Full supported history is rechecked for corrections. Retrieval timestamps are preserved; this is not a real-time feed. Local indexed neighborhood snapshot. Totals are for the loaded area before other filters, not citywide totals. Citywide and unassigned-area views use a separate network-backed scope.

Snapshot

daily-v1:8c35ac8d-21c1-45e9-8c56-8bf32f3df7b0:neighborhood-v2:e7960081fd0af1502eb624a9ffea00cf

Discovery method

multi-feed-turn-and-frequency-renewal-v2

Analyze method

exploratory-segmented-log10-ols-zero-as-one-v3

Search plan

a3ffccedeb8d8ce18a30df3636839f775af1e5188e55a1f685695133135c6e35

Evidence run

c68872352234c94318b5369d5ea2e452aa2a2296f353160a630551000efaa122