My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 1999/08/02
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
1990-1999
>
1999
>
Agenda Packets - 1999/08/02
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:49:19 PM
Creation date
6/12/2018 9:56:01 AM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
8/2/1999
Supplemental fields
City Council Document Type
City Council Packets
Date
8/2/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
81
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
(b) To the extent known, the tentative locations. and estimated beginninE. and ending <br />dates for all Projects contemplated for the five years following the next calendar <br />year (in this section, a "Five-year Project"). <br />The term "project" in this section shall include both Next -year Projects and Five-year <br />Projects. <br />By January i of each year the Director will have available for inspection in the Director's <br />office a composite list of all Projects of which the Director has been informed of the <br />annual plans. All Registrants are responsible for keeping themselves informed of the <br />current status of this list. <br />Thereafter. by February 1. each Registrant may change any Project in its list -af Next -year <br />Projects, and must notify the Director and all other Registrants of all such changes in said <br />list. Notwithstanding the foregoing, a Registrant may at any time join in a Next -year <br />Project of another Registrant listed by the other Registrant. <br />Subd. 2. Additional Next -year Projects: Notwithstanding the foregoing, the ?director will <br />not deny an application for a Right -of -Way Permit for failure to include: a project in <br />a plan submitted to the City if the Registrant has used commercially reasonable <br />efforts to anticipate and plan for the project. <br />910.08, PERMIT REQUIREMENT: <br />Siibd. 1. Permit Required: Except as otherwise provided in this Code, no Person may Obstruct <br />or Excavate any Right -of -Way without first having obtained the appropriate Right -of - <br />Way Permit from the Director to do so. <br />(a) Excavation Permit: An Excavation Permit is required by a Registrant to Excavate that <br />part of the Right -of -Way described in such perHt and to hinder free and open passage over <br />the .specified portion of the Right -of -Way by placing Facilities described therein, to the <br />extent and for the duration specified therein. <br />(b) Obstruction Permit: An Obstruction Permit is required by a Registrant to hinder free and <br />open passage over the specified portion of Right -of -Way by placing Equipment described <br />therein on the Right-of-way, to the extent and for the duration specified therein. An <br />Obstruction Permit is not required if a Person already possesses a valid Excavation Permit <br />for the same project. <br />Subd. 2. Permit Extensions: No Person may Excavate or Obstruct the Fight -of -Way beyond the <br />date or dates specified in the permit unless such Person (i) makes a S upplementary <br />Application for another Right -of -Way Permit before the expiration o r the initial permit, <br />and (ii) a new permit or permit extension is granted- <br />Subd_ 3. Delay Penalty: In accordance with Minnesota Rule 7819.1000 sutp. 3 and <br />notwithstanding subd. 2 of this section, the City shall establish and impose a Delay <br />SJR-163902 t0 <br />MU210-14 <br />169-d vi/11'd SIN 01EILM HAM ! AHNNN-Mi O2:91 66-Bi-20 <br />
The URL can be used to link to this page
Your browser does not support the video tag.