File size: 8,942 Bytes
1060f62 eee6963 1060f62 eee6963 1060f62 caf2e4c 1060f62 ee55cd2 3b9b3ff ee55cd2 1060f62 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 | ---
tags:
- geospatial
- open-data
- tabular
- public-safety
- fire-response
- municipal-infrastructure
- emergency-services
- mapping
- parquet
- geojson
- csv
- openstreetmap
- year-2025
libraries:
- datasets
size_categories:
- 1M<n<10M
license: odbl
pretty_name: "Emergency Fire Hydrant Dataset - Global Fire Safety Infrastructure Data - EmbedEarth"
---
# Emergency Fire Hydrant Dataset - Global Fire Safety Infrastructure Data - EmbedEarth
This dataset maps emergency fire hydrant features from OpenStreetMap. A fire hydrant is a mapped connection to a water supply that can support firefighting operations. The records provide a geographic starting point for infrastructure analysis, emergency-service mapping, and data-quality work.
This release contains geolocated records from 2025 and is provided as a sample of a much larger dataset of mapped features.
Prepared and distributed by **[EmbedEarth](https://embed.earth)** from **[OpenStreetMap contributors](https://www.openstreetmap.org/copyright)**.
## Search millions more geographic features
This Hugging Face release is one downloadable dataset from the broader **[EmbedEarth](https://embed.earth)** geographic index. EmbedEarth provides developers and AI systems with tools for searching and working with geographic features, places, infrastructure, and other observations of the physical world.
### Build with EmbedEarth
* **[EmbedEarth](https://embed.earth)** — programmable infrastructure for Earth
* **[Geographic Feature List](https://www.embed.earth/catalog/features)** — browse geographic features available through EmbedEarth
* **[Developer Documentation](https://www.embed.earth/docs)** — APIs, SDKs, tools, guides, and examples
* **[Geographic Search SDK](https://www.embed.earth/docs/sdk/search)** — search geographic features and regions programmatically
* **API** — integrate geographic search and spatial data into applications
* **SDK** — build geographic capabilities directly into applications
* **CLI** — work with geographic data from the terminal
* **MCP** — connect geographic search and spatial tools to AI agents
## Search the physical world
The same geographic infrastructure used to create this dataset can support searches such as:
```text
fire hydrants near schools in Boston
hydrant coverage around downtown Toronto
emergency infrastructure in Los Angeles
fire hydrants near industrial areas in Houston
```
## Dataset overview
This dataset focuses on **emergency fire hydrants** represented in OpenStreetMap. Each record is a geolocated map feature with source attribution and, where available, additional tags such as names, addresses, references, operators, websites, access details, and feature-specific values.
Mapped emergency fire hydrants and related water-access points used by fire services, where those features are recorded in openstreetmap.
## Use cases
### Public-safety mapping
Map fire-hydrant coverage alongside roads, buildings, fire stations, and other emergency infrastructure.
### Emergency-response analysis
Explore proximity, access, and network relationships relevant to response planning.
### Municipal asset research
Compare mapped hydrant attributes and coverage across neighborhoods or service areas.
### Infrastructure risk analysis
Combine hydrant locations with buildings, parcels, hazards, and population data.
### OpenStreetMap quality checks
Review completeness and consistency of fire-hydrant tags and supporting attributes.
## Schema
The downloadable Parquet and CSV files use a normalized schema. Source-specific attributes are preserved inside the JSON-encoded `properties` field rather than expanded into separate top-level columns. GeoJSON exposes the same record attributes alongside its geometry.
| Column | Type | Description |
| --- | --- | --- |
| `id` | string | Stable identifier for the exported record. |
| `sample` | boolean | Whether this record was selected for the optional image archive sample. |
| `latitude` | float64 | Latitude in decimal degrees using WGS 84 when a valid location is available. |
| `longitude` | float64 | Longitude in decimal degrees using WGS 84 when a valid location is available. |
| `geometry_wkb` | binary | The record geometry encoded as Well-Known Binary for spatial workflows. |
| `media_url` | string | URL for associated imagery or other visual media when available. |
| `attribution` | string | Attribution information carried into the exported record. |
| `source` | string | Source or provider associated with the observation. |
| `properties` | string | JSON-encoded object containing source-specific OpenStreetMap attributes. |
### Source-specific properties
The `properties` field preserves additional OpenStreetMap tags associated with each feature. Exact keys vary by record and region; common examples include:
| Property | Description |
| --- | --- |
| `osm_id` | OpenStreetMap object identifier when supplied. |
| `fire_hydrant:type` | Hydrant type when mapped. |
| `fire_hydrant:position` | Position or placement information when supplied. |
| `fire_hydrant:diameter / water_source` | Hydrant or water-source attributes when mapped. |
| `operator / ref` | Responsible organization or asset reference when available. |
| `address` | Address or location text when supplied. |
Not every property is populated for every record.
## Download
The dataset is available in Parquet, GeoJSON, and CSV formats:
* [Parquet](https://huggingface.co/datasets/EmbedEarth/emergency-fire-hydrant/resolve/main/data.parquet)
* [GeoJSON](https://huggingface.co/datasets/EmbedEarth/emergency-fire-hydrant/resolve/main/data.geojson)
* [CSV](https://huggingface.co/datasets/EmbedEarth/emergency-fire-hydrant/resolve/main/data.csv)
**Parquet** is recommended for analytics, Python workflows, DuckDB, and large-scale processing. **GeoJSON** is useful for GIS software and web maps. **CSV** is convenient for tabular analysis and interoperability.
## Data sources and attribution
This dataset was prepared and distributed by **[EmbedEarth](https://embed.earth)** from data contributed to **[OpenStreetMap](https://www.openstreetmap.org/copyright)**.
OpenStreetMap data is available under the **[Open Database License (ODbL) 1.0](https://opendatacommons.org/licenses/odbl/1.0/)**. When using or redistributing the data, retain the OpenStreetMap attribution and follow the applicable ODbL requirements. Record-level media or third-party links may have additional terms set by their original providers.
Suggested attribution:
> Contains information from OpenStreetMap, which is made available under the Open Database License (ODbL). https://www.openstreetmap.org/copyright
## Methodology and limitations
Records were exported from an OpenStreetMap snapshot for 2025. A mapped hydrant is not a guarantee that the asset is accessible, operational, supplied with water, or suitable for a particular response. Field verification and local authority data are required for operational decisions.
OpenStreetMap coverage and tagging vary by place and contributor. Geographic absence should not be interpreted as real-world absence, and mapped presence should not be treated as an independent inspection or operational certification.
<!-- embedearth-tools:start -->
## Build with EmbedEarth
- [Geographic Feature List](https://embed.earth/catalog/features) — browse geographic features available through EmbedEarth
- [EmbedEarth](https://embed.earth) — programmable infrastructure for Earth
- [Developer Documentation](https://embed.earth/docs) — APIs, tools, guides, and examples
- [GitHub — EmbedEarth/e2](https://github.com/EmbedEarth/e2) — open-source code, issues, and contributions
- [Geographic Search SDK](https://www.npmjs.com/package/@embedearth/sdk) — search geographic features and regions programmatically
- [API](https://embed.earth/docs) — integrate geographic search and spatial data into applications
- [SDK](https://www.npmjs.com/package/@embedearth/sdk) — build geographic capabilities directly into applications
- [CLI](https://www.npmjs.com/package/@embedearth/cli) — work with geographic search and spatial data from the terminal
- [MCP](https://www.npmjs.com/package/@embedearth/mcp) — connect geographic search and spatial tools to AI agents
Install from npm:
```bash
npm i @embedearth/cli
npm i @embedearth/sdk
npm i @embedearth/mcp
```
<!-- embedearth-tools:end -->
## License
The OpenStreetMap-derived database in this repository is made available under the **Open Database License (ODbL) 1.0**. See the [ODbL license text](https://opendatacommons.org/licenses/odbl/1.0/) and [OpenStreetMap attribution guidance](https://www.openstreetmap.org/copyright).
EmbedEarth-created explanatory text and metadata are provided to help users understand the release. Users are responsible for complying with the terms applying to OpenStreetMap data and any underlying third-party media or links.
|