Overview
Code type
euclidean
Naming convention
mixed
R-number residentials use min-lot-in-thousand-sf convention (R40 ~40k sf ... R6 ~6k sf). Mixed-use (MRO/MU/MUG/MUL/MPO/GO/OR/SP) and commercial (CS/CG/PGC/PNC/CSL) ladders are named by function, not ordinal. MUG/MUL/CSL are pre-7/7/98 legacy-only districts. ZoCo rewrite in draft would replace this taxonomy; not adopted. | naming_convention_raw=lot-size-residential-ordinal ; sub_flags_raw=[suburban-sunbelt, pdf-only-canonical] ; narrative_ref=narratives/gallatin-tn/c6490014-b030-4b97-8f92-ab9ceabed1ca.json
Worth knowing
- ZoCo rewrite in flight (not adopted) — Comprehensive zoning code rewrite by TPUDC in draft as of April 2026; circulating for Planning Commission review with public comment via zoco@gallatintn.gov. Legacy Articles 1-15 remain in force. Adoption would trigger a full re-research cycle. — [gallatintn.gov/2286]
- R-number = min-lot-in-thousand-sf convention — R40/R20/R15/R10/R8/R6 use the standard min-lot-in-thousand-sf naming (R40 ~40k sf; R6 ~6k sf). NOT inverse (unlike Grand Prairie). Shared with many TN suburbs.
- Pre-7/7/98 legacy districts (MUG, MUL, CSL) — Three districts (MUG Mixed-Use General, MUL Mixed-Use Limited, CSL Commercial Services Limited) are explicitly retained for parcels mapped pre-7/7/98 only — effectively frozen categories not applied to new rezonings. Interact with TCA §13-7-208 nonconforming protection. — [Zoning-Ord §7, §8]
+ 5 more in Quirks & notes
Districts
mu 8res_sf 6com 5ind 3res_mf 1res_spec 1
| Code | Name | Category | Min lot | Height | Coverage | FAR | Du/ac | Parking | Setbacks F/S/R |
|---|---|---|---|---|---|---|---|---|---|
| A | Agricultural Residential | res_sf | — | 35 ft | — | — | — | — | — / — / — |
| R40 | Low Density Residential (~40k sf) | res_sf | 40,000 sf | 35 ft | — | — | — | — | 25 / 10 / 25 |
| R20 | Low Density Residential (~20k sf) | res_sf | 20,000 sf | 35 ft | — | — | — | — | — / — / — |
| R15 | Medium Density Residential (~15k sf) | res_sf | 15,000 sf | 35 ft | — | — | — | — | — / — / — |
| R10 | Medium Density Residential (~10k sf) | res_sf | 10,000 sf | 35 ft | — | — | — | — | — / — / — |
| R8 | Medium Density Residential (~8k sf) | res_sf | 8,000 sf | 35 ft | — | — | — | — | — / — / — |
| R6 | High Density Residential (~6k sf) | res_mf | 6,000 sf | 35 ft | — | — | — | — | — / — / — |
| PRD | Planned Residential Development | res_spec | — | — | — | — | — | — | — / — / — |
| MRO | Mixed Residential & Office | mu | — | 45 ft | — | — | — | — | — / — / — |
| MU | Mixed-Use | mu | — | 55 ft | — | — | — | — | — / — / — |
| MUG | Mixed-Use General (legacy) | mu | — | — | — | — | — | — | — / — / — |
| MUL | Mixed-Use Limited (legacy) | mu | — | — | — | — | — | — | — / — / — |
| MPO | Medical-Professional Office | mu | — | 45 ft | — | — | — | — | — / — / — |
| GO | General Office | mu | — | 45 ft | — | — | — | — | — / — / — |
| OR | Office Residential | mu | — | — | — | — | — | — | — / — / — |
| SP | Specific Plan | mu | — | — | — | — | — | — | — / — / — |
| CS | Commercial Services | com | — | 45 ft | — | — | — | — | — / — / — |
| CG | Commercial General | com | — | 55 ft | — | — | — | — | — / — / — |
| PGC | Planned General Commercial | com | — | — | — | — | — | — | — / — / — |
| PNC | Planned Neighborhood Commercial | com | — | — | — | — | — | — | — / — / — |
| CSL | Commercial Services Limited (legacy) | com | — | — | — | — | — | — | — / — / — |
| IR | Industrial Restrictive | ind | — | 45 ft | — | — | — | — | — / — / — |
| IG | Industrial General | ind | — | 55 ft | — | — | — | — | — / — / — |
| PBP | Planned Business Park | ind | — | — | — | — | — | — | — / — / — |
Confidence: confirmed partial under review not found
Overlays
H-1
Historic District Overlay
SPECDesignated H-1 boundary on zoning map — Gallatin Commercial Historic District (Public Square, Sumner County Courthouse, Water/Main/College/Franklin Streets). NRHP-listed 1985; local historic zoning 1991.
AO
Airport Overlay
SPECFAR Part 77 imaginary surfaces around Sumner County Regional Airport (Gallatin Municipal / M33) plus city-adopted airport influence zone
FP
Municipal Floodplain Overlay
SPECFEMA Special Flood Hazard Area (SFHA) Zone A/AE within Gallatin corporate limits — includes portions of Station Camp Creek, Town Creek, Old Hickory Lake tributaries
State preemptions
TN-STR-ACTapplies
Qualifying condition
qualifying_condition=Gallatin is a Tennessee municipal corporation; statute applies to all 'local governmental units' in TN. ; city_specific_note=Gallatin's STR ordinance effective date + inventory of lawfully licensed STRs as of that date: not_found in the extracted zoning ordinance (search_performed: gallatintn.gov zoning landing; §10 Special Districts; §13 Non-Conforming Uses). STR regulation — if any — likely lives in a separate chapter of Gallatin's Municipal Code (business-license / hotel-motel regulations) rather than in the zoning ordinance per se. Greater Nashville metro: Sumner County/Gallatin is a growth market for STRs given Nashville tourism spillover; grandfathering inventory is material.
Effect
Any Gallatin STR ordinance may regulate prospectively (registration, occupancy, noise, parking, tax) but cannot retroactively prohibit or eliminate pre-existing lawfully licensed STRs. Pre-ordinance STRs grandfathered in perpetuity as nonconforming uses.
TN-IZ-BANapplies
Qualifying condition
qualifying_condition=Gallatin is a TN municipal corporation; statute applies to all 'local governmental units'. ; city_specific_note=Gallatin's extracted zoning ordinance contains no mandatory IZ percentage or affordability set-aside; mandatory_iz_preempted = false. Any future ZoCo draft provision tying affordability to rezoning or density-bonus USE (not opt-in) would be preempted.
Effect
Gallatin may not enact mandatory affordable set-asides as a condition of zoning approval, building permit, or CO. Voluntary density-bonus opt-in, fee waiver, expedited permitting, or direct-subsidy-tied affordability covenants permitted.
TN-MH-PARITYapplies
Qualifying condition
qualifying_condition=Gallatin residential districts permit site-built SFD; parity requirement attaches to any Gallatin compatibility standard (roof pitch, foundation, skirting, width, orientation). ; city_specific_note=No MH-exclusion or MH-stricter compatibility standard observed in the extracted ordinance; parity assumed in the absence of disparate treatment. Pre-HUD-code (pre-1976) mobile homes are NOT protected and may be banned outright.
Effect
HUD-code manufactured homes must be allowed on parity with site-built SFD in residential districts where SFD is permitted. Compatibility standards must be facially and functionally equivalent to site-built.
TN-Greenbeltapplies
Qualifying condition
qualifying_condition=Any parcel in Gallatin-or-ETJ under active Greenbelt classification (ag 15+ ac farming; forest 15+ ac plan; open space 3+ ac). ; city_specific_note=Gallatin (Sumner County, Nashville-metro fringe) has active agricultural land on the north and east edges consistent with Greenbelt-classified parcels. Rollback exposure is a material acquisition-stage cost on urban-fringe sites; flag at site-selection stage.
Effect
Conversion of Greenbelt-classified land to non-qualifying use triggers rollback tax (3-yr ag/forest, 5-yr open space) plus interest at rezoning / subdivision / change of use.
TN-13-7-208-Nonconformingapplies
Qualifying condition
qualifying_condition=Any lawfully established industrial/commercial use pre-dating a Gallatin zoning change (including any ZoCo adoption).
Effect
Such use cannot be terminated by a subsequent zoning change absent discontinuance. Background protection; relevant for ZoCo rewrite adoption — MUG/MUL/CSL legacy districts also interact with this protection.
Non-applicable laws (1)
TN-ADU-NONEunder_review
Qualifying condition
qualifying_condition=N/A
Effect
ADU regulation is fully local. 2024–2025 statewide ADU-by-right bills failed in committee; 2026 session bills pending (none yet enacted).
Adopted building codes
Major cities adopt newer locally
Click a code label to open its state-by-state adoption atlas.
Quirks & notes
- ZoCo rewrite in flight (not adopted) — Comprehensive zoning code rewrite by TPUDC in draft as of April 2026; circulating for Planning Commission review with public comment via zoco@gallatintn.gov. Legacy Articles 1-15 remain in force. Adoption would trigger a full re-research cycle. — [gallatintn.gov/2286]
- R-number = min-lot-in-thousand-sf convention — R40/R20/R15/R10/R8/R6 use the standard min-lot-in-thousand-sf naming (R40 ~40k sf; R6 ~6k sf). NOT inverse (unlike Grand Prairie). Shared with many TN suburbs.
- Pre-7/7/98 legacy districts (MUG, MUL, CSL) — Three districts (MUG Mixed-Use General, MUL Mixed-Use Limited, CSL Commercial Services Limited) are explicitly retained for parcels mapped pre-7/7/98 only — effectively frozen categories not applied to new rezonings. Interact with TCA §13-7-208 nonconforming protection. — [Zoning-Ord §7, §8]
- Historic District CLG authority — H-1 Historic District Overlay operates under Certified Local Government status (state-federal recognition); Historic Zoning Commission has design review + demolition delay authority on top of base district standards. NRHP-listed 1985; local historic zoning 1991. — [Zoning-Ord §10.02]
- Planned-development family across categories — PRD (residential), SP (mixed), PGC/PNC (commercial), PBP (industrial) provide master-planned flexibility across every base category — unusual breadth. Combined with SP ('Specific Plan'), allows effectively bespoke regulation on large sites. — [Zoning-Ord §6, §7, §8, §9]
- Arterial/collector setback enhancement — Enhanced setback requirements for lots fronting arterial or collector corridors — affects pro formas on primary road frontages (US-31E / Nashville Pike, SR-109, SR-386 / Vietnam Veterans Blvd). — [Zoning-Ord §12.04]
- PDF-only canonical source — Gallatin's zoning ordinance canonical source is a set of per-article city-hosted PDFs (Articles 1-15). No municode / ecode360 mirror. WebFetch cannot parse the PDF binary content; dimensional table re-extraction requires external PDF tooling. Shared pattern with Bartlett TN, Worcester MA.
- Sumner County / Nashville-metro context (non-Metro) — Gallatin is the Sumner County seat and part of the Nashville MSA, but — unlike Davidson/Nashville — is NOT a Metro consolidated government. Municipal zoning governs inside corporate limits; Sumner County zoning (TCA §13-7-201) applies only to unincorporated territory. Nashville-tourism STR spillover + urban-fringe Greenbelt parcels are the two material cross-jurisdictional flags.
Formulas
Definitions
- height
- Maximum building height measured grade to highest point of structure
- lot_coverage
- Building footprint as percentage of lot area
- far
- Gross floor area / lot area
- setbacks
- Distance from property line to nearest building face
- parking
- Schedule 11.03 by use type
Capacity calculations
- arterial_collector_setback_enhancement
Enhanced setback provision for lots fronting arterial or collector roadways- off_street_parking_schedule
Schedule of Off-Street Parking Requirements by use type
Massing explorer
Interactive 3D comparison across every district. Drag to orbit, scroll to zoom, use the slider to walk districts, and toggle applicable overlays in the right-side panel.
Sort by
Max height
— ft
——
Floor area ratio
—
——
Lot coverage
—%
——
Setbacks (F / S / R)
— ft
——
Parking
— /unit
——
Max density
— du/ac
——
Min lot size
— sf
——
Copy zoning profile
Loading…
| District | Category | Height | FAR | Coverage | Setbacks | Parking | Density | Min lot | Overlays |
|---|
Sources & references
Primary source
Research status
Publication gates
| primary url present | passed | |
|---|---|---|
| no aggregator cited | passed | |
| confidence tags full form | passed | |
| overlays have parameters trigger confidence | passed | |
| preempt section city specific | passed |
Data quality
Documented gaps
- R40 setbacks in profile (front=25/side=10/rear=25, status=partial) do NOT match Zoning-Ord §06.03 actual values (front=50/side=20/rear=30). Width 120 ft also missing. Replace partial values with confirmed live-ordinance values on next refresh. Source: gallatintn.gov/DocumentCenter/View/1118 §06.03.030.C and §06.03.030.D. Verified 2026-05-21.
- R20 setbacks not populated in profile (currently absent). Live values per §06.04: front=40, side=15, rear=30, width=100. Add to base_districts[R20] on next refresh.
- R15 setbacks not populated. Live values per §06.05: front=40, side=10, rear=25, width=75. Add on next refresh.
- R10 setbacks not populated. Live values per §06.06: front=25, side=10, rear=15, width=60. Add on next refresh.
- R8 setbacks not populated (per-use-type table: SFD=20/10*/15 with combined-side-yard=18 ft floor, attached=20/10/15, other=25/10/25, width=55). Add on next refresh.
Verification
| last_verified_at | 2026-05-21T00:00:00Z |
|---|---|
| verifier_specialist | verification-pass |
| verifier_version | 1.0 |
| verification_result | passed |
| atomic_claims_checked | 28 |
| atomic_claims_passed | 28 |
| atomic_claims_failed | 0 |
| notes | All confirmed claims carry Zoning-Ord §X citations (§6/§7/§8/§9/§10.02/§10.03/§10.04/§11.03/§12.04) or TCA §X citations. No aggregator citations (Municode, Zoneomics, Steadily, SitePlanGuide) appear. Partial / inferred / not_found / not_applicable statuses are explicit with reason or derivation. |
| narrative_ref | narratives/gallatin-tn/c6490014-b030-4b97-8f92-ab9ceabed1ca.json |
| last_verified_evidence | {"verified_at": "2026-05-21T00:00:00Z", "method": "re-fetch primary Gallatin Article 6 (Residential) and Article 10 (Special District / Overlays) PDFs + pdftotext + dimensional diff vs profile partial-status values", "url": "https://gallatintn.gov/DocumentCenter/View/1118", "sections_resampled": ["Article 6 §06.03 R40 Low Density Residential: '06.03.030.B Minimum Required Lot Area shall be 40,000 square feet' — matches profile R40.min_lot_sf=40000 (inferred status, value correct)", "Article 6 §06.03 R40 setbacks (PDF line 312-314): 'Front Yards - a minimum of fifty (50) feet. Side Yards - a minimum of twenty (20) feet. Rear Yards - a minimum of thirty (30) feet.' — DOES NOT MATCH profile R40 partial values (front=25 ✗, side=10 ✗, rear=25 ✗). The current profile setbacks appear to be ~R10 values mistakenly applied to R40. See quality.gaps[] for required correction.", "Article 6 §06.04 R20: 'Minimum Required Lot Area shall be 20,000 square feet ... Front Yards - minimum of forty (40) feet. Side Yards - minimum of fifteen (15) feet ... Rear Yards - minimum of thirty (30) feet. Minimum Lot Width 100 feet' — profile R20 carries min_lot_sf=20000 only (matches) with no setback values, so no profile conflict, but new ground-truth values now available", "Article 6 §06.05 R15: '15,000 sq ft, front 40, side 10, rear 25, width 75' — profile R15 has only min_lot_sf=15000 (matches)", "Article 6 §06.06 R10: '10,000 sq ft, front 25, side 10, rear 15, width 60' — profile R10 has only min_lot_sf=10000 (matches)", "Article 6 §06.07 R8 setback table (line 759): 'Front 20 (SF det) / 20 (SF att) / 25 (Other); Side 10*/10/10; Rear 15/15/25' — profile R8 has only min_lot_sf=8000 (matches)", "Article 10 §10.02 H-1 Historic District, §10.03 Floodplain, §10.04 Airport Overlay — all overlay citations confirmed verbatim against §10.02-10.04 structure (PDF lines 9-10, 17, 31)"], "match_rate_pct": 85, "outcome": "verified-with-gaps", "gap_notes": "Most cited section/article numbers + lot-area values resolve correctly. ONE concrete mismatch: profile R40 setback values (front=25/side=10/rear=25, status=partial) do not match the live ordinance (50/20/30 per Article 6 §06.03). Profile honestly flagged these as 'partial' rather than 'confirmed' — but the values themselves are wrong and should be replaced in a future pass. Logged in quality.gaps[]."} |
Other cities in this state
Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.