Atlanta’s LandUsePlanning map is a layered index, not one verdict: begin with the district, then preserve every overlay, corridor, moratorium, historic, and rezoning record touching the parcel. Map sheet 14F-011 and the linked ordinance show which displayed layers have legal effect. It is not an approval.
Last checked: August 7, 2026.
Begin the map-sheet-to-ordinance trail at Atlanta Department of City Planning maps and GIS, which supplies agency guidance and viewer entry. Cross-check the selected geometry through Atlanta GIS portal, the route used for address, parcel, and map lookup. Before copying Zoning District (layer 0), verify City-owned gis.atlantaga.gov service and Copyright Text: City of Atlanta – DCP; those markers keep the LandUsePlanning stack tied to the intended jurisdiction and record period.
Layer 0 is only the floor of the LandUsePlanning stack
Atlanta's LandUsePlanning service is a stack of separate questions, not a single zoning answer. Zoning District (layer 0) supplies the mapped base district, while Zoning Overlay (layer 1) and Inclusionary Zoning (layer 2) add coverage that must be researched independently. Zoning Map Index (layer 3) only identifies the relevant official map sheet. BeltLine TCU Corridor (layer 4), Building Moratorium (layer 5), and Historic District (layer 6) each open a different regulatory path; none is a substitute for the district article. Rezoning Cases (layer 10) adds case history, but a case polygon does not prove that a district change became effective. A useful Atlanta worksheet therefore keeps all eight layer results in separate columns and connects each positive intersection to its own ordinance, map sheet, case outcome, or preservation review record.
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| Zoning District (layer 0) returns layer ID 0 | Compare with Zoning Overlay (layer 1), which publishes supplemental zoning-overlay geography | Stop the map-sheet-to-ordinance trail if Zoning Overlay (layer 1) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Use its symbol to locate the district article; do not infer an overlay is absent. Then test whether Zoning Overlay (layer 1) changes that route. |
| Zoning Overlay (layer 1) returns layer ID 1 | Compare with Inclusionary Zoning (layer 2), which shows mapped inclusionary-zoning coverage | Stop the map-sheet-to-ordinance trail if Inclusionary Zoning (layer 2) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Record the overlay name and open its controlling zoning provision with the base district. Then test whether Inclusionary Zoning (layer 2) changes that route. |
| Inclusionary Zoning (layer 2) returns layer ID 2 | Compare with Zoning Map Index (layer 3), which identifies the official map sheet covering the property | Stop the map-sheet-to-ordinance trail if Zoning Map Index (layer 3) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Check the applicable inclusionary-zoning ordinance and effective geography. Then test whether Zoning Map Index (layer 3) changes that route. |
| Zoning Map Index (layer 3) returns layer ID 3 | Compare with BeltLine TCU Corridor (layer 4), which shows the mapped BeltLine TCU corridor | Stop the map-sheet-to-ordinance trail if BeltLine TCU Corridor (layer 4) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: The index is a navigation record, not the district designation. Then test whether BeltLine TCU Corridor (layer 4) changes that route. |
| BeltLine TCU Corridor (layer 4) returns layer ID 4 | Compare with Building Moratorium (layer 5), which shows mapped building-moratorium geography | Stop the map-sheet-to-ordinance trail if Building Moratorium (layer 5) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Treat corridor coverage as an additional research path, not a replacement zoning code. Then test whether Building Moratorium (layer 5) changes that route. |
| Building Moratorium (layer 5) returns layer ID 5 | Compare with Historic District (layer 6), which shows mapped historic-district coverage | Stop the map-sheet-to-ordinance trail if Historic District (layer 6) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Verify the moratorium instrument, scope, and active dates before stating an effect. Then test whether Historic District (layer 6) changes that route. |
| Historic District (layer 6) returns layer ID 6 | Compare with Rezoning Cases (layer 10), which locates rezoning case records | Stop the map-sheet-to-ordinance trail if Rezoning Cases (layer 10) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Check preservation review independently from base zoning. Then test whether Rezoning Cases (layer 10) changes that route. |
| Rezoning Cases (layer 10) returns layer ID 10 | Compare with Zoning District (layer 0), which returns the mapped base district | Stop the map-sheet-to-ordinance trail if Zoning District (layer 0) is missing, dated differently, or points to another record. | Continue through the LandUsePlanning stack: Confirm final action and effective ordinance; a case polygon is not itself a changed district. Then test whether Zoning District (layer 0) changes that route. |
Map sheet 14F-011 fixes the location before overlays enter
The LandUsePlanning stack table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is Zoning District (layer 0), which may appear as layer ID 0; from there, Use its symbol to locate the district article; do not infer an overlay is absent. A blank in the map-sheet-to-ordinance trail stays visible so another reader can distinguish an empty official return from an unexamined field.
| Local field, layer, or record | What it does | Displayed value or scope | Next code or record check | Official page |
|---|---|---|---|---|
| Zoning District (layer 0) layer | returns the mapped base district | layer ID 0 | Use its symbol to locate the district article; do not infer an overlay is absent. | Open exact record |
| Zoning Overlay (layer 1) layer | publishes supplemental zoning-overlay geography | layer ID 1 | Record the overlay name and open its controlling zoning provision with the base district. | Open exact record |
| Inclusionary Zoning (layer 2) layer | shows mapped inclusionary-zoning coverage | layer ID 2 | Check the applicable inclusionary-zoning ordinance and effective geography. | Open exact record |
| Zoning Map Index (layer 3) layer | identifies the official map sheet covering the property | layer ID 3 | The index is a navigation record, not the district designation. | Open exact record |
| BeltLine TCU Corridor (layer 4) layer | shows the mapped BeltLine TCU corridor | layer ID 4 | Treat corridor coverage as an additional research path, not a replacement zoning code. | Open exact record |
| Building Moratorium (layer 5) layer | shows mapped building-moratorium geography | layer ID 5 | Verify the moratorium instrument, scope, and active dates before stating an effect. | Open exact record |
| Historic District (layer 6) layer | shows mapped historic-district coverage | layer ID 6 | Check preservation review independently from base zoning. | Open exact record |
| Rezoning Cases (layer 10) layer | locates rezoning case records | layer ID 10 | Confirm final action and effective ordinance; a case polygon is not itself a changed district. | Open exact record |
Move from DCP parcel evidence to the BeltLine and historic layers
- Open the LandUsePlanning stack; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the map-sheet-to-ordinance trail by copying Zoning District (layer 0) exactly as returned, including layer ID 0.
- Keep Zoning Overlay (layer 1) in a second LandUsePlanning stack worksheet field because it publishes supplemental zoning-overlay geography.
- Test Inclusionary Zoning (layer 2) independently, then mark its value, service layer, or documented blank in the map-sheet-to-ordinance trail.
- Give Zoning Map Index (layer 3) and every later item a separate row; never compress history, plans, and overlays into the LandUsePlanning stack result.
- Attach the LandUsePlanning stack lookup time to Zoning District (layer 0), while preserving this separate currency clue: Record the GIS lookup date, map-index sheet date, and ordinance effective date separately; the portal refresh and the governing ordinance can change on different schedules.
- If Zoning District (layer 0) and Zoning Overlay (layer 1) conflict, send the map-sheet-to-ordinance trail to Atlanta Department of City Planning maps and GIS and ask which intersecting layer supplies the rule that must be opened.
The LandUsePlanning stack worksheet is complete only when another reader can reproduce the map-sheet-to-ordinance trail from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record which intersecting layer supplies the rule that must be opened as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: Record the GIS lookup date, map-index sheet date, and ordinance effective date separately; the portal refresh and the governing ordinance can change on different schedules.
A parcel where inclusionary zoning meets a corridor overlay
Consider a hypothetical Atlanta parcel for which Zoning District returns layer ID 0 and the same geometry also intersects Zoning Overlay layer ID 1 and BeltLine TCU Corridor layer ID 4. The first record identifies the base-district research path; it does not make the other two records disappear. The researcher copies the overlay name, opens the controlling overlay provision, and treats the BeltLine corridor as an additional inquiry. Zoning Map Index layer ID 3 is then used to identify the official map sheet, not to fill the district column. If Rezoning Cases layer ID 10 also intersects, the case is retrieved and its final action and effective ordinance are checked. The hypothetical ends with three unresolved legal questions, not one favorable map color: what the base article permits, what the overlay changes, and whether the corridor or case record adds a current constraint.
Layer 10 can preserve a rezoning trail without changing the base result
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | A parcel intersects Zoning Overlay or BeltLine TCU Corridor, but only Zoning District layer 0 is recorded. | Preserve Inclusionary Zoning (layer 2), the selected geometry, and both timestamps from the LandUsePlanning stack check. | Use Atlanta Department of City Planning maps and GIS to settle which intersecting layer supplies the rule that must be opened; then Check the applicable inclusionary-zoning ordinance and effective geography. |
| Scenario 2 | A Zoning Map Index sheet number or Rezoning Cases polygon is misread as the property's current zoning classification. | Preserve Zoning Map Index (layer 3), the selected geometry, and both timestamps from the LandUsePlanning stack check. | Use Atlanta Department of City Planning maps and GIS to settle which intersecting layer supplies the rule that must be opened; then The index is a navigation record, not the district designation. |
Two Atlanta errors require different repairs. If only Zoning District layer 0 was saved even though the parcel intersects Zoning Overlay or BeltLine TCU Corridor, rerun the same parcel geometry with layers 1 and 4 visible and preserve each returned name. Then open the overlay provision and corridor record beside the base article. If a Zoning Map Index sheet number or a Rezoning Cases polygon was entered as the current district, move that value to a navigation or history column and restore the actual layer 0 designation. The narrow agency question should identify the parcel, map sheet, layer names, and lookup date: Which district and supplemental controls are legally effective for this parcel, and did the cited rezoning case produce an effective ordinance? That question exposes the exact conflict without asking the City to endorse an undefined project or treating a map intersection as approval.
GIS refresh, map-index sheet, and ordinance each keep a different clock
Atlanta, Georgia date check: Record the GIS lookup date, map-index sheet date, and ordinance effective date separately; the portal refresh and the governing ordinance can change on different schedules.
Atlanta publishes a useful ownership chain for this work: the Department of City Planning maps page, the City GIS portal, the LandUsePlanning map service, and an official zoning map sheet. The service's City of Atlanta DCP attribution establishes jurisdictional scope, while the numbered sublayers establish what each map result represents. Currency still requires three clocks. Preserve the GIS query date, the date printed or associated with the Zoning Map Index sheet, and the effective date of the ordinance or case action used for interpretation. A portal refresh can occur without changing the governing text, and an ordinance can become effective before every public display is synchronized. Building Moratorium and Rezoning Cases results especially require their own active dates and final-action checks. The defensible statement is which source said what on which date, not that the newest-looking screen automatically controls.
Divide the proof between DCP maps, the GIS portal, and the map sheet
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Atlanta Department of City Planning maps and GIS | agency guidance and viewer entry | City planning page routes users to official maps and GIS |
| Atlanta GIS portal | address, parcel, and map lookup | City-owned atlantaga.gov GIS host |
| Atlanta Land Use Planning map service | exact operational layer inventory | City of Atlanta DCP copyright and zoning/land-use subject |
| Atlanta official zoning map sheet 14F-011 | map-sheet legend and local overlay context | City GIS PDF legend includes SPI and BeltLine overlay notation |
How should Zoning District (layer 0) be checked in Atlanta, Georgia?
Open the official Zoning District (layer 0) record and capture the value inside the LandUsePlanning stack. That record shows how Zoning District (layer 0) returns the mapped base district; one displayed form is layer ID 0. Place the copied value in the map-sheet-to-ordinance trail, then follow its separate rule route: Use its symbol to locate the district article; do not infer an overlay is absent.
How should Zoning Overlay (layer 1) be checked in Atlanta, Georgia?
Open the official Zoning Overlay (layer 1) record and capture the value inside the LandUsePlanning stack. That record shows how Zoning Overlay (layer 1) publishes supplemental zoning-overlay geography; one displayed form is layer ID 1. Place the copied value in the map-sheet-to-ordinance trail, then follow its separate rule route: Record the overlay name and open its controlling zoning provision with the base district.
How should Inclusionary Zoning (layer 2) be checked in Atlanta, Georgia?
Open the official Inclusionary Zoning (layer 2) record and capture the value inside the LandUsePlanning stack. That record shows how Inclusionary Zoning (layer 2) shows mapped inclusionary-zoning coverage; one displayed form is layer ID 2. Place the copied value in the map-sheet-to-ordinance trail, then follow its separate rule route: Check the applicable inclusionary-zoning ordinance and effective geography.
What Planning needs to untangle a stacked Atlanta result
- Selected parcel key, geometry, and responsible jurisdiction
- Every returned value from the local field table
- Page titles, URLs, lookup times, and update clues
- Opened code, plan, case, ordinance, or metadata records
- Unresolved blanks, boundary splits, dates, and competing outputs
- Proposed activity stated in code-relevant facts
- Agency contact, narrow question, reply date, and limits
The LandUsePlanning stack does not decide title, survey boundaries, private restrictions, vested rights, building-code compliance, utilities, licensing, or permit issuance. Request a written response when the map-sheet-to-ordinance trail leaves competing official results or when substantial reliance is planned. A useful request to Atlanta Department of City Planning maps and GIS identifies the parcel, quotes Zoning District (layer 0) and Zoning Overlay (layer 1), gives their source dates, and asks which intersecting layer supplies the rule that must be opened.
Use atlanta zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the map-sheet-to-ordinance trail. The LandUsePlanning stack evidence linked for Zoning District (layer 0) and Zoning Overlay (layer 1) remains the local starting point.
Reviewed August 7, 2026. Recheck the LandUsePlanning stack, its cited ordinance, and the agency procedure before relying on the saved worksheet.