Fly-tipping Observatory
Explore reports, places and patterns — with transparent evidence about what the data does and doesn't show.
What the reports tell us
Highest report counts
Understand the denominator. These figures count reports submitted to the council, not necessarily distinct dumping incidents. Duplicate flags, highly active reporting accounts and incomplete records affect interpretation. See for details.
Comparing Croydon's wards
Ward reporting and community context
Distinct identifier totals are calculated over the entire selected period, not added between months.
Population estimates and councillors are sourced administrative reference data, not attributes of an incident.
24h/48h valid: percentage of reports with a valid recorded completion interval. 24h/48h all: percentage of all reports, including open, unknown and missing completion times. Thresholds are strictly less than 24/48 hours. Distinct IDs per 1,000 uses the selected period and historical population, and counts reporting references rather than people. Detailed completion rates are hidden for wards with fewer than 10 reports.
Categories and reporting accounts
Select “All environmental reports” to compare fly-tipping with other council service types.
Reports by category
Category reporting identifiers
Reporting over time
Monthly council reports
Monthly distinct reporting identifiers
Three-month rolling trend and statistical process control
Council report and reporting-account trends for the selected filters. Months with missing accepted FOI coverage are gaps, not zeros.
Awaiting data…
Explore individual reports
Server-side DataTables: search, sort and page through the filtered council records. Addresses are nearest *reported* locations, not confirmed property addresses. Publication is controlled by a separate privacy approval setting. User identifiers are never exposed.
Council FOI records
The filters above apply to the table and CSV download. —
| JobCode | Reported | Category | Ward | Nearest reported location | Status | Completed | Completed at | Within 24h | Hours | Duplicate | Council resolution | Source | Contractor jobs | Contractor state | Contractor resolution | Contractor SLA |
|---|
“Within 24h” means from creation to recorded completion, not contractor SLA compliance. Missing or inconsistent data is Unknown. Public synchronous CSV exports are limited to 50,000 matching rows; refine the filters for larger result sets.
Patterns, performance and reporting concentration
The same applied filters govern all measures below. Count of reports does not equal count of incidents.
Weekday × hour reported
Local source timestamps; darker cells represent more reports.
Recorded completion distribution
Calculated from valid council completion timestamps, not proof of clearance.
Completion performance · weekly & local comparisons
Council completion timestamps, independently reported contractor SLAs, backlog and descriptive changes. Uses the same reporting filters as the dashboard.
Weekly completion performance
Blue: <24h, orange: <48h, purple: rolling four-week 24h rate · valid measured completionsSee weekly figures and denominators
Completion intervals by ward
Completion intervals by category
Median and P90 use only records with valid non-negative completion intervals.
Wards with notable deterioration
Latest 28 days versus preceding 28 days · ≥15 percentage-point decline · minimum sample sizesContractor CRM · independent operational context
Contractor data may be missing or delayed. Its SLA designation is not equivalent to a council elapsed-hour measure.
Rates refer to report creation dates, and completed status is not proof of physical clearance. Open reports and reports lacking usable completion timestamps are separated; percentages of measured completions exclude them. A later FOI release may revise earlier records.
Compared with preceding equivalent period
Population-adjusted ward rates
Reports per 1,000 residents during the selected period; only sourced ADMIN-approved denominators are used.
Persistent locations ranked by descriptive score
Approximately 100m × 100m grid squares centred at stated coordinates (not 100m-radius circles). Ranked by recurring-report score and labelled with source ward(s). Select Investigate to open the area on the map.
Deprivation context · IMD 2025
Loading official geographic context…
Fly-tipping and deprivation · IMD 2025
Geographical association between reports and LSOA deprivation deciles. Sourced population rates appear only with complete population denominators.
Waiting for selected data…
Counts describe reporting locations, not the deprivation or behaviour of individuals.
Reporting concentration by ward and category
Share attributed to the most active reporting account and ten most active accounts. High reporting activity is not evidence of incorrect reports.
Participation and reporting consistency
Aggregate measures of reporting identifiers. An identifier may represent a resident, shared account, organisation or staff member — not necessarily one person.
How many separate days are accounts active?
Accounts grouped by distinct reporting days in the chosen period; no account-level data exposed.
Participation over time
First in selection is not first-ever reporting. Missing source coverage is not zero.
Which weekdays attract more active identifiers?
Distinct active reporting identifiers by weekday; the same account can appear on multiple weekdays.
Visual stories worth sharing
Ten ranked hotspot maps plus reporting and community graphics from the current filters. Export all eligible graphics, with map overlays and reproducible source metadata, in a ZIP.
Design a graphic
Data from the selected months, wards, categories and duplicate setting. Graphics use verified dashboard figures, with missing data left unavailable rather than invented.
Select a visualisation to preview.
Data quality and coverage
What we've received, where the gaps are, and the limitations to consider.
Council FOI
Contractor CRM
Council ↔ contractor
Exact LCS reference matches only. Comparisons require full accepted monthly coverage from both sources.
Data linkage is not contractor performance. Closed council reports, contractor Completed/Not Completed states and actual waste clearance are distinct. Raw category names and ward labels are retained rather than silently reconciled.
How to interpret this data
Heatmaps, report pins and hotspot history
25m native analysis cells, adaptive zoom detail and optional source-location pins. Reported places are approximate *nearest locations* — they do not establish responsibility by any resident or property.
Explore Croydon
Preparing geographic data…
Display settings Mode-specific controls
Find & investigate an area
Heat intensity and gradient are visual settings, not additional reports. The 25m analysis grid is combined into larger cells at lower zoom levels. Exact pins, searchable source addresses and radius results are withheld until the explicit privacy-approval switch is enabled. Base map © OpenStreetMap contributors.