My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
DV-19-00001 Marian Meadows Development Agreement Master File
>
Meetings
>
2020
>
10. October
>
2020-10-06 2:00 PM - 2:00pm Public Hearing
>
DV-19-00001 Marian Meadows Development Agreement Master File
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/1/2020 1:55:20 PM
Creation date
10/1/2020 1:41:42 PM
Metadata
Fields
Template:
Meeting
Date
10/6/2020
Meeting title
2:00pm Public Hearing
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Alpha Order
a
Item
Public Hearing to Consider the Marian Meadows Development Agreement (DV-19-00001)
Order
1
Placement
2:00pm Public Hearing
Row ID
67284
Type
Hold Public Hearing
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.
/
464
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Exhibit D – Community Standards & Guidelines <br />Page 3 of 5 <br /> <br /> <br />* The 4 large parcels in the eastern region of the project are a-typical for this PUD <br />and region and set apart from the main function of the Marian Meadows community. <br />These parcels may share in some common facilities and shared interest of the general <br />plat but these parcels will be treated uniquely due to their size, recreational/tourism <br />possibilities and commercial agricultural/forestry opportunities. Measures will be in <br />place to protect the common interest of the community but also allow for these lots to <br />function independent of the PUD and associated CC & R’s for the overall Marian <br />Meadows plat. <br /> <br />5. Community Buildings – (pool bldgs., mail fac., solid waste/recycling, etc.) <br /> (a) Setbacks – 10’ all sides <br /> (b) Height – 35’ <br /> (c) Use of onsite septic per KCC or inclusion with the RV Complex LOSS. <br /> (d) All construction will comply with KCC unless specifically addressed within <br /> the section. <br />6. R V Complex. <br /> A. Storage Units – (see Exh. D-RV Unit Elev.) <br /> (a) Setbacks – 15’ from natural buffer areas <br /> (b) One single tract with building pads to be determined. Illustration shows <br /> conceptual layout with individual 4 unit buildings and larger single <br /> building design. (See Exh. D – RV layout 1 & 2) <br /> (c) 6’ security fencing with concertina wire at RV Complex perimeter. <br /> (d) Units will be equipped with fire sprinklers, gas and CO2 monitors. <br /> (e) R V Complex will be privately owned storage operations focusing on <br /> Recreational Vehicle usage. <br /> (f) are partially located within restricted Airport Safety Zone (see Exh. D–ASZ-4) <br /> (g) Limited exterior uses in storage (ASZ-4) zone. <br /> (h) No overnight use within storage (ASZ-4) zone. This is inclusive of any <br /> storage unit or the storage unit areas. Any overnight use will be required to <br /> take place in the campground or RV Pad area. <br /> (i) Outside storage would be limited, seasonal and primarily apply to short term <br /> storage for vehicles to be serviced. In most cases, this would be within the <br /> gated portion of the complex. <br /> (j) Storage unit use would be limited to fee simple ownership, tenants and guest. <br /> (k) Camping and RV Park usage will include restrictions for duration, seasonal <br /> uses, etc. Use of this area will be by owners/tenants and guest of Storage <br /> Complex. <br /> (l) all operations within the R V Complex will be required to be connected and <br /> serviced by the LOSS system within the complex. <br /> B. RV Commercial Applications* (see Exh. D -Commercial Location) <br /> (a) in place for servicing, monitoring and oversight of RV Complex operations.
The URL can be used to link to this page
Your browser does not support the video tag.