My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
11-10-2009 Council Work Session Packet
Orono
>
City Council
>
2009
>
11-10-2009 Council Work Session Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/8/2015 3:58:03 PM
Creation date
7/8/2015 3:57:58 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
57
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).
Show annotations
View images
View plain text
1245 Arbor Tax Forfeiture <br /> November 4,2009 <br /> Page 2 <br /> May 2009 revisions to the State Statutes re: nonconformities in the Shoreland suggest that these <br /> parcels may have to be considered as two separate building sites (Attachment E). However, as <br /> individual parcels each has severe zoning limitations, in part due to their location in the Shoreland <br /> District. Each would require lot area and setback variances, and potentially variances for hardcover <br /> (250-500' zone allows 30% HC, x 14,000 s.f. = 4,200 sf allowed Hardcover) and structural <br /> coverage (14,000 sf x 15% = 2100 s.f. allowed Structural Coverage). The Statutes limit hardcover <br /> to 25%, more restrictive than the City ordinance, which yields about 3,500 sf. This is likely <br /> adequate to construct a small home & garage of 2000 sf footprint with 1500 sf far driveways, <br /> sidewalks, decks, etc.; but nothing more than this modest size home. (see Attachment F) <br /> I will have Soren review the Statutes and advise as to whether we are required by law to grant the <br /> area, width and setback variances needed to construct homes on each parcel. I do not believe we <br /> would be obligated to approve lot coverage or hardcover variances. <br /> The question at this time is whether we should release this property to the County with a <br /> stipulation that it be sold as a single 0.64 acre building site; or as two 0.32 acre building sites; or as <br /> unbuildable land only available for purchase by an adjacent owner. Some factors to consider: <br /> ► It is not adjacent to a park, but is surrounded by homes, and would not be conducive to retain <br /> for City parkland or open space. <br /> ► It is not topographically situated so as to be useful for stormwater management, and does not <br /> contain any wetlands or other features we would specifically want to preserve. <br /> ► While the property had just one house on it in the past, placing two homes on it would not be <br /> totally out of character with the neighborhood, as long as those homes are not overbuilt for the site. <br /> ► But, the City has held firm on not allowing the Crystal Bay neighborhood to get denser, which <br /> is why we never changed the 2-acre zoning to match the typical 1/2-acre lot sizes in the <br /> neighborhood. <br /> ► This would be a neighborhood where we might expect to be able to create some affordable <br /> housing; however, the assessed land value for virtually identically shaped/sized lots across the <br /> street is $160,000 for just the 100x 140' lot. By the time a home is constructed on one of these <br /> parcels, the assessed land & building value would likely be in the high $200s or more. The current <br /> "affordability" level is in the low $200s. <br /> ► Neighborhood reaction to allowing both parcels to be built on would likely be negative. <br /> ► Another option to consider is to allow the parcels for sale only to an adjacent owner. There are <br /> homes on each of the two adjacent lots to the north, each of which is about 0.24 acres in area. <br /> These adjacent owners might be interested in acquiring the parcels as additional land. <br /> Council is asked to discuss the issue and provide as much direction to staff as <br /> possible. We must respond to Hennepin County on this by December 7. <br />
The URL can be used to link to this page
Your browser does not support the video tag.