My WebLink
|
Help
|
About
|
Sign Out
Home
Search
01/08/2003 P&Z Minutes
LinoLakes
>
Advisory Boards & Commissions
>
Planning & Zoning Board
>
Minutes
>
2003
>
01/08/2003 P&Z Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/16/2014 9:53:13 AM
Creation date
4/16/2014 9:52:48 AM
Metadata
Fields
Template:
P&Z
P&Z Document Type
P&Z Minutes
Meeting Date
01/08/2003
P&Z Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
35
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
Planning & Zoning Board <br />January 8, 2003 <br />Page 16 <br /> APPROVED MINUTES <br />1. The street jog introduces an additional c onflict point for local traffic entering and <br />exiting Century Trail. Stop signs for Ca rl Street, both east and west, is the <br />preferred option to interrupt traffic and allow for safer traffic movements between <br />these two streets. <br /> <br />2. Residents within Century Farms North wishing to proceed to an easterly <br />destination will not be discouraged from us ing Carl Street due to the street jog. <br />Rather, it just introduces another unsafe turning movement within a distance of <br />150 feet between two local streets. <br /> <br />3. It is important to look at the proposed pr eliminary plat within the context of the <br />larger area. Recognizing that Carl Street provides an access point to the east, and <br />Century Trail will provide for connections into adjoining undeveloped properties. <br />In this respect, a safer four-way intersecti on at Carl Street a nd Century Trail is a <br />preferred traffic design in that it reduces the number of conflict points along <br />Century Trail. The two-way stop will provide an interruption of traffic on Carl <br />Street, providing safer access to these str eet corridors. In this respect, staff <br />believes that the four-way intersection with two stop signs offers a more effective <br />traffic calming element than the street jog currently proposed. <br />Condition 13. Lot 4, Block 4 be converted from an Airpark lot to a traditional single <br />family lot. <br />Condition 14. Lot 9, Block 4, an Airpark lot, be eliminated, combined with the adjacent <br />traditional single-family lots to the north to allow the creation of a buffer yard. <br />Applicant’s Response: Based on informal comment s received from the Planning and <br />Zoning Board supporting the existing lot confi guration, they have not made any changes <br />to this and respond to these conditions. <br />Staff’s Response: Staff is still concerned regard ing the compatibility of the traditional <br />and airport lots in this area of the project, specifically to the following areas: <br />1. The introduction of the hangars and airpor t traffic on Lots 4 and 9, Block 4, will <br />introduce incompatible land use relationship with Lots 5, 6, and 7 in the same <br />block. It does not appear, based on the s ite plan, that there is adequate space <br />between the traditional lots and the airpor t lots to properly screen or buffer the <br />introduction of airplane hangars, taxiways , and airplane traffic onto this area. <br />Staff believes that this relationship is not a compatible land use relationship and <br />should not be encouraged. <br /> <br />2. Review of the preliminary plat indicates that Lot 9 and portions of Lots 6 and 7 <br />contain a stand of oak trees that have been identified by the Environmental Board <br />to be saved. This significant oak stand will be disturbed with the construction of <br />the cul-de-sac to serve Lot 9 as well as the house placement, hangar placement, <br />and any driveway construction. Consis tent with the Environmental Board <br />recommendation, staff agrees that this significant oak stand should be saved as
The URL can be used to link to this page
Your browser does not support the video tag.