My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 01/06/1998
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
1998
>
Agenda - Planning Commission - 01/06/1998
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:09:18 AM
Creation date
9/18/2003 9:43:08 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
01/06/1998
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
44
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
Z.B. November 25, 1997 Page 3 <br /> <br />considered under the county ordinances then in effect. <br /> The developer had a vested right to have its proposal considered under the <br />county's zoning regulations, and if they were met, to have the city's approval. <br />The city was correct that the PUD was not in effect when the developer filed its <br />subdivision application; the PUD was still only a proposal. But the county's <br />zoning ordinances that were in effect alIowed the developer to show its proposed <br />PUD complied with various land use regulations. If the county agreed, it would <br />have had to adopt an ordinance granting a preliminary PUD. <br /> The city's claim that the vested rights doctrine didn't apply because a PUD <br />required a zoning amendment if the application was approved was irrelevant. <br />The developer didn't claim the city had to approve its plan outright, it claimed <br />only the right to have its application considered under the county ordinances <br />that allowed for townhouses in a PUD. <br /> see also: Noble Manor Co. v. Pierce County, 9J3 P..2d 417 (]996). <br /> <br /> Subdivision m Developer says commission relied on neighbors' testimony <br /> rather than substantive evidence <br /> Metropolitan Dade County v. Sportacres Development Group Inc., 698 <br /> So.2d 281_ (Florida) 1997 <br /> Sportacres Development Group Inc. owned a 107-acre abandoned golf <br /> course zoned single family in Dade County, Fla. It wanted to deveIop a 372- <br /> unit subdivision with an 18-acre lake on the property. <br /> Sportacres' property was bounded on two sides by property developed with <br /> multifamily attached residences and on two sides by property developed with <br /> s ingle-family detached houses. ImmediateIy north of the single-family residential <br /> area next to Sportacres' property was a large area being developed for apartment <br /> complexes. <br /> Sportacres filed a zoning application seeking a use variance to allow the <br /> excavation of an 18-acre lake and a variance of lot area and frontage <br /> requirements for its proposed subdivision. It sought permission to develop the <br /> subdivision with lots varying in frontage from 50 feet to 74.99 feet in an area <br /> with a 75-foot minimum frontage requirement, and lots on cul-de-sacs with a <br /> minimum frontage of 33 feet where 50 feet was required. It also sought a <br /> minimum lot area of 4,500 square feet where 7,500 square feet were required. <br /> The Dade County Zoning Appeals Board approved Sportacres' application <br />with 39 conditions. A group of neighbors appealed to the county commission. <br /> The neighbors testified that with the lake and the variances, the subdivision's <br />lots would be of substandard size and would, therefore, be incompatible with <br />the surrounding neighborhood. They apparently claimed Sportacres' property <br />was subject to a restrictive covenant requiring minimum lots of 7,500 square <br />feet. The neighbors also claimed the lake would pose a health hazard, and said <br />the substandard lots would have a negative effect on their property values. <br /> Sportacres claimed the neighbors' testimony was not competent. It als° <br />showed its property was not subject to a restrictive covenant requiring a <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.