The layers most map products end up needing.
Parcels tell you who owns the ground. Flood, wetlands and public lands tell you what can be done with it. Assembling those from source is months of pipeline work — they are all already tiled and serving here.
Every layer, and where it comes from
Property parcels
251 GBParcel boundaries for all 50 states and DC, assembled from state cadastral programmes and individual county assessors, with the attribute fields each source publishes.
State + county cadastral offices
FEMA flood zones
51 archivesNational Flood Hazard Layer zones for every state and DC, classified into high, moderate and minimal risk and filterable by the raw FEMA zone code.
FEMA NFHL
Wetlands
9.3 GBNational Wetlands Inventory polygons — the layer that decides whether a site is buildable long before anyone visits it.
US Fish & Wildlife Service
Basemap
133 GBA full planet basemap with roads, buildings, land use, water and labels, styleable in light, dark or your own palette.
Protomaps · OpenStreetMap
Terrain & elevation
47 GBElevation tiles for hillshade, 3D terrain exaggeration and slope analysis.
Public elevation models
Public & federal lands
BLM · USFSBureau of Land Management parcels, National Forest boundaries, designated wilderness and PAD-US protected areas.
BLM · USFS · PAD-US
PLSS survey grid
4.5 GBPublic Land Survey System townships, ranges and sections — the grid that legal descriptions in most of the country are written against.
BLM cadastral survey
Hydrography
NHDNational Hydrography Dataset rivers, streams and water bodies.
USGS
Wildfire perimeters
1.3 GBHistorical fire perimeters, for risk scoring and insurance-adjacent workflows.
Interagency fire perimeter data
Critical facilities
HIFLDHospitals, schools, fire stations and other infrastructure points from the HIFLD open catalogue.
HIFLD
Source data is published by the agencies named above; we handle the acquisition, reprojection, tiling and refresh.
Architecture chosen so the bill stays flat
The pricing model on this site is only possible because of how the tiles are stored. These two things are the same decision.
PMTiles, not a tile server
Each layer is one archive read with HTTP range requests. There is no tile server to scale, no cache to warm and no cold-start on an unusual zoom level — the client fetches exactly the byte ranges it needs.
Signed, short-lived tile access
Tiles are served through an edge gateway that mints short-lived signed tokens per session and enforces a per-client byte budget. The underlying bucket is private and not reachable directly.
Style it like any vector source
These are ordinary Mapbox Vector Tiles. Every MapLibre paint and layout property, every filter expression and every feature-state interaction works exactly as documented.
Offline packages
Because an archive is a single file, a bounded region can be handed over for use inside a field application with no connectivity at all.