My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
8/8/1995
CBCC
>
Meetings
>
1990's
>
1995
>
8/8/1995
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/23/2015 12:05:12 PM
Creation date
6/16/2015 2:43:55 PM
Metadata
Fields
Template:
Meetings
Meeting Type
Regular Meeting
Document Type
Minutes
Meeting Date
08/08/1995
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
65
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
proliferation inevitably puts more wear on unpaved roads and either <br />degrades the roadway or requires more maintenance. <br />*Paving 62nd Avenue <br />The subject property and all other parcels on the east side of 62nd <br />Avenue have benefitted from the public road right-of-way <br />established by the Sunniland Homesites plat. Over the years, <br />grandfathered -in and lot split homesites along 62nd Avenue have <br />been allowed to be developed. Now, a subdivision is proposed and <br />a variance has been requested, raising this central question: <br />should 62nd Avenue be paved? If 62nd Avenue is never to be paved, <br />then the county's subdivision paving requirement makes sense by <br />limiting the number of homesites and residents using the roadway so <br />that road degradation and maintenance costs are minimized. The <br />county's subdivision paving requirements also make sense if the <br />road is to be paved at some point in the future, since the <br />requirement causes the subdividers to initiate either a petition <br />paving or a forced assessment. <br />Because the site is located at the end of 62nd Avenue, about 1,200' <br />of the road would need to be paved to provide paved access from the <br />Ferguson's proposed lots to 33rd Street. Based upon county <br />engineering's rough estimates for petition paving projects, paving <br />the road to county standards would cost $40 - $50 per linear foot. <br />Therefore, paving a 1,200' segment could cost $48,000 - $60,000. <br />Using the general petition paving formula, where the county pays <br />25% of the cost and property owners on each side of the road split <br />the remaining 75%, the petition paving cost for a property owner <br />could run $1,500 - $1,875 per 100' of frontage. <br />As previously described, there are generally 3 alternatives for <br />funding the paving of 62nd Avenue: <br />(1) The developer or a group of developers pays for the paving <br />cost. <br />(2) A petition paving program is initiated and approved by the <br />county. <br />(3) An involuntary paving assessment is approved by the county. <br />In the past, some subdivision developers have used the petition <br />paving process to help pay for paving roads in existing <br />subdivisions. The Fergusons' primary contention is that the entire <br />cost of the required road paving is not feasible for them*to bear <br />for their proposed 2 lot subdivision. Staff agrees. However, the <br />subdivision should not be approved without a mechanism in place <br />(such as an approved petition paving project or approved <br />involuntary paving assessment) to guarantee the paving and commit <br />the developers to paying their fairshare for the paving. <br />*Variance Review and Consideration <br />Section 913.11 of the subdivision ordinance gives the Board clear <br />guidance in its review and consideration of a variance request. <br />According to Section 913.11, the Board shall not approve a variance <br />unless it finds all of the following: <br />(A) The particular physical conditions, shape, or topography of <br />the specific property involved would cause an undue hardship <br />to the applicant if the strict letter of the land development <br />regulation is carried out; _ <br />19 <br />August 8, 1995iri <br />
The URL can be used to link to this page
Your browser does not support the video tag.