My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
9A - Metes and Bounds Subdivision
Laserfiche
>
Planning & Zoning
>
Agenda Packets
>
2008
>
04-17-2008 Planning Commission Meeting
>
9A - Metes and Bounds Subdivision
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/6/2016 3:56:15 PM
Creation date
6/6/2016 3:55:08 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
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
Unit Development shall have a minimum of 33 feet of frontage on a public right- <br /> of-way. <br /> Staff Findings:The Staff provides the following findings of fact for consideration: <br /> i. The property is properly zoned Commercial and is suitable in its natural state for — <br /> commercial uses as permitted in the C zone. The property has been used for <br /> commercial purposes. <br /> 2. There are not any significant natural features, such as steep slopes or wetlands <br /> that would constrain future development on these properties. <br /> 3. The Gravel driveway on Tract A encroaches upon the side yard setback.The other <br /> structures located on this property are conforming as they meet all required <br /> setbacks and the total impervious falls under the 25%maximum allowed. — <br /> 4. Each of the lots in the proposed subdivision has a separate on-site sewage <br /> treatment system. <br /> 5. Both Tract A and Tract B have an on-site well for a water supply source. <br /> 6. The applicant is not proposing any provisions for water-based recreation as these <br /> properties are not adjacent to any water bodies. <br /> 7. Both lots meet the minimum buildable lot size of 20,000 square feet in the C <br /> zone,with Tract A being 21,o61 square feet and Tract B being 40,521 square feet. — <br /> Tract C would be a non-conforming lot for the sole purpose of ingress,egress,and <br /> utility easement. <br /> 8. Tracts A and B meet the minimum lot width of 50 feet, with both Tract A and _ <br /> Tract B being just over 117 feet wide. <br /> 9. Tracts A and B meet the impervious coverage limit of 25% for the Commercial <br /> zone, with Tract A having approximately 23.8% coverage and Tract B currently <br /> having about 12.1%coverage. <br /> 1o. The proposed lot layouts are compatible with the existing layout of adjoining <br /> properties and the proposed lot lines are parallel and perpendicular to existing lot <br /> lines.Future development will not be constrained by the proposed lot layouts. _ <br /> 11. The proposed side lot line is at right angles to the existing road line and the <br /> property line of the adjacent property. <br /> 12. Both Tract A and Tract B meet the minimum frontage on public right-of-way <br /> requirement of 33 feet,with the subdivision of Tract C being reserved for ingress — <br /> and egress for both Tracts A and B and lands to the west of the subject property. <br /> Tracts A and B would each own an undivided one-half interest in Tract C. <br /> Planning Commission Direction: The Planning Commission may approve the metes <br /> and bounds subdivision, develop findings to deny the metes and bounds subdivision, or <br /> table the subdivision request to gather additional information on which to base a — <br /> decision or to provide the applicant time to modify the proposal. <br /> Staff Recommendation: Staff is recommending approval of the metes and bounds <br /> subdivision along with the following conditions: <br /> 1. The owners of Tracts A and B shall submit a common ownership and <br /> maintenance agreement of Tract C to the City. <br /> 2. The gravel driveway on Tract A shall be reduced in such a way so not as to — <br /> encroach upon the side yard setback. <br /> Pequot Lakes Staff Report 9(a)-3 <br /> April 17,2Oo8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.