Get fire hydrant location/attribute GIS data for flow-test planning or system design in a specific city
domain: opendata.dc.gov · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check whether the target city publishes a hydrant layer on its own open-data/GIS portal — DC (opendata.dc.gov/datasets/fire-hydrants), Boise (opendata.cityofboise.org/datasets/fire-hydrants), and Spokane (data-spokane.opendata.arcgis.com) are confirmed live examples as of mid-2026
Prefer the ArcGIS REST/GeoService endpoint over a one-time CSV export if you need to keep the layer current in your own GIS
Verify field definitions (owner, size, color-code/flow class) per city, since hydrant attribute schemas are not standardized nationally
Confirm the data's last-updated date before using it for design work — hydrant layers are maintained by water utilities on inconsistent cycles
Known gotchas
Hydrant open-data coverage is patchy and city-by-city; there is no single national hydrant dataset, so each jurisdiction must be checked individually
Attribute completeness (especially flow/color-class data) varies widely — don't assume a published layer includes flow-test results
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?