My WebLink
|
Help
|
About
|
Sign Out
ORD 1732
City of Pleasanton
>
CITY CLERK
>
ORDINANCES
>
1701 - 1800
>
ORD 1732
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/30/2023 4:24:23 PM
Creation date
3/8/1999 5:41:57 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
ORDINANCES
DOCUMENT NO
ORD 1732
Tags
Ordinance
Description:
Ordinance
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).
View images
View plain text
The City shall collect such amounts in conjunction with each <br />buildin~ permit requested by a Contributing Project. The <br />City shall use its best efforts to prevent Contributing <br />Projects from receiving any City approvals without the <br />condition that they make such payments and shall not issue <br />permits, licenses or consents for development of the <br />Contributing Projects without such payments being made (or <br />committed to, as applicable). If, for any reason, the City <br />grants an approval to a Contributing Project but voluntarily <br />elects not to collect or impose such payment in respect of <br />the Net Actual/Estimated Traffic Mitigation Improvements <br />Costs, then the City shall, for all purposes, be deemed to <br />have collected the required payment from the Contributing <br />Project and shall, accordingly, be obligated to advance from <br />the City's general funds the full amount thereof for the <br />purpose of paying such Traffic Mitigation Improvements Costs <br />and/or making a payment of Reimbursement Fees to Developer <br />hereunder, as applicable. To the extent that Reimbursement <br />Fees are owed to Developer (or any other Contributing <br />Project which may have advanced more than its applicable <br />percentage share of Traffic Mitigation Improvements Costs), <br />then the City shall be obligated to pay such Reimbursement <br />Fees owed, subject to the following: (i) payments collected <br />from each Contributing Project shall first be applied <br />payment of Actual Traffic Mitigation Improvements Costs'+then <br />payable in orderto maintain LOS "D" at the required <br />intersections as stated above; and (ii) any remaining funds <br />collected shall be applied in payment of Reimbursement Fees, <br />with such payments to be allocated among Developer and other <br />Contributing Projects owed Reimbursement Fees in proportion <br />to the amount of such Reimbursement Fees owed to each such <br />person. Notwithstanding any termination of this Agreement, <br />the City shall continue to pay to Developer Reimbursement <br />Fees which may be owed to Developer from payments later <br />collected by the City from other Contributing Projects, <br />until Developer's Reimbursement Fees have been fully repaid. <br /> <br /> (f) This subparagraph sets forth several examples of <br />the manner in which Reimbursement Fees would accrue and, <br />ultimately, be paid hereunder. The addition of the Sears <br />department store shall trigger the need to widen Canyon Way <br />in the form of the Traffic Mitigation Improvement listed as <br />Item A-1 on Exhibit D. Assuming that the Actual Traffic <br />Mitigation Improvement Costs therefor are $500,000, then <br />Developer (and/or Sears, as its successor) would be required <br />to pay to the City $374,750 (i.e., the Actual Traffic <br />Mitigation Improvement Costs less the Existing Funding <br />Sources totalling $125,250). Said payment would generate a <br />Reimbursement Fee to Developer in the amount of $220,450 <br />calculated as follows: <br /> <br /> (i) 178,000 sq. ft. (Sears store) divided by <br /> 558,000 sq. ft. (total Project) yields an allocable <br /> share of the total Project of approximately 32%; <br /> <br /> -7-. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.