Datasets:
Download README.md from EDK-Earth/sewer-issues: direct link, hf CLI and curl.
- Browser
- Download file 5.84 kB
-
https://huggingface.co/datasets/EDK-Earth/sewer-issues/resolve/main/README.md
- Command line
-
hf download hf://datasets/EDK-Earth/sewer-issues/README.md
-
curl -L -o README.md https://huggingface.co/datasets/EDK-Earth/sewer-issues/resolve/main/README.md
pretty_name: Sewer Issues (311) - 30,000-record Geospatial Sample
license: other
size_categories:
- 10K<n<100K
task_categories:
- tabular-classification
- other
language:
- en
annotations_creators:
- no-annotation
language_creators:
- found
multilinguality:
- monolingual
source_datasets:
- original
tags:
- geospatial
- open-data
- tabular
- parquet
- geojson
- csv
- sewer
- '311'
- infrastructure
- utilities
- service-requests
- public-records
- year-2025
Sewer Issues (311) - 30,000-record Geospatial Sample
A free, ready-to-use sample of 30,000 geolocated sewer issue service requests (calendar year 2025), published by EDK.
Sewer backups, blockages and related complaints reported through municipal 311 systems, with coordinates and the original city-specific fields preserved.
This is a 30,000-record sample of a much larger collection (about 1,138,000 source records). Need the full dataset, other places or years, or live search? See the EDK atlas.
At a glance
| Records | 30,000 |
| Period | Calendar year 2025 |
| Geometry | Point, WGS 84 (EPSG:4326) |
| Formats | Parquet, GeoJSON, CSV |
| Publisher | EDK |
Quick start
from datasets import load_dataset
ds = load_dataset("parquet", data_files="hf://datasets/EDK-Earth/sewer-issues/data.parquet", split="train")
print(ds)
print(ds[0])
import pandas as pd
import json
df = pd.read_parquet("hf://datasets/EDK-Earth/sewer-issues/data.parquet")
df["properties"] = df["properties"].apply(json.loads)
df[["latitude", "longitude"]].describe()
Search millions more geographic features
EDK provides developers and AI systems access to millions of geographic features and geolocated imagery spanning infrastructure, places, roads, buildings, nature and community issues.
Build with EDK
- Geographic Feature List — browse geographic features available through EDK
- EDK — programmable infrastructure for Earth
- Developer Documentation — APIs, tools, guides, and examples
- SDK — build geographic capabilities directly into applications
- CLI — work with geographic search and spatial data from the terminal
- MCP — connect geographic search and spatial tools to AI agents
Use cases
- Finding areas with recurring sewer complaints
- Infrastructure maintenance and capital planning research
- Correlating complaints with rainfall, flooding or building age
- Benchmarking city service response
Schema
| Column | Type | Description |
|---|---|---|
id |
string | Record identifier from the source table. |
latitude |
float64 | Latitude in decimal degrees (WGS 84). |
longitude |
float64 | Longitude in decimal degrees (WGS 84). |
description |
string | Short plain-language summary of the record (category, type and status) taken from the source's metadescription field. |
attribution |
string | Original data provider and dataset the record comes from. Cite this when you reuse the record. |
properties |
string | JSON-encoded object with the original source fields for the record (keys vary by record). |
The description column is a short plain-language summary of each record (category, type and status), ready to use for search, labelling or text models.
Properties
The properties column is a JSON string holding the original source attributes. The most common keys in this sample:
| Key | Example value |
|---|---|
origin |
Phone Call |
location |
(41.91179829672742, -87.71905485986424) |
precinct |
11 |
duplicate |
false |
police_beat |
2535 |
street_name |
WABANSIA |
created_hour |
15 |
x_coordinate |
1151451.0394360537 |
y_coordinate |
1911045.0555632855 |
created_month |
2 |
legacy_record |
false |
police_sector |
3 |
Keys vary by record and source; not every field is populated for every row.
Files
Methodology
Records are exported directly from the EDK geographic index, ordered by identifier and capped at 30,000 rows. Coordinates are WGS 84. Source fields are preserved in properties without reinterpretation. Inclusion means a record appeared in the contributing public dataset; it was not independently verified.
Sources and attribution
Every record names its original provider in the attribution column. Contributing sources:
- Edmonton Open Data - 311 Requests (Edmonton, AB)
- Chicago, IL - 311 Service Requests
- Calgary Open Data - 311 Service Requests (Calgary, AB)
- Cambridge Open Data - Commonwealth Connect Service Requests (Cambridge, MA)
- NYC Open Data - NYC 311 Service Requests from 2020 to Present (New York)
Prepared and distributed by EDK.
License
Records come from public municipal open-data portals whose terms vary by city. Credit the provider named in each record's attribution column and EDK when you reuse this data.