Las Vegas, NV Zoning

Euclidean-zoning. 21 districts · 7 overlays · 7 applicable state preemptions.

Overview

Code type
euclidean
Naming convention
mixed
Naming convention by category
res_sfletter-code
res_mfdensity-encoded
comletter-code
indletter-code

Residential SF districts use letter-code (R-A, R-E, R-D, R-1, R-CL). MF districts R-2/R-3/R-4/R-5 encode density band (6-12 du/ac, 13-25, 26-50, unlimited). Commercial districts use letter-code (P-R, N-S, O, C-D, C-1, C-2, C-PB, C-M, M). Note: R-5 appears to be higher density than R-4 (density-encoded ascending). NOT inverse — R-1 is standard SF, higher number = higher density.

Worth knowing
  • Las Vegas UDC replaced original Title 19 (1997) + Title 18 subdivision ordinances effective 2011-05-01. Some city PDFs still carry 'March 1997' headers but have been amended through Ord. 6210+ and subsequent enactments.
  • FAR is NOT used as a primary dimensional control in any base district. Height + lot coverage govern massing. FAR values are not_found by design, not a data gap.
  • Lot coverage is absent (NA) for all single-family residential districts (U, R-A, R-E, R-D, R-1, R-CL, R-MH) and most multi-family districts. Coverage is meaningful primarily in C/I districts.

+ 12 more in Quirks & notes

Districts

res_sf 7res_mf 4com 4ind 3off 2ag 1
CodeNameCategory Min lotHeight CoverageFAR Du/acParking Setbacks F/S/R
UUndeveloped (GPA Designation)ag20,000 sf[4]35 ft[5][6][7][8][9]50[1] / 10[2] / 35[3]
R-ARanch Acresres_sf40,000 sf[13]35 ft[14][15][16]1[17]2[18]50[10] / 10[11] / 35[12]
R-EResidence Estatesres_sf20,000 sf[22]35 ft[23][24][25]1[26]2[27]50[19] / 10[20] / 35[21]
R-DSingle Family Residential-Restrictedres_sf11,000 sf[31]35 ft[32][33][34]1[35]2[36]25[28] / 10[29] / 30[30]
R-1Single Family Residentialres_sf6,500 sf[40]35 ft[41][42][43]1[44]2[45]20[37] / 5[38] / 15[39]
R-CLSingle Family Compact-Lotres_sf3,500 sf[49]35 ft[50][51][52]1[53]2[54]14[46] / 5[47] / 10[48]
R-MHMobile/Manufactured Home Residenceres_sf6,500 sf[58]35 ft[59][60][61]1[62]2[63]15[55] / 5[56] / 10[57]
R-MHPResidential Mobile/Manufactured Home Parkres_sf4,000 sf[67]35 ft[68]0.5[69][70]6[71]2[72]5[64] / 5[65] / 5[66]
R-2Medium-Low Density Residentialres_mf6,500 sf[76]35 ft[77][78][79][80]2[81]20[73] / 5[74] / 20[75]
R-3Medium Density Residentialres_mf6,500 sf[85][{'variant': 'standard', 'value': 35}, {'variant': 'senior-citizen-apartments', 'value': 40, 'note': 'With SDP approval per Table 2 note 5; further height waivers require SDP'}] ft[86][87][88][89]2[90]20[82] / 5[83] / 20[84]
R-4High Density Residentialres_mf6,500 sf[94][{'variant': 'standard', 'value': 35}, {'variant': 'senior-citizen-apartments', 'value': 40, 'note': 'With SDP approval per Table 2 note 5'}] ft[95][96][97][98]2[99]10[91] / 5[92] / 20[93]
R-5Apartment Districtres_mf7,000 sf[103][{'variant': 'outside-DCP-O', 'value': 55, 'note': '5 stories or 55 ft whichever is less per Table 2'}, {'variant': 'inside-DCP-O', 'value': -1, 'note': 'Unlimited — DCP-O exempts from automatic height limits per §19.08.040(A) Table 2 note 1'}] ft[104][105][106]-1[107]2[108]10[100] / 5[101] / 20[102]
P-RProfessional Office and Parkingoff[112]35 ft[113]0.3[114][115][116][117]20[109] / 5[110] / 15[111]
N-SNeighborhood Servicecom[121]35 ft[122]0.3[123][124][125][126]25[118] / 10[119] / 25[120]
OOfficeoff[130]35 ft[131]0.3[132][133][134][135]25[127] / 10[128] / 15[129]
C-DDesigned Commercialcom[139][{'variant': 'charleston-blvd-between-rancho-and-valley-view', 'value': 20, 'note': '1 story or 20 ft per §19.08.050(C) Table 1 note 2c(1)'}, {'variant': 'all-other-parcels', 'value': 35, 'note': '2 stories or 35 ft per §19.08.050(C) Table 1 note 2c(2)'}] ft[140]0.3[141][142][143][144]25[136] / 10[137] / 25[138]
C-1Limited Commercialcom[148][{'variant': 'outside-neighborhood-revitalization-area-mixed-use', 'value': 150, 'note': '10 stories or 150 ft for mixed-use outside NRA per §19.08.050(C) note 2d'}, {'variant': 'standard', 'value': 35, 'note': '2 stories or 35 ft base standard per Table 1; NRA parcels subject to base only'}] ft[149]0.5[150][151][152][153]20[145] / 10[146] / 20[147]
C-2General Commercialcom[157][{'variant': 'outside-neighborhood-revitalization-area-mixed-use', 'value': 150, 'note': '10 stories or 150 ft for mixed-use outside NRA per §19.08.050(C) note 2d'}, {'variant': 'standard', 'value': 35, 'note': '2 stories or 35 ft base standard per Table 1'}] ft[158]0.5[159][160][161][162]20[154] / 10[155] / 20[156]
C-PBPlanned Business Parkind871,200 sf[166][{'variant': 'standard', 'value': 85, 'note': '5 stories or 85 ft whichever is less per §19.08.050(C) note 2e'}, {'variant': 'freeway-adjacent-within-200ft', 'value': 100, 'note': '6 stories or 100 ft for C-PB contiguous to or within 200 ft of freeway/expressway per note 2e'}, {'variant': 'commercial-retail-uses', 'value': 35, 'note': '2 stories or 35 ft for permitted commercial/retail uses per note 2e'}] ft[167]0.5[168][169][170][171]20[163] / 10[164] / 15[165]
C-MCommercial/Industrialind[175][176]0.5[177][178][179][180]10[172] / 10[173] / 20[174]
MIndustrialind[184][185][186][187][188][189]10[181] / 0[182] / 0[183]

Confidence: confirmed partial under review not found

Overlays

DCP-O
Downtown Centennial Plan Overlay District
DT
§19.06.060

Applies to all parcels within the Downtown Centennial Plan Overlay District boundaries as delineated on the official boundary map adopted per Ord. 6080. Exempts properties from automatic application of height, setback, lot coverage, residential adjacency, landscaping, and parking standards in §§19.08.040, 19.08.050, 19.08.060, Ch.19.10, Ch.19.12.

height_limit_overrideNo automatic maximum; standards imposed on case-by-case basis via Site Development Plan review
setback_overrideAutomatic setback requirements waived; case-by-case via SDP
lot_coverage_overrideAutomatic lot coverage requirements waived; case-by-case via SDP
parking_overrideStandard parking requirements waived within DCP-O; case-by-case via SDP
design_standardsDevelopment must conform to Las Vegas Downtown Centennial Plan Design Standards (mandatory per §19.06.060(B))
residential_adjacency_exemptTrue
G-O
Gaming Enterprise Overlay District
SPEC
§19.06.070

Applies to parcels within the Gaming Enterprise Overlay District boundaries as set forth in maps under LVMC Chapter 6.40. Boundaries changed per rezoning procedures in LVMC 19.18.040 and State law + LVMC 6.40.160.

height_limit_overrideAll licensed gaming establishments within the Gaming Enterprise District are exempt from automatic height limitations in Title 19 Chapter 19.08
height_conditionsCity Council may impose height limitation via Site Development Plan approval
governing_lawLVMC Chapter 6.40 and Nevada gaming state law
A-O
Airport Overlay District
AP
§19.06.080

Applies to parcels delineated on: (1) McCarran International Airport Official Airspace Zoning Map (sheet 3, Clark County Airport Engineering Dept., dated 1990-07-18); (2) North Las Vegas Air Terminal Official Airspace Zoning Map. All development above 35 ft within mapped airspace surfaces subject to height limitations on the Airport Overlay Maps.

height_controlNo structure may exceed FAA imaginary surface heights depicted on Airport Overlay Maps (approach surfaces, transitional surfaces, horizontal surfaces, conical surfaces). Structures up to 35 ft above grade are exempt from Planning Commission review.
faa_review_threshold_ft200
slope_restrictionStructures exceeding 100:1 horizontal-to-vertical slope from nearest runway point within 20,000 ft require Planning Commission approval
nellis_considerationNellis AFB airspace given consideration although not formally part of A-O per §19.06.080(A)(4)
aviation_easementMay be required as condition of building permit
use_restrictionsNo use creating electrical interference, glare, or bird-strike hazards to aircraft
H
Historic Designation
HP
§19.06.090

Applied to individually-designated Landmarks, Historic Properties, and Historic Districts via Historic Preservation Commission nomination and City Council adoption per §19.06.090(I). Geographic scope defined per each individual designation.

review_requiredAlterations, new construction, demolition, or removal of designated properties require Certificate of Appropriateness from Historic Preservation Commission
demolition_standardDemolition requires finding that retention is not feasible or compatible with neighborhood; 90-day delay imposed during review
design_reviewGuidelines and standards for review adopted per §19.06.090(K); maintains character-defining features
incentivesTax incentives and other incentives available per §19.06.090(O)
DEOD
Downtown Casino Overlay District
SPEC
§19.06.100

Applies to parcels within boundaries adopted by ordinance per §19.06.100(A). Focuses on Fremont Street area and surrounding downtown casino corridor.

sign_standardsSpecial sign standards apply — large-format signs, LED displays, and specific sign setbacks governed by §19.06.100(C)
sign_review_procedureSpecial sign approvals per §19.06.100(D) — Planning Commission and City Council review for off-premise signs and non-standard sign types
sign_height_bonusSign structures may exceed base zoning height limits per DEOD special standards
LW-O
Live/Work Overlay District
SPEC
§19.06.130

Applies to parcels within the Live/Work Overlay District boundaries as delineated on the Live/Work Overlay District Map in §19.06.130(C). Located in designated urban infill areas.

permitted_usesLive/work units (combined residential + commercial in single unit) permitted by right within overlay boundaries
approval_processApplications evaluated per §19.06.130(E) criteria; case-by-case Director approval
applicabilityDoes not supersede other Title 19 provisions except as specifically stated in §19.06.130(F)
FEMA-SFHA
Floodplain Management
FP
§19.00 + FEMA FIRM panels for Clark County

Applies to all parcels within the Special Flood Hazard Area (SFHA) as delineated on current FEMA Flood Insurance Rate Maps for Las Vegas / Clark County. Separate from A-O.

bfe_complianceDevelopment in SFHA must comply with base flood elevation requirements per Clark County Regional Flood Control District Hydrologic Criteria and Drainage Design Manual (HCDDM) as adopted by the City
drainage_designDrainage studies required per §19.08.030(F) and §19.08.050(E)(1)(d) for developments ≥15 net acres
natural_channel_retentionPreference for natural-material lining per §19.08.050(E)(1)(d); plain concrete requires Public Works approval
freeboardLocal freeboard standard not separately quantified in retrieved code sections; governed by HCDDM

State preemptions

Qualifying condition
Always applicable statewide — NRS 278 is the foundational delegation statute for all Nevada local zoning authority. Las Vegas is a charter city under NRS 268 and draws all zoning power from NRS 278. Population threshold: not applicable (always).
Source
NRS 278 text; City of Las Vegas is a charter city confirmed per §19.00 code preamble
Effect
All local zoning actions must trace to NRS 278 grant; regulations beyond enumeration are ultra vires. NRS 278.250(2) requires uniformity within each district. NRS 278.0235 imposes 25-day SOL on judicial review. Development agreements must comply with NRS 278.0201–278.0207.
Qualifying condition
Trigger: county population ≥ 100,000. Clark County population = 2,291,167 (2020 Census) ≥ 100,000 threshold. Las Vegas is an incorporated city in Clark County. ADU mandate applies.
Source
U.S. Census Bureau 2020 Decennial Census, Clark County population; NRS 278.02095 (AB 240, 81st Session 2021)
Effect
Las Vegas must authorize ADUs by-right on lots zoned for single-family use. De facto bans through onerous standards not permitted. City may impose substantive conditions (setbacks, height, parking, owner-occupancy, minimum lot size) if not tantamount to prohibition.
Qualifying condition
Always applicable statewide — no population threshold. Las Vegas may not categorically exclude HUD-Code post-1976 manufactured homes from districts permitting site-built single-family; R-MH district exists as specialized district.
Source
NRS 278.02083 text; NRS Chapter 489 (Manufactured Housing Division)
Effect
HUD-Code post-1976 manufactured homes allowed by right in single-family districts. Installation governed exclusively by NRS 489. CUP not required solely because home is manufactured.
Qualifying condition
Statewide mandate — applies to all Nevada commercial-zoned parcels except (a) parcels inside Tahoe Regional Planning Compact boundary and (b) parcels inside airport-overlay or airport-influence zones. Las Vegas is in Clark County (not Tahoe compact area). Airport Overlay District (A-O) parcels in Las Vegas are expressly exempt per AB 241 §5. All non-airport commercial parcels subject to by-right multifamily mandate effective 2025-10-01 with local ordinance conformance deadline of 2026-03-01.
Source
Nevada AB 241 (83rd Session, 2025), Chapter 174, Statutes of Nevada 2025 §§1-5; lasvegasnevada.gov for confirmation Las Vegas is outside Tahoe compact
Effect
Multifamily residential and mixed-use residential permitted by-right on all commercially-zoned parcels (C-D, C-1, C-2, C-PB, C-M, O, P-R) not in airport overlay. Ministerial (non-discretionary) review required. Inconsistent local ordinances voided by operation of law as of 2026-03-01.
Qualifying condition
Trigger: county population ≥ 700,000. Clark County population = 2,291,167 (2020 Census) ≥ 700,000 threshold. Las Vegas is an incorporated city in Clark County. STR ordinance mandate applies. Note: this overlay targets the county-level ordinance requirement, but as an incorporated city in Clark County, Las Vegas's STR regulations (and LVMC amendments thereto) must conform to the AB 363 framework.
Source
U.S. Census Bureau 2020 Decennial Census, Clark County; NRS 244.3358 (AB 363, 81st Session 2021)
Effect
Las Vegas must maintain an STR regulatory framework including: permit required, distance separation, occupancy and parking minimums, event-use prohibition above capacity. Floor not ceiling — Las Vegas may impose more restrictive rules.
Qualifying condition
Trigger: city is in Clark County AND parcel is near designated transit corridor AND project is qualifying multifamily. Clark County population = 2,291,167 ≥ 700,000 threshold. Las Vegas is in Clark County. Parcels near designated transit corridors in Las Vegas subject to 120-day ministerial review shot-clock for qualifying multifamily. Specific transit corridor boundaries to be designated per implementing regulations; parcel-level determination required.
Source
Nevada AB 540 (83rd Session, 2025), NRS 278.02527; U.S. Census Bureau 2020 Clark County population
Effect
Qualifying multifamily projects near designated transit corridors receive ministerial (non-discretionary) review with 120-day shot-clock. AMI definition broadened to 30–150% for attainable-housing eligibility.
Qualifying condition
Trigger: county population ≥ 100,000 AND project type = multifamily AND application complete. Clark County population = 2,291,167 ≥ 100,000. Las Vegas is in Clark County. Shot-clock applies to complete multifamily applications submitted on or after 2025-10-01.
Source
Nevada SB 394 (83rd Session, 2025); U.S. Census Bureau 2020 Clark County population
Effect
Las Vegas must decide complete multifamily applications within 120 days. Pairs with AB 241 (substantive by-right entitlement) and AB 540 (transit ministerial review).
Non-applicable laws (1)
Nellis AFB AICUZ + FAA Part 77 Federal Overlayper_parcel_conditional
Qualifying condition
Federal overlay applies to parcels within FAA Part 77 imaginary surfaces and AICUZ APZs for Nellis AFB (northeast Las Vegas Valley). Las Vegas city limits include some parcels near Nellis. Per §19.06.080(A)(4), Las Vegas code gives 'consideration' to Nellis AFB airspace but Nellis is not formally part of the municipal A-O District. NV AB 241 (2025) airport carve-out is self-executing for parcels in the A-O district. Nellis AICUZ extends outside formal A-O boundary.
Source
§19.06.080(A)(4) LVMC; DoD Instruction 4165.57; AB 241 (2025) §5 airport carve-out
Effect
Height limits per FAA Part 77 imaginary surfaces; AICUZ APZ compatibility recommendations. Federal-conflict check enabled for parcels in Nellis flight path; AB 241 by-right multifamily exempted for airport-zoned parcels.

Adopted building codes

Statewide w/ local amendments

Local adoption
2024
2023
Local
IECC (Residential)
2024
IECC (Commercial)
2024

Click a code label to open its state-by-state adoption atlas.

Amendment history

DateKindCitation
2026-05-27retrieved athttps://online.encodeplus.com/regs/lasvegas-nv/doc-viewer.aspx + https://files.lasvegasnevada.gov/planning/
2018-10-22amendment effectiveChapter 19.09 Form-Based Code effective for downtown properties per lasvegasnevada.gov/Business/Planning-Zoning/Zoning-Code
2011-05-01effectiveUnified Development Code replaced Title 18 Subdivision Ordinances + Title 19 Zoning Code per city planning department website
1997-03-01adoptionTitle 19 Zoning Code, City of Las Vegas — original adoption

Quirks & notes

  • Las Vegas UDC replaced original Title 19 (1997) + Title 18 subdivision ordinances effective 2011-05-01. Some city PDFs still carry 'March 1997' headers but have been amended through Ord. 6210+ and subsequent enactments.
  • FAR is NOT used as a primary dimensional control in any base district. Height + lot coverage govern massing. FAR values are not_found by design, not a data gap.
  • Lot coverage is absent (NA) for all single-family residential districts (U, R-A, R-E, R-D, R-1, R-CL, R-MH) and most multi-family districts. Coverage is meaningful primarily in C/I districts.
  • R-MHP has the same 50% lot coverage as commercial districts — unique among residential districts.
  • R-5 maximum height is 5 stories/55 ft outside DCP-O but unlimited inside DCP-O where the Downtown Centennial Plan overlay waives all automatic standards.
  • R-2/R-3/R-4 density ranges (6-12, 13-25, 26-50 du/ac) are bands per Table 2 — not single scalar values. Schema du_ac field cannot represent ranges; values recorded as not_captured per FM-5.
  • R-3 and R-4 senior citizen apartments may exceed standard 35 ft height limit up to 40 ft with SDP approval; further waivers require separate SDP waiver per Table 2 note 5.
  • Residential adjacency standards (§19.08.060) impose a 3:1 proximity slope on non-residential and multi-family development near SF residential — not codified in per-district dimensional table but applies citywide.
  • Downtown Centennial Plan Overlay (DCP-O) is NOT subject to residential adjacency standards per §19.08.060(A)(3).
  • C-PB requires a 20-acre minimum site area to rezone — among the largest minimum in the code.
  • M (Industrial) district has zero side and rear yard setbacks, but a 50 ft setback from residential property line is required where adjacent to residential per §19.08.050(C) Table 1 note 7.
  • Nevada AB 241 (2025) by-right multifamily mandate on commercial land is citywide effective 2025-10-01; local ordinance conformance deadline was 2026-03-01. Verify whether LVMC amendments have been incorporated.
  • Parking ratios for all uses are in Table 2 of Section 19.04.010 (LVMC 19.12.070) — the parking chapter is NOT reproduced in the development-standards chapter. Residential parking is 2 spaces per DU (inferred standard; exact residential table not retrieved from 19.04.010).
  • The Gaming Enterprise Overlay (G-O) encompasses the Las Vegas Strip and Fremont Street casino corridors. Height exemption for licensed gaming establishments is complete — no automatic maximum.
  • Form-Based Code Chapter 19.09 (effective 2018-10-22) applies to downtown subdistricts within DCP-O boundaries and introduces transect-based standards for those areas.

Formulas

Definitions

height
Grade to highest point of structure. §19.08.030(C).
lot_coverage
Aggregate ground floor area of all structures (excluding carports and detached trash enclosures) / lot area. §19.08.050(C)(1)(c) note 8.
far
Gross floor area / lot area. Not used as a primary control in Title 19 base districts — height and lot coverage govern instead.
du_ac
Dwelling units per gross acre. Used in R-2/R-3/R-4/R-5 Table 2. §19.08.040(A).
setback_front
Building face to front property line. §19.08.040(A) Table 1/2.
setback_side
Building face to side property line. §19.08.040(A) Table 1/2.
setback_rear
Building face to rear property line. §19.08.040(A) Table 1/2.
parking
Spaces per dwelling unit. Governed by LVMC 19.12.070 (Table 2 of Section 19.04.010). Driveways may satisfy parking for SF uses. §19.10.010(E)(7).

Capacity calculations

max_footprint_sf
lot_area_sf * lot_coverage
buildable_width_ft
lot_width_ft - setback_side_ft * 2
buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_ft
max_stories_approx
max_height_ft / 10

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
LOW
HIGH
drag to orbit · scroll to zoom
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

Citations
  1. [1] §19.08.040(A) Table 1 note 1
  2. [2] §19.08.040(A) Table 1
  3. [3] §19.08.040(A) Table 1
  4. [4] §19.08.040(A) Table 1
  5. [5] §19.08.040(A) Table 1
  6. [6] §19.08.040(A) Table 1
  7. [7] n
  8. [8] §19.08.040(A) Table 1
  9. [9] §19.10.010
  10. [10] §19.08.040(A) Table 1 note 1
  11. [11] §19.08.040(A) Table 1
  12. [12] §19.08.040(A) Table 1
  13. [13] §19.08.040(A) Table 1
  14. [14] §19.08.040(A) Table 1
  15. [15] §19.08.040(A) Table 1
  16. [16] n
  17. [17] §19.08.040(A) Table 1
  18. [18] §19.10.010(E)(7)
  19. [19] §19.08.040(A) Table 1 note 1
  20. [20] §19.08.040(A) Table 1
  21. [21] §19.08.040(A) Table 1
  22. [22] §19.08.040(A) Table 1
  23. [23] §19.08.040(A) Table 1
  24. [24] §19.08.040(A) Table 1
  25. [25] n
  26. [26] §19.08.040(A) Table 1
  27. [27] §19.10.010(E)(7)
  28. [28] §19.08.040(A) Table 1
  29. [29] §19.08.040(A) Table 1
  30. [30] §19.08.040(A) Table 1
  31. [31] §19.08.040(A) Table 1
  32. [32] §19.08.040(A) Table 1
  33. [33] §19.08.040(A) Table 1
  34. [34] n
  35. [35] §19.08.040(A) Table 1
  36. [36] §19.10.010(E)(7)
  37. [37] §19.08.040(A) Table 1
  38. [38] §19.08.040(A) Table 1
  39. [39] §19.08.040(A) Table 1
  40. [40] §19.08.040(A) Table 1
  41. [41] §19.08.040(A) Table 1
  42. [42] §19.08.040(A) Table 1
  43. [43] n
  44. [44] §19.08.040(A) Table 1
  45. [45] §19.10.010(E)(7)
  46. [46] §19.08.040(A) Table 1 note 4
  47. [47] §19.08.040(A) Table 1 note 5
  48. [48] §19.08.040(A) Table 1
  49. [49] §19.08.040(A) Table 1 note 2
  50. [50] §19.08.040(A) Table 1
  51. [51] §19.08.040(A) Table 1
  52. [52] n
  53. [53] §19.08.040(A) Table 1
  54. [54] §19.10.010(E)(7)
  55. [55] §19.08.040(A) Table 1
  56. [56] §19.08.040(A) Table 1
  57. [57] §19.08.040(A) Table 1
  58. [58] §19.08.040(A) Table 1
  59. [59] §19.08.040(A) Table 1
  60. [60] §19.08.040(A) Table 1
  61. [61] n
  62. [62] §19.08.040(A) Table 1
  63. [63] §19.10.010(E)(7)
  64. [64] §19.08.040(A) Table 1
  65. [65] §19.08.040(A) Table 1
  66. [66] §19.08.040(A) Table 1
  67. [67] §19.08.040(A) Table 1
  68. [68] §19.08.040(A) Table 1
  69. [69] §19.08.040(A) Table 1
  70. [70] n
  71. [71] §19.08.040(A) Table 1
  72. [72] §19.10.010(E)(7)
  73. [73] §19.08.040(A) Table 2
  74. [74] §19.08.040(A) Table 2
  75. [75] §19.08.040(A) Table 2
  76. [76] §19.08.040(A) Table 2
  77. [77] §19.08.040(A) Table 2
  78. [78] §19.08.040(A) Table 2
  79. [79] n
  80. [80] §19.08.040(A) Table 2
  81. [81] §19.10.010(F)
  82. [82] §19.08.040(A) Table 2
  83. [83] §19.08.040(A) Table 2
  84. [84] §19.08.040(A) Table 2
  85. [85] §19.08.040(A) Table 2
  86. [86] §19.08.040(A) Table 2 + note 5
  87. [87] §19.08.040(A) Table 2
  88. [88] n
  89. [89] §19.08.040(A) Table 2
  90. [90] §19.10.010(F)
  91. [91] §19.08.040(A) Table 2
  92. [92] §19.08.040(A) Table 2
  93. [93] §19.08.040(A) Table 2
  94. [94] §19.08.040(A) Table 2
  95. [95] §19.08.040(A) Table 2 + note 5
  96. [96] §19.08.040(A) Table 2
  97. [97] n
  98. [98] §19.08.040(A) Table 2
  99. [99] §19.10.010(F)
  100. [100] §19.08.040(A) Table 2
  101. [101] §19.08.040(A) Table 2
  102. [102] §19.08.040(A) Table 2 note 2
  103. [103] §19.08.040(A) Table 2
  104. [104] §19.08.040(A) Table 2 note 1
  105. [105] §19.08.040(A) Table 2
  106. [106] n
  107. [107] §19.08.040(A) Table 2 note 1
  108. [108] §19.10.010(F)
  109. [109] §19.08.050(C) Table 1
  110. [110] §19.08.050(C) Table 1
  111. [111] §19.08.050(C) Table 1
  112. [112] §19.08.050(C) Table 1
  113. [113] §19.08.050(C) Table 1 note 2b
  114. [114] §19.08.050(C) Table 1
  115. [115] n
  116. [116] n
  117. [117] §19.10.010(F)
  118. [118] §19.08.050(C) Table 1
  119. [119] §19.08.050(C) Table 1
  120. [120] §19.08.050(C) Table 1
  121. [121] §19.08.050(C) Table 1
  122. [122] §19.08.050(C) Table 1
  123. [123] §19.08.050(C) Table 1
  124. [124] n
  125. [125] n
  126. [126] §19.10.010(F)
  127. [127] §19.08.050(C) Table 1
  128. [128] §19.08.050(C) Table 1
  129. [129] §19.08.050(C) Table 1
  130. [130] §19.08.050(C) Table 1
  131. [131] §19.08.050(C) Table 1 note 2b
  132. [132] §19.08.050(C) Table 1
  133. [133] n
  134. [134] n
  135. [135] §19.10.010(F)
  136. [136] §19.08.050(C) Table 1
  137. [137] §19.08.050(C) Table 1
  138. [138] §19.08.050(C) Table 1
  139. [139] §19.08.050(C) Table 1
  140. [140] §19.08.050(C) Table 1 note 2c
  141. [141] §19.08.050(C) Table 1
  142. [142] n
  143. [143] n
  144. [144] §19.10.010(F)
  145. [145] §19.08.050(C) Table 1
  146. [146] §19.08.050(C) Table 1
  147. [147] §19.08.050(C) Table 1
  148. [148] §19.08.050(C) Table 1
  149. [149] §19.08.050(C) Table 1 note 2d
  150. [150] §19.08.050(C) Table 1
  151. [151] n
  152. [152] n
  153. [153] §19.10.010(F)
  154. [154] §19.08.050(C) Table 1
  155. [155] §19.08.050(C) Table 1
  156. [156] §19.08.050(C) Table 1
  157. [157] §19.08.050(C) Table 1
  158. [158] §19.08.050(C) Table 1 note 2d
  159. [159] §19.08.050(C) Table 1
  160. [160] n
  161. [161] n
  162. [162] §19.10.010(F)
  163. [163] §19.08.050(C) Table 1
  164. [164] §19.08.050(C) Table 1
  165. [165] §19.08.050(C) Table 1
  166. [166] §19.08.050(C) Table 1
  167. [167] §19.08.050(C) Table 1 note 2e
  168. [168] §19.08.050(C) Table 1
  169. [169] n
  170. [170] n
  171. [171] §19.10.010(F)
  172. [172] §19.08.050(C) Table 1
  173. [173] §19.08.050(C) Table 1
  174. [174] §19.08.050(C) Table 1
  175. [175] §19.08.050(C) Table 1
  176. [176] §19.08.050(C) Table 1
  177. [177] §19.08.050(C) Table 1
  178. [178] n
  179. [179] n
  180. [180] §19.10.010(F)
  181. [181] §19.08.050(C) Table 1
  182. [182] §19.08.050(C) Table 1
  183. [183] §19.08.050(C) Table 1
  184. [184] §19.08.050(C) Table 1
  185. [185] §19.08.050(C) Table 1
  186. [186] §19.08.050(C) Table 1
  187. [187] n
  188. [188] n
  189. [189] §19.10.010(F)

Research status

Publication gates

primary url presentpassedcode_source = https://online.encodeplus.com/regs/lasvegas-nv/doc-viewer.aspx — city-hosted enCodePlus platform, not an aggregator
no aggregator citedpassedScan clean — no Zoneomics, Steadily, SitePlanGuide, Propwire, Zonara, Unzoned, or similar aggregator domain cited in any field
confidence tags full formpassed78 confirmed fields; all confirmed fields carry §-citations (e.g., §19.08.040(A) Table 1, §19.06.060, §19.08.050(C) Table 1). Gate 3 format enforced throughout.
overlays have parameters trigger confidencepassed7 overlays defined; all have non-empty params, geographic_trigger, status, and §-citation confidence codes
preempt section city specificpassed8 preemption laws with city-specific qualifying_condition_checked including numeric inputs (Clark County pop 2,291,167 ≥ 100k/700k thresholds), vintages (2020 Census), and arithmetic where applicable

Data quality

82%completeness78 confirmed18 not found
Documented gaps
  • Parking ratios for non-residential uses (office, commercial, industrial) not extracted — reference LVMC 19.12.070 (Table 2 of §19.04.010) for exact per-use ratios
  • R-2/R-3/R-4 density ranges encoded as not_captured (FM-5); actual values: R-2=6-12 du/ac, R-3=13-25 du/ac, R-4=26-50 du/ac
  • Mixed-use lot coverage bonus (up to 75% with SDP) not reflected in per-district records — applies to C-1/C-2 per §19.08.050(C)(3) note 8
  • Nellis AFB AICUZ boundary exact parcels within Las Vegas city limits not cross-referenced
  • AB 241/AB 540 local conformance ordinance status as of 2026-05-27 not verified against LVMC update history

Other cities in this state

Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.