Laserfiche WebLink
unicipal Consent <br />HP <br />i No., <br />oping / Subject Guidance <br />Also, main <br />A �1 <br />ce activities do not trigger the need <br />Examples <br />Permanent Eas <br />(because <br />is (such as <br />ake permanent right-of-way <br />Mn /DOT <br />ideal consent. <br />Easements) require municipal consent <br />oundabouts are used for traffic regulation and as a safety <br />exceptions that do not require Municipal Consent even if they involve <br />e, and thus are <br />'`� nent <br />Roles and Procedures <br />Municipal consent should only be requested from a city if it is required. (See Threshold Criteria <br />above). <br />Sometimes a city may choose to waive municipal consent on a specific project. In that case the <br />city council must pass a resolution clearly identifying the project and waiving its right to <br />municipal consent for that project. However, the typical municipal consent process is as outlined <br />below. <br />Procedure (for obtaining municipal consent) <br />1. Mn /DOT (District) submits to the city the final layout with a letter requesting city <br />approval. The letter includes a good faith cost estimate of the city's share of the <br />project's cost and the following (either in the letter or in an attached report): <br />• project purpose <br />• route location <br />• short description of the proposed design of the highway <br />• any additional supporting data <br />2. City schedules and holds public hearing (within 60 days of submittal). <br />City must schedule within 15 days of receiving Mn /DOT's request for approval and <br />must give 30 days public notice. <br />3. City passes resolution approving f disapproving (within 90 days of public hearing). <br />After 90 from the date of the public hearing, if the city has not passed a resolution <br />disapproving the layout, the layout is deemed approved. <br />2 of 5 <br />3 <br />