My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
2009-05-18 Special Called Regular Meeting and Workshop of La Porte City Council minutes
LaPorte
>
.Minutes
>
City Council
>
2000's
>
2009
>
2009-05-18 Special Called Regular Meeting and Workshop of La Porte City Council minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/2/2016 12:07:24 PM
Creation date
7/31/2025 11:12:21 AM
Metadata
Fields
Template:
City Meetings
Meeting Body
City Council
Meeting Doc Type
Minutes
Date
5/18/2009
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
86
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
<br />(6) The permittee shall be required to repair all portions of any street across or along and <br />under which pipelines are laid and place the same in as good a state of repair and condition as <br />they were at the time the construction, repair or removal was commenced, such repairs to be to <br />the satisfaction of the city. <br /> <br />(7) Upon completion of the pipeline, the permittee shall provide the director with three as-built <br />(or record) drawings of the pipeline, showing the route, distances and shut-off valve locations. <br />These drawings shall be submitted in digital format acceptable to the city. <br />(Ord. No. 2004-2755, S 1, 7-12-04) <br /> <br />Sec. 102-242. Pipeline location. <br /> <br />(a) Where feasible, a new pipeline shall be located within existing pipeline corridors. The <br />feasibility of locating new pipelines in established corridors in the city shall be considered from <br />the perspective of the pipeline owner or operator, taking into consideration the following: <br /> <br />(1) The availability and cost of corridor space; <br /> <br />(2) The availability and cost of right-of-way to and from the corridor; <br /> <br />(3) Technical, environmental, safety, efficiency and cost issues related to building, operating <br />and maintaining both the portion of the pipeline that would be located in the corridor and the <br />lengths of pipeline required to gain access to and from routing through a corridor; <br /> <br />(4) Any delays in right-of-way acquisition or pipeline construction that may result from routing <br />through a corridor; <br /> <br />(5) The availability of an alternative right-of-way to the owner or operator; and <br /> <br />(6) All other matters that a prudent pipeline owner or operator would consider in selecting the <br />route for a new pipeline. <br />Provided that the owner or operator has considered in good faith the use of existing corridors <br />within the city, the determination of the owner or operator as to the feasibility shall be <br />determinative, unless there is clear and convincing evidence that contradicts the conclusion of <br />the owner or operator. <br /> <br />(b) When it is not feasible for a new pipeline to be located within an existing corridor, the <br />pipeline should, to the extent practical: <br />(1) Follow property boundaries of fee parcels or existing easements to avoid unnecessary <br />fragmentation of land and avoid diagonal routes that would create slivers of land between public <br />ways, except if following: <br /> <br />a. Manmade or topographical features is in the public interest; <br />b. Boundary lines or existing easements is impractical under the circumstances; <br />c. Boundary lines or existing easements poses safety concerns; or <br />d. Boundary lines or existing easements would not be feasible. <br /> <br />(2) Avoid areas of unique recreational or aesthetic importance, environmentally sensitive areas <br />and areas of historical or cultural significance, unless appropriate mitigation measures are <br />undertaken to the satisfaction of the director; and <br /> <br />7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.