My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25A - GEOFILE DATASET MAINTENANCE
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2009
>
11/02/2009
>
25A - GEOFILE DATASET MAINTENANCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/3/2012 4:14:15 PM
Creation date
10/27/2009 7:42:10 AM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Item #
25A
Date
11/2/2009
Destruction Year
2014
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
12
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
Va!leyCom Statement of Work <br />5.3 Geofile Maintenance Layers <br />The following provides a description of the Layers that GDR will maintain. <br />5.3.1 STREETS (WITH ROUTING. IF APPLICABLE) <br />Maximum <br />Limit Updates of the total number of segments in the original base map in the following quantities may <br />be performed in a Release before the Maximum Limit is exceeded, as follows: <br />• Up to 5% for Releases on a quarterly Maintenance Cycle <br />• Up to 10% for Releases on a bi-annual Maintenance Cycle <br />• Up to 15% for Releases on an annual Maintenance Cycle <br />Spatial 1. Any new segment additions will be digitized and/or corrected to the most recent aerial <br />Accuracy imagery that GDR can obtain. If roads are so new that they do not appear on any ~, <br />imagery, GDR will then add segmentation using reasonable commercial efforts with the <br />understanding that the Layer will be corrected to spatially accurate imagery in a I <br />subsequent Release when said imagery becomes available to GDR. <br />2. Any original segmentation found later to be in error in the original base map, will be <br />corrected without counting against the Maximum Limit. <br />3. GDR will not ortho-rectify an entire street fife to a completely different source data set as <br />part of a maintenance update. An example of this might be if a Licensee receives an j <br />engineer grade (1 inch accuracy) line file that they wish to transfer existing attributes to <br />This is not part of the maintenance cycle, but could be done as a different work order at <br />an additional cost. <br />Attribution 1. A 'golden" address range or point fife (such as CAD, SITUS, or MSAG data) may be <br />specified by Licensee during the initial file build. This file or files is/are used to validate <br />the deliverable street file and ensure all address and name data is contained within. <br />Customer may provide GDR with an updated version of their `golden" file for use in <br />maintenance updates; however GDR will not accept additional "golden" files or a golden <br />file that comes from a differing source with respect to the original. ~I <br />2. If a "golden" file was not provided to GDR by Licensee as part of the original <br />Specifications. none may be provided for subsequent Release unless mutually agreed in <br />writing between GDR and Licensee. Alternatively, a "golden" file may be incorporated <br />into future Specifications at an additional cost. <br />3. The unique ID field will be maintained during a maintenance update. At Licensee's <br />request. deleted segments may be provided in a separate file. New segments will be ', <br />given new ID numbers, and one part of any split segments will retain the original ID. <br />while the other split portions will receive new IDs. <br />', 4. All node, cross street. and polygon (ciry_ police, fire, EMS, etc.) attribute data will be <br />updated for each record if appropriate. ', <br />Integration <br />Scope <br />1. GDR will receive the countywide street centerline file from Santa Ana. '~ <br />2. GDR will change the format of the countywide streets to match Santa Ana streets (field <br />names. field order, field values, missing fields). <br />3. GDR will integrate the countywide and Santa Ana datasets <br />- Remove countywide streets that exist in Santa Ana street centerline layer. <br />- Edge-match the Santa Ana streets to the countywide streets. <br />- Ensure topological/attribute consistency such that routability across dataset <br />borders are maintained. <br />- Apply left/right Santa Ana FRDs values to countywide streets, if these values do <br />_,_ not exist in the countywide dataset. <br />8 Digital Dnve. Suite 200. Novato. CA 94949 • (888) 654-4GDR (4437} • Phone (ai5) 884-4437 • FAX {415) 884-4407 <br />www.adccom <br />Page 3 of 7 <br />25A-8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.