My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09.2 Joint Road Project Request for Proposal (RFP)
Laserfiche
>
City Council (Permanent)
>
Agenda Packets (Permanent)
>
2020
>
11-10-2020 City Council Meeting
>
09.2 Joint Road Project Request for Proposal (RFP)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/8/2021 4:10:59 PM
Creation date
3/8/2021 3:39:23 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
20
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
Page 9 of 19 <br /> <br />x The base map should include labels for owner name, parcel identification, <br />section-township-range-quarter-quarter-gov’t lots, subdivision plat names <br />with block and lot identification. <br />This work must be performed by or under the direct supervision of a Land Surveyor <br />licensed by the State of Minnesota. If conflicts with parcel boundaries are present, <br />the consultant should contact the Crow Wing County Survey Planning Coordinator, <br />to determine an appropriate solution. <br /> <br />2.1.10. Preliminary Right-of-Way Determination <br /> Based on the parcel breakdown described in Section 2.1.9, the consultant shall <br />determine the existing right-of-way. This determination may require some research <br />to define areas of public easement, utility easement, and/or prescriptive easement. <br />All determinations shall be documented and approved by a licensed Land Surveyor. <br />If right-of-way conflicts cannot be resolved, the consultant should contact the Crow <br />Wing County Survey Planning Coordinator, to determine an appropriate solution. <br /> <br />Using the preliminary geometric designs, the Consultant shall develop the <br />anticipated proposed right-of way and construction limits for each layout. An impact <br />analysis shall be performed to clearly identify acreage takings, damages to property, <br />and utilities impacts. This analysis will provide the Coalition with information <br />related to right of way costs and aid in determining the preferred layout. The <br />proposed right-of-way limits along with anticipated construction limits shall be used <br />as a public visual in the preferred and alternative geometric layouts. <br /> <br />2.1.11. Preferred Geometric Layout and Alternatives <br /> During the preliminary design process, the Consultant will develop a preferred <br />geometric layout and alternatives. Alternative layouts shall be considered for <br />varying design standards, geometrics, and/or substantial cost considerations. At a <br />minimum, the Consultant will provide two alternatives. One that meets State Aid <br />Design Standards and a second that meets Local Agency Design Standards. <br />Recognizing, State Aid Standard may not be relevant for all segment of roadway <br />associated with this project. The Consultant shall use data analysis, professional <br />expertise, and input from the City/Township Coalition to determine the appropriate <br />alternative layouts to meet the project needs. The geometric layouts shall be a clear <br />representation of the project design which includes design standards, horizontal <br />alignments, profiles, roadway geometry, design speed, typical sections, <br />intersections, and preliminary topographic information. These layouts shall contain <br />all right-of-way information including but not limited to the existing and proposed <br />right-of-way, parcel identification, and ownership/address information. Areas of <br />property impact shall clearly define acreage and damages to trees, structures, <br />utilities, etc. Throughout this period, the Consultant shall arrange multiple meetings <br />and establish continual communication with the City/Township Coalition as to
The URL can be used to link to this page
Your browser does not support the video tag.