Datasets:
Rebrand Outerview to EDK: update names, links (edk.earth, edk.earth/docs) and clean up README
Browse files
README.md
CHANGED
|
@@ -1,130 +1,130 @@
|
|
| 1 |
-
---
|
| 2 |
-
pretty_name: "Sewer Issues (311) - 30,000-record Geospatial Sample"
|
| 3 |
-
license: other
|
| 4 |
-
size_categories: ["10K<n<100K"]
|
| 5 |
-
task_categories: ["tabular-classification", "other"]
|
| 6 |
-
language: ["en"]
|
| 7 |
-
annotations_creators: ["no-annotation"]
|
| 8 |
-
language_creators: ["found"]
|
| 9 |
-
multilinguality: ["monolingual"]
|
| 10 |
-
source_datasets: ["original"]
|
| 11 |
-
tags: ["geospatial", "open-data", "tabular", "parquet", "geojson", "csv", "sewer", "311", "infrastructure", "utilities", "service-requests", "public-records", "year-2025"]
|
| 12 |
-
---
|
| 13 |
-
|
| 14 |
-
# Sewer Issues (311) - 30,000-record Geospatial Sample
|
| 15 |
-
|
| 16 |
-
A free, ready-to-use sample of **30,000 geolocated sewer issue service requests** (calendar year 2025), published by **[
|
| 17 |
-
|
| 18 |
-
Sewer backups, blockages and related complaints reported through municipal 311 systems, with coordinates and the original city-specific fields preserved.
|
| 19 |
-
|
| 20 |
-
> **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 [
|
| 21 |
-
|
| 22 |
-
## At a glance
|
| 23 |
-
|
| 24 |
-
| | |
|
| 25 |
-
| --- | --- |
|
| 26 |
-
| Records | 30,000 |
|
| 27 |
-
| Period | Calendar year 2025 |
|
| 28 |
-
| Geometry | Point, WGS 84 (EPSG:4326) |
|
| 29 |
-
| Formats | Parquet, GeoJSON, CSV |
|
| 30 |
-
| Publisher | [
|
| 31 |
-
|
| 32 |
-
## Quick start
|
| 33 |
-
|
| 34 |
-
```python
|
| 35 |
-
from datasets import load_dataset
|
| 36 |
-
|
| 37 |
-
ds = load_dataset("parquet", data_files="hf://datasets/
|
| 38 |
-
print(ds)
|
| 39 |
-
print(ds[0])
|
| 40 |
-
```
|
| 41 |
-
|
| 42 |
-
```python
|
| 43 |
-
import pandas as pd
|
| 44 |
-
import json
|
| 45 |
-
|
| 46 |
-
df = pd.read_parquet("hf://datasets/
|
| 47 |
-
df["properties"] = df["properties"].apply(json.loads)
|
| 48 |
-
df[["latitude", "longitude"]].describe()
|
| 49 |
-
```
|
| 50 |
-
|
| 51 |
-
## Search millions more geographic features
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
|
| 55 |
-
<!--
|
| 56 |
-
## Build with
|
| 57 |
-
|
| 58 |
-
- [Geographic Feature List](https://
|
| 59 |
-
- [
|
| 60 |
-
- [Developer Documentation](https://
|
| 61 |
-
- [SDK](https://
|
| 62 |
-
- [CLI](https://
|
| 63 |
-
- [MCP](https://
|
| 64 |
-
<!--
|
| 65 |
-
|
| 66 |
-
## Use cases
|
| 67 |
-
|
| 68 |
-
- Finding areas with recurring sewer complaints
|
| 69 |
-
- Infrastructure maintenance and capital planning research
|
| 70 |
-
- Correlating complaints with rainfall, flooding or building age
|
| 71 |
-
- Benchmarking city service response
|
| 72 |
-
|
| 73 |
-
## Schema
|
| 74 |
-
|
| 75 |
-
| Column | Type | Description |
|
| 76 |
-
| --- | --- | --- |
|
| 77 |
-
| `id` | string | Record identifier from the source table. |
|
| 78 |
-
| `latitude` | float64 | Latitude in decimal degrees (WGS 84). |
|
| 79 |
-
| `longitude` | float64 | Longitude in decimal degrees (WGS 84). |
|
| 80 |
-
| `description` | string | Short plain-language summary of the record (category, type and status) taken from the source's metadescription field. |
|
| 81 |
-
| `attribution` | string | Original data provider and dataset the record comes from. Cite this when you reuse the record. |
|
| 82 |
-
| `properties` | string | JSON-encoded object with the original source fields for the record (keys vary by record). |
|
| 83 |
-
|
| 84 |
-
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.
|
| 85 |
-
|
| 86 |
-
## Properties
|
| 87 |
-
|
| 88 |
-
The `properties` column is a JSON string holding the original source attributes. The most common keys in this sample:
|
| 89 |
-
|
| 90 |
-
| Key | Example value |
|
| 91 |
-
| --- | --- |
|
| 92 |
-
| `origin` | `Phone Call` |
|
| 93 |
-
| `location` | `(41.91179829672742, -87.71905485986424)` |
|
| 94 |
-
| `precinct` | `11` |
|
| 95 |
-
| `duplicate` | `false` |
|
| 96 |
-
| `police_beat` | `2535` |
|
| 97 |
-
| `street_name` | `WABANSIA` |
|
| 98 |
-
| `created_hour` | `15` |
|
| 99 |
-
| `x_coordinate` | `1151451.0394360537` |
|
| 100 |
-
| `y_coordinate` | `1911045.0555632855` |
|
| 101 |
-
| `created_month` | `2` |
|
| 102 |
-
| `legacy_record` | `false` |
|
| 103 |
-
| `police_sector` | `3` |
|
| 104 |
-
|
| 105 |
-
Keys vary by record and source; not every field is populated for every row.
|
| 106 |
-
|
| 107 |
-
## Files
|
| 108 |
-
|
| 109 |
-
- [Parquet](https://huggingface.co/datasets/
|
| 110 |
-
- [GeoJSON](https://huggingface.co/datasets/
|
| 111 |
-
- [CSV](https://huggingface.co/datasets/
|
| 112 |
-
## Methodology
|
| 113 |
-
|
| 114 |
-
Records are exported directly from the
|
| 115 |
-
|
| 116 |
-
## Sources and attribution
|
| 117 |
-
|
| 118 |
-
Every record names its original provider in the `attribution` column. Contributing sources:
|
| 119 |
-
|
| 120 |
-
- [Edmonton Open Data - 311 Requests (Edmonton, AB)](https://data.edmonton.ca/City-Administration/311-Requests/q7ua-agfg)
|
| 121 |
-
- Chicago, IL - 311 Service Requests
|
| 122 |
-
- [Calgary Open Data - 311 Service Requests (Calgary, AB)](https://data.calgary.ca/Services-and-Amenities/311-Service-Requests/iahh-g8bj)
|
| 123 |
-
- [Cambridge Open Data - Commonwealth Connect Service Requests (Cambridge, MA)](https://data.cambridgema.gov/Public-Works/Commonwealth-Connect-Service-Requests/2z9k-mv9g)
|
| 124 |
-
- [NYC Open Data - NYC 311 Service Requests from 2020 to Present (New York)](https://data.cityofnewyork.us/Social-Services/311-Service-Requests-from-2020-to-Present/erm2-nwe9)
|
| 125 |
-
|
| 126 |
-
Prepared and distributed by [
|
| 127 |
-
|
| 128 |
-
## License
|
| 129 |
-
|
| 130 |
-
Records come from public municipal open-data portals whose terms vary by city. Credit the provider named in each record's `attribution` column and **
|
|
|
|
| 1 |
+
---
|
| 2 |
+
pretty_name: "Sewer Issues (311) - 30,000-record Geospatial Sample"
|
| 3 |
+
license: other
|
| 4 |
+
size_categories: ["10K<n<100K"]
|
| 5 |
+
task_categories: ["tabular-classification", "other"]
|
| 6 |
+
language: ["en"]
|
| 7 |
+
annotations_creators: ["no-annotation"]
|
| 8 |
+
language_creators: ["found"]
|
| 9 |
+
multilinguality: ["monolingual"]
|
| 10 |
+
source_datasets: ["original"]
|
| 11 |
+
tags: ["geospatial", "open-data", "tabular", "parquet", "geojson", "csv", "sewer", "311", "infrastructure", "utilities", "service-requests", "public-records", "year-2025"]
|
| 12 |
+
---
|
| 13 |
+
|
| 14 |
+
# Sewer Issues (311) - 30,000-record Geospatial Sample
|
| 15 |
+
|
| 16 |
+
A free, ready-to-use sample of **30,000 geolocated sewer issue service requests** (calendar year 2025), published by **[EDK](https://edk.earth)**.
|
| 17 |
+
|
| 18 |
+
Sewer backups, blockages and related complaints reported through municipal 311 systems, with coordinates and the original city-specific fields preserved.
|
| 19 |
+
|
| 20 |
+
> **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](https://edk.earth/atlas).
|
| 21 |
+
|
| 22 |
+
## At a glance
|
| 23 |
+
|
| 24 |
+
| | |
|
| 25 |
+
| --- | --- |
|
| 26 |
+
| Records | 30,000 |
|
| 27 |
+
| Period | Calendar year 2025 |
|
| 28 |
+
| Geometry | Point, WGS 84 (EPSG:4326) |
|
| 29 |
+
| Formats | Parquet, GeoJSON, CSV |
|
| 30 |
+
| Publisher | [EDK](https://edk.earth) |
|
| 31 |
+
|
| 32 |
+
## Quick start
|
| 33 |
+
|
| 34 |
+
```python
|
| 35 |
+
from datasets import load_dataset
|
| 36 |
+
|
| 37 |
+
ds = load_dataset("parquet", data_files="hf://datasets/EDK-Earth/sewer-issues/data.parquet", split="train")
|
| 38 |
+
print(ds)
|
| 39 |
+
print(ds[0])
|
| 40 |
+
```
|
| 41 |
+
|
| 42 |
+
```python
|
| 43 |
+
import pandas as pd
|
| 44 |
+
import json
|
| 45 |
+
|
| 46 |
+
df = pd.read_parquet("hf://datasets/EDK-Earth/sewer-issues/data.parquet")
|
| 47 |
+
df["properties"] = df["properties"].apply(json.loads)
|
| 48 |
+
df[["latitude", "longitude"]].describe()
|
| 49 |
+
```
|
| 50 |
+
|
| 51 |
+
## Search millions more geographic features
|
| 52 |
+
|
| 53 |
+
EDK provides developers and AI systems access to **millions of geographic features and geolocated imagery** spanning infrastructure, places, roads, buildings, nature and community issues.
|
| 54 |
+
|
| 55 |
+
<!-- edk-tools:start -->
|
| 56 |
+
## Build with EDK
|
| 57 |
+
|
| 58 |
+
- [Geographic Feature List](https://edk.earth/atlas) — browse geographic features available through EDK
|
| 59 |
+
- [EDK](https://edk.earth) — programmable infrastructure for Earth
|
| 60 |
+
- [Developer Documentation](https://edk.earth/docs) — APIs, tools, guides, and examples
|
| 61 |
+
- [SDK](https://edk.earth/docs/sdk) — build geographic capabilities directly into applications
|
| 62 |
+
- [CLI](https://edk.earth/docs/cli) — work with geographic search and spatial data from the terminal
|
| 63 |
+
- [MCP](https://edk.earth/docs/mcp) — connect geographic search and spatial tools to AI agents
|
| 64 |
+
<!-- edk-tools:end -->
|
| 65 |
+
|
| 66 |
+
## Use cases
|
| 67 |
+
|
| 68 |
+
- Finding areas with recurring sewer complaints
|
| 69 |
+
- Infrastructure maintenance and capital planning research
|
| 70 |
+
- Correlating complaints with rainfall, flooding or building age
|
| 71 |
+
- Benchmarking city service response
|
| 72 |
+
|
| 73 |
+
## Schema
|
| 74 |
+
|
| 75 |
+
| Column | Type | Description |
|
| 76 |
+
| --- | --- | --- |
|
| 77 |
+
| `id` | string | Record identifier from the source table. |
|
| 78 |
+
| `latitude` | float64 | Latitude in decimal degrees (WGS 84). |
|
| 79 |
+
| `longitude` | float64 | Longitude in decimal degrees (WGS 84). |
|
| 80 |
+
| `description` | string | Short plain-language summary of the record (category, type and status) taken from the source's metadescription field. |
|
| 81 |
+
| `attribution` | string | Original data provider and dataset the record comes from. Cite this when you reuse the record. |
|
| 82 |
+
| `properties` | string | JSON-encoded object with the original source fields for the record (keys vary by record). |
|
| 83 |
+
|
| 84 |
+
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.
|
| 85 |
+
|
| 86 |
+
## Properties
|
| 87 |
+
|
| 88 |
+
The `properties` column is a JSON string holding the original source attributes. The most common keys in this sample:
|
| 89 |
+
|
| 90 |
+
| Key | Example value |
|
| 91 |
+
| --- | --- |
|
| 92 |
+
| `origin` | `Phone Call` |
|
| 93 |
+
| `location` | `(41.91179829672742, -87.71905485986424)` |
|
| 94 |
+
| `precinct` | `11` |
|
| 95 |
+
| `duplicate` | `false` |
|
| 96 |
+
| `police_beat` | `2535` |
|
| 97 |
+
| `street_name` | `WABANSIA` |
|
| 98 |
+
| `created_hour` | `15` |
|
| 99 |
+
| `x_coordinate` | `1151451.0394360537` |
|
| 100 |
+
| `y_coordinate` | `1911045.0555632855` |
|
| 101 |
+
| `created_month` | `2` |
|
| 102 |
+
| `legacy_record` | `false` |
|
| 103 |
+
| `police_sector` | `3` |
|
| 104 |
+
|
| 105 |
+
Keys vary by record and source; not every field is populated for every row.
|
| 106 |
+
|
| 107 |
+
## Files
|
| 108 |
+
|
| 109 |
+
- [Parquet](https://huggingface.co/datasets/EDK-Earth/sewer-issues/resolve/main/data.parquet)
|
| 110 |
+
- [GeoJSON](https://huggingface.co/datasets/EDK-Earth/sewer-issues/resolve/main/data.geojson)
|
| 111 |
+
- [CSV](https://huggingface.co/datasets/EDK-Earth/sewer-issues/resolve/main/data.csv)
|
| 112 |
+
## Methodology
|
| 113 |
+
|
| 114 |
+
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.
|
| 115 |
+
|
| 116 |
+
## Sources and attribution
|
| 117 |
+
|
| 118 |
+
Every record names its original provider in the `attribution` column. Contributing sources:
|
| 119 |
+
|
| 120 |
+
- [Edmonton Open Data - 311 Requests (Edmonton, AB)](https://data.edmonton.ca/City-Administration/311-Requests/q7ua-agfg)
|
| 121 |
+
- Chicago, IL - 311 Service Requests
|
| 122 |
+
- [Calgary Open Data - 311 Service Requests (Calgary, AB)](https://data.calgary.ca/Services-and-Amenities/311-Service-Requests/iahh-g8bj)
|
| 123 |
+
- [Cambridge Open Data - Commonwealth Connect Service Requests (Cambridge, MA)](https://data.cambridgema.gov/Public-Works/Commonwealth-Connect-Service-Requests/2z9k-mv9g)
|
| 124 |
+
- [NYC Open Data - NYC 311 Service Requests from 2020 to Present (New York)](https://data.cityofnewyork.us/Social-Services/311-Service-Requests-from-2020-to-Present/erm2-nwe9)
|
| 125 |
+
|
| 126 |
+
Prepared and distributed by [EDK](https://edk.earth).
|
| 127 |
+
|
| 128 |
+
## License
|
| 129 |
+
|
| 130 |
+
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.
|