United States land use plans data sources

Where can I get the current land-use and zoning plans of the United States as geometry, with land classification and the planning instrument they belong to?

Answer

No single official nationwide zoning dataset was found: zoning is adopted locally. Two tested cities publish open polygon services: Denver (3,934 polygons; ordinance number/year and code version per polygon) and Austin (22,503 polygons; ordinance boundaries in a separate layer, linked only by spatial overlay). Nationwide coverage appears only as a paid commercial layer (Regrid) or a nonprofit viewer (National Zoning Atlas); neither was verified here. Zone codes are not comparable between places; future-land-use plans are separate layers.

Official data
Partial coverage
Non official data
Partial coverage

Local search terms

Published
2026-11-20
Research reviewed
2026-11-20
Access checked
2026-11-20

Requested attributes

AttributeCoverageSourcesScope and limitations
Current plan geometry plan_geometryPartially covered
  • denver-ccd-zoning
  • austin-zoning-polygons
Open polygon APIs tested for Denver (3,934) and Austin (22,503); no national official geometry found; Regrid layer is paid.

Not checked: Only two jurisdictions were tested. Next step: sample other jurisdictions' GIS portals; check NZA terms and Regrid sample files. Regrid's nationwide zoning layer is sold through sales (restricted).

Land classification land_classificationPartially covered
  • denver-ccd-zoning
  • austin-zoning-polygons
Denver ZONE_DISTRICT/ZONE_DESCRIPTION/ZONE_DIST_TYPE and Austin ZONING_ZTYPE/ZONING_BASE; codes are local and need each city's code.

Not checked: Classification vocabularies were read only for Denver and Austin; no standard national scheme was verified (Regrid sells a standardized layer, not inspected).

Planning instrument planning_instrumentPartially covered
  • denver-ccd-zoning
  • austin-zoning-ordinance-boundaries
Denver: ORD_NUM/ORD_YEAR/ZCODE_VERSION per polygon. Austin: ordinance polygons with EDIMS PDF links, overlapping and incomplete before 2001.

Not checked: Denver ordinance PDFs and the Denver Municipal Code text were not opened beyond the zoning code page; Austin Land Development Code (Municode) returned 403, so code definitions were not read.

Main caveats

Sources

CCD Zoning (Denver zoning boundaries, FeatureServer layer 27)

Source id
denver-ccd-zoning
Publisher
City and County of Denver, Community Planning and Development / Geospatial Denver
Official
Yes
Landing url
https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/ArcGIS/rest/services/CCD_Zoning/FeatureServer
Data url
https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/ArcGIS/rest/services/CCD_Zoning/FeatureServer/27/query
Access
api
Format
ArcGIS REST FeatureServer (query JSON/GeoJSON; service lists csv, shapefile, geoPackage, filegdb, kml, excel exports)
License
Custom terms in the ArcGIS item: ACCESS CONSTRAINTS: None; provided AS IS; NOT FOR ENGINEERING PURPOSES
Language
en
Has coordinates
Yes
Location precision
exact
Summary
Denver publishes its zoning polygons as an open ArcGIS service: district, type, ordinance number/year, code version and PUD document name.
Coverage note
Denver only; 3,934 polygons, 2,779 under the 2010 code and 1,155 under Former Chapter 59.
Date of data
2024-03-12 (service data last edit)
Caveats
  • Informational, not for engineering; confirm rezonings after 2024-03-12 with the city.
  • Read ZCODE_VERSION before interpreting district codes.
Test
Tested on
2026-11-20
Method
api_query
Http status
200
Problems
  • data.denvergov.org timed out after 30 s from this host.
  • denvergov.org/opendata redirects to a JavaScript-rendered ArcGIS Hub page; no landing metadata (frequency, licence name) was readable.
  • size_bytes is the GeoJSON page of 1,934 features at resultOffset=2000 (WGS84, all fields).
Example
Example request
curl -G 'https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/ArcGIS/rest/services/CCD_Zoning/FeatureServer/27/query' --data-urlencode 'geometry=-104.9847,39.7392' --data-urlencode 'geometryType=esriGeometryPoint' --data-urlencode 'inSR=4326' --data-urlencode 'spatialRel=esriSpatialRelIntersects' --data-urlencode 'outFields=ZONE_DISTRICT,ZONE_DESCRIPTION,ZONE_DIST_TYPE,ORD_NUM,ORD_YEAR,ZCODE_VERSION' --data-urlencode 'returnGeometry=false' --data-urlencode 'f=json'
Example result
One feature: ZONE_DISTRICT D-CV, ZONE_DESCRIPTION 'Downtown - Civic (D-CV)', ZONE_DIST_TYPE 'Commercial Mixed Use', ORD_NUM 333, ORD_YEAR 2010, ZCODE_VERSION 2010 (queried 2026-11-20).
Members summary
Not a grouped source

Zoning (Large Map Scale) - City of Austin

Source id
austin-zoning-polygons
Publisher
City of Austin, Geospatial Services (Planning Cadastre)
Official
Yes
Landing url
https://services.arcgis.com/0L95CJ0VTaxqcmED/ArcGIS/rest/services/PLANNINGCADASTRE_zoning_large_map_scale/FeatureServer
Data url
https://services.arcgis.com/0L95CJ0VTaxqcmED/ArcGIS/rest/services/PLANNINGCADASTRE_zoning_large_map_scale/FeatureServer/0/query
Access
api
Format
ArcGIS REST FeatureServer (query JSON/GeoJSON; exports: csv, shapefile, geoPackage, filegdb, kml, excel)
License
Unknown
Language
en
Has coordinates
Yes
Location precision
exact
Summary
Austin's zoning polygons are an open ArcGIS service edited through 2026-11-20, with a full district string and a base district.
Coverage note
Austin area; 22,503 polygons. No ordinance key in the layer.
Date of data
2026-11-20 (service data last edit)
Caveats
  • Informational; the city directs users to its Property Profile map for determinations.
  • Licence not named; attribution requested.
Test
Tested on
2026-11-20
Method
api_query
Http status
200
Problems
  • size_bytes is the first GeoJSON page (2,000 features, four fields, WGS84); the full set needs 12 pages.
  • A first-vertex-average point test fell outside its polygon (0 hits); an interior point was used for the documented example.
Example
Example request
curl -G 'https://services.arcgis.com/0L95CJ0VTaxqcmED/ArcGIS/rest/services/PLANNINGCADASTRE_zoning_large_map_scale/FeatureServer/0/query' --data-urlencode 'geometry=-97.718057,30.327897' --data-urlencode 'geometryType=esriGeometryPoint' --data-urlencode 'inSR=4326' --data-urlencode 'spatialRel=esriSpatialRelIntersects' --data-urlencode 'outFields=ZONING_ID,ZONING_ZTYPE,ZONING_BASE' --data-urlencode 'returnGeometry=false' --data-urlencode 'f=json'
Example result
One feature: ZONING_ID 135025, ZONING_ZTYPE 'SF-3-NP', ZONING_BASE 'SF' (queried 2026-11-20).
Members summary
Not a grouped source

Zoning Ordinance boundaries - City of Austin

Source id
austin-zoning-ordinance-boundaries
Publisher
City of Austin, Geospatial Services (Planning Cadastre)
Official
Yes
Landing url
https://services.arcgis.com/0L95CJ0VTaxqcmED/ArcGIS/rest/services/PLANNINGCADASTRE_zoning_ordinance/FeatureServer
Data url
https://services.arcgis.com/0L95CJ0VTaxqcmED/ArcGIS/rest/services/PLANNINGCADASTRE_zoning_ordinance/FeatureServer/0/query
Access
api
Format
ArcGIS REST FeatureServer (query JSON/GeoJSON)
License
Unknown
Language
en
Has coordinates
Yes
Location precision
exact
Summary
Austin publishes ordinance boundaries with ordinance and case numbers and a link to each ordinance PDF; they overlap zoning polygons spatially.
Coverage note
Austin; 10,723 polygons for 5,768 ordinance numbers; older ordinances less likely included.
Date of data
2026-11-20 (service data last edit)
Caveats
  • Overlay link only; a citywide 1999 code ordinance shows up beside the case-specific one.
  • Entered day-forward since 2001.
Test
Tested on
2026-11-20
Method
api_query
Http status
200
Problems
  • size_bytes is the first GeoJSON page (2,000 features, four attributes).
  • Both linked EDIMS PDFs opened (824,125 and 3,188,168 bytes) and their first page was read.
  • EDIMS links are plain http and redirect to services.austintexas.gov.
Example
Example request
curl -G 'https://services.arcgis.com/0L95CJ0VTaxqcmED/ArcGIS/rest/services/PLANNINGCADASTRE_zoning_ordinance/FeatureServer/0/query' --data-urlencode 'geometry=-97.718057,30.327897' --data-urlencode 'geometryType=esriGeometryPoint' --data-urlencode 'inSR=4326' --data-urlencode 'spatialRel=esriSpatialRelIntersects' --data-urlencode 'outFields=ZONING_ORDINANCE_NUMBER,CASE_NUMBER,ZONING_ORDINANCE_ZTYPE,ZONING_ORDINANCE_PATH' --data-urlencode 'returnGeometry=false' --data-urlencode 'f=json'
Example result
Two ordinances: 20040513-33B (case C14-04-0012.002, type NP; PDF = rezoning to add a neighborhood plan combining district) and 19990225-070b (the 1999 ordinance replacing Title 13 with Title 25).
Members summary
Not a grouped source

National Zoning Atlas

Source id
national-zoning-atlas
Publisher
Land Use Atlas, Inc. (National Zoning Atlas)
Official
No
Landing url
https://www.zoningatlas.org/atlas
Data url
Not stated
Access
web_viewer_only
Format
Web atlas (viewer); downloads not verified
License
Unknown
Language
en
Has coordinates
Not stated
Location precision
Not stated
Summary
A nonprofit atlas of zoning conditions across US jurisdictions; only the web viewer was checked.
Coverage note
Claims 33,000+ jurisdictions; state coverage and download terms not verified.
Date of data
Not stated
Caveats
  • Download of geometry not demonstrated.
  • Not an official source.
Test
Tested on
2026-11-20
Method
page_only
Http status
200
Problems
  • Only HTML pages were read; no data file was downloaded.
  • The S3 data bucket (statezoningatlasdata.s3.amazonaws.com) returned NoSuchBucket (HTTP 404).
  • mercatus.org list of state/regional atlas datasets returned HTTP 403 (Cloudflare block).
Example
Complete procedure available in the full detail
Members summary
Not a grouped source

Regrid Standardized Zoning (add-on to parcels)

Source id
regrid-standardized-zoning
Publisher
Regrid
Official
No
Landing url
https://regrid.com/zoning
Data url
Not stated
Access
paid
Format
Commercial bulk files / feature service / API (per Regrid page)
License
Unknown
Language
en
Has coordinates
Not stated
Location precision
Not stated
Summary
A paid commercial layer that standardizes local zoning across thousands of municipalities, attached to parcels.
Coverage note
Coverage and price not verified; sold through enterprise sales.
Date of data
Not stated
Caveats
  • Paid; no sample inspected.
  • Vendor-standardized categories.
Test
Tested on
2026-11-20
Method
page_only
Http status
200
Problems
  • Product page only; no data, sample or price list was accessed.
Example
Complete procedure available in the full detail
Members summary
Not a grouped source

Additional sources in the detail: 0. Read the full detail; locate each source by its source_id.

Document access

Summary
Adopted zoning ordinances and the code text are PDFs or code-hosting sites; the GIS layers only reference them.

Confidence

Confidence
medium
Confidence reason
Denver and Austin services were queried live; the national picture rests on two web pages (NZA, Regrid) and failed attempts to read federal and aggregator catalogues.

Research provenance

Pass count
1
Models
  • Claude Sonnet 5.5 (claude-sonnet-5-5)
Minutes estimate
Not stated
Pages opened
63
Passes
  • Pass
    1
    Date
    2026-11-20
    Model
    Claude Sonnet 5.5 (claude-sonnet-5-5)
Note
Minutes are researcher estimates. Counts describe documented passes, not publication approval. Missing history or effort is not reconstructed.

Record metadata

Schema version
1.0
Country
us
Country name
United States
Topic
land-use-plans
Territory
us
Territory level
country
Parent url
No parent territory
Html url
https://georutter.org/us/land-use-plans/