My WebLink
|
Help
|
About
|
Sign Out
05
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2023
>
091923 SPECIAL
>
05
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/13/2023 2:06:04 PM
Creation date
9/13/2023 1:53:23 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
9/19/2023
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
62
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
Scope of Work <br /> Preparation of Plans,Specifications and Estimates <br /> Sunol Boulevard/I-680 Improvements Project <br /> August 21,2023 <br /> • Provide timely written reports to the City on communications between AECOM <br /> and Caltrans staff. <br /> The Encroachment Policy Variance Request (EPVR) that was completed during the <br /> Project Approval/Environmental Document phase will be updated and resubmitted, for <br /> final approval. <br /> Task 7.2 Right of Way Engineering <br /> 7.2.1 Record Boundary Land Net <br /> Utilizing current CT Record Maps (R-maps) and Survey Maps (S-maps), the current <br /> Interstate 680 ROW will be calculated and placed into the record boundary land net based <br /> on the location of the recovered ROW monuments. Title reports and associated <br /> supporting documents for each of the 7 acquisition parent parcels will be obtained, <br /> cataloged, and organized. The record boundary and plottable easements for each parent <br /> parcel will be calculated and placed into the record boundary land net. Selected Records <br /> of Survey, Parcel Maps, Final Maps, and other record documents will also be calculated <br /> and included in the record boundary land net, as appropriate. Following completion of <br /> the record boundary land net, a resolved boundary land net will be prepared, utilizing the <br /> recovered ROW monuments to determine each resolved boundary and easement line. <br /> 7.2.2 Base Mapping <br /> Upon completion of the resolved boundary land net, the Base Mapping deliverable will <br /> be prepared. This proposal assumes a maximum of three (3) sheets will be required <br /> although the final sheet count will be determined just prior to this phase of the project. <br /> The Base Mapping will show the applicable CT ROW, all parent parcel boundaries, all <br /> plottable easements for each parent parcel, and other required data. The Base Mapping <br /> will be submitted to CT D4 personnel for review and acceptance. Title reports, <br /> supporting documents, and other applicable record documents will be provided to CT D4 <br /> with the Base Mapping deliverable. <br /> 7.2.3 Appraisal Mapping <br /> Upon CT acceptance of the Base Mapping, preparation of the Appraisal Mapping will <br /> begin. This proposal assumes a maximum of three (3) sheets will be required although <br /> the final sheet count will be determined just prior to this phase of the project. As <br /> determined by the civil engineering team, linework representing the required acquisitions <br /> will be incorporated into the base mapping land net model. The Appraisal Mapping will <br /> include the sub-parcel identifier for each acquisition parcel, the acquisition type, and the <br /> area of each sub-parcel, with each sub-parcel uniquely color-coded per parent parcel. <br /> Additional Appraisal Mapping items include but are not limited to parent parcel <br /> boundaries and easements, adjacent owner parcel boundaries and easements, city ROW's, <br /> prior CT acquisitions, existing topography, existing CT ROW, proposed CT ROW, and <br /> proposed design lines. Closure calculations for each acquisition sub-parcel, each design <br /> line, and the final proposed CT ROW will be performed. The Appraisal Mapping and <br /> closure <br /> Page 27 of 42 <br />
The URL can be used to link to this page
Your browser does not support the video tag.