My WebLink
|
Help
|
About
|
Sign Out
Home
2025 08-19 CC Packet
GemLake
>
CITY COUNCIL
>
PACKETS
>
2020 - 2026
>
2025
>
2025 08-19 CC Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/9/2025 9:29:58 AM
Creation date
10/9/2025 9:26:19 AM
Metadata
Fields
Template:
Administration
Code
ADM 00500
Document
CITY COUNCIL PACKETS
Destruction
PERMANENT
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
468
Show annotations
View images
View plain text
Consolidated Land Use Ordinance No. 131 Update <br />Gem Lake City Council 8/19/25 <br />August 13, 2025 <br />Page 2 <br /> <br /> <br /> <br />Residential Zone Reference Guide <br /> <br />The following table serves as a reference as the Council walks through the proposed amendments to ensure <br />understanding of the four very similarly abbreviated residential districts. <br />Zoning District Maximum Allowable Density Symbology on the Zoning Map <br />Singe Family Estate – RE <br />(Section 5 in the Ordinance) <br />1 dwelling unit per 5 acres Shown in yellow, the largest lots in the <br />City near Gem Lake <br />Singe Family Executive – RX <br />(Section 6 in the Ordinance) <br />1 dwelling unit per 3 acres Shown in light orange, covers most land <br />in the City and includes the golf course. <br />Low Density Single Family – RO <br />(Section 7 in the Ordinance) <br />1 dwelling unit per 1 acre Shown in orange, located north of <br />Goose Lake road and east of <br />Schueneman Road <br />Medium Density Single Family – RS <br />(Section 8 in the Ordinance) <br />1 dwelling unit per 0.5 acres Shown in brown, located in the northern <br />portion of the City, the highest density. <br /> <br />PROPOSED AMENDMENTS <br /> <br />Amendments were made to provide clarity on permitting within each zoning district. This includes updated <br />formatting, language, and division of sections, as well as the minor changes of writing conventions. To better <br />understand the progress of these revisions since June 2025, please review the Planning Commission meeting <br />minutes and packets. <br /> <br />Restructuring Sections 5, 6, 7, and 8 <br />The primary amendment and reason for this process is due to the current structuring of permitted uses in the <br />ordinance. At this time, the ordinance “back references” the previous sections as it progresses through each <br />district. This creates confusion as residents and staff must flip back and forth and decipher what the amendme nts <br />refer to. The Planning Commission recommends listing each use in each section clearly as well as adopting a <br />new figure, 1c, to show all uses listed in a table for easy reference. <br /> <br />In addition, all references to setbacks have been located within the subsection, “Area, Frontage, and Yard <br />Requirements” for easier navigation. Fence regulations that were in these sections have been moved to the <br />existing fence regulations in Section 16.13. <br /> <br />Conditional vs Interim Uses <br />The current ordinance lists conditional and interim uses within the same section. This creates confusion for <br />residents and creates the opportunity for conflict when determining if an application should be considered <br />conditional or interim, as these two permitting types have significant differences. The Planning Commission <br />recommends listing these two separately to create a clearer application, permitting, and permitting maintenance <br />process. <br /> <br />Conditional use permits “run with the land” regardless of change of ownership. Any conditional use permit is <br />considered void if the use listed is discontinued for six months. <br /> <br />An interim use is granted to a property owner and has a predetermined expiration date (typically 3 or 5 years). <br />Interim use permit holders can renew their permits at that time following Council approval. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.