My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
City Council Minutes 1999 09 07
PORTAL
>
CITY COUNCIL RECORDS
>
MINUTES (45.090)
>
1970-1999 City Council Minutes
>
1999 City Council Minutes
>
City Council Minutes 1999 09 07
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2021 2:36:45 PM
Creation date
2/3/2004 2:19:31 PM
Metadata
Fields
Template:
City Council Records
Doc Type
City Council Minutes
Signed Date
9/7/1999
Original Hardcopy Storage
2E4
Supplemental fields
Test
CCMIN 1999 09 07
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
42
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
Mayer asked Light for clarification that it would fall upon Council to define these terms. <br />He questioned whether Council could determine tonight whether the project doesn't <br />really meet the criteria. <br /> <br />Light replied that for Council to adopt a definition of any particular terms for general <br />application would require amending the 1041 Ordinance. He explained that in drafting <br />the 1041 regulations last fall, one of the objectives was to make the interchange criteria <br />self-executing. This was to cause a permit process to automatically kick in without <br />having the need for an affirmative act by Council whenever there was a 'proposed' <br />interchange involving at least one arterial highway. He stated that Council could direct <br />that the Highway 42 and US 36 interchange is not proposed for the purposes of this <br />application, however, he felt that it would only affect this application for a short period of <br />time. He stated that Council would need to decide at some point when the 1041 process <br />would kick in for developments around that interchange, wherever it may eventually end <br />up. <br /> <br />Mayer agreed that Council needs to define some terms in order to provide a clear <br />understanding of what they mean. He apologized to the applicant for getting caught up in <br />this. He asked Light for clarification that everything is hinging on whether the connection <br />is considered proposed as of yet. <br /> <br />Light replied, yes. He explained that the one consideration that is mostly in Council's <br />control is the definitions of interchange and arterial highway. <br /> <br />Mayer questioned whether or not the interchange had been proposed. He stated that <br />having the 1041 process concurrent with the PUD process would make more sense. <br /> <br />Keany asked Light whether 96th Street is considered an arterial or whether Council was <br />strictly discussing the connection where it meets with Highway 42, therefore, this project <br />would fall within a mile of that connection. <br /> <br />Light replied, that, for purposes of 1041 regulations, the City is interested in the point of <br />the interchange and a one-mile radius around it. <br /> <br />Keany explained that the Intergovernmental Agreement states that an interchange will be <br />built, however, the location of the interchange has not been determined. He questioned <br />how Council could apply that definition to this project under the circumstances. <br /> <br />Light replied that the consequence will be that when the applicant pulls their building <br />permits and begins to expend funds in reliance of those building permits, the City will not <br />be able to come back with the 1041 process. He explained that if the applicant expands or <br />amends the project, they might be required to apply for a 1041 permit. He stated that if <br />the project is approved, once the applicant starts to pull building permits, they would <br />have, under the common law, a right to proceed as approved, without any additional <br />regulatory hurdle. <br /> <br />19 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.