Laserfiche WebLink
C. The most current imagery available is used to update Layers for each Release; however, this <br />imagery is not delivered as part of a Release. Licensee may purchase the imagery from <br />GDR, if available, at an additional cost. <br />D. Layers will by modified by GDR in accordance with the following terms and limitations (please <br />select only those Layers applicable to the Specifications): <br />Limit Updates of the total number of segments in the original base map in the following quantities <br />may 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 <br />Accuracy recent aerial imagery that GDR can obtain. If roads are so new that they do <br />not appear on any imagery, GDR will then add segmentation using <br />reasonable commercial efforts with the understanding that the Layer will be <br />corrected to spatially accurate imagery in a subsequent Release when said <br />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 file to a completely different source data <br />set as part of a maintenance update. An example of this might be if a Licensee receives <br />an engineer grade (1 inch accuracy) line file that they wish to transfer existing attributes <br />to. This is not part of the maintenance cycle, but could be done as a different work <br />order at an additional cost <br />Attribution 1. A "golden" address range or point file (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 <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 <br />in 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 (city, police, fire, EMS, etc.) attribute data will be <br />updated for each record if appropriate <br />r ire or <br />Limits 1. A complete rebuild of a response polygon Layer is considered part of a Release as long <br />as it does not occur more often than once every 2 years. If Licensee has the need to <br />completely rebuild polygon boundaries more often than once every 2 years, this may be <br />incorporated into future Specifications at an additional cost <br />2. Geometry changes for up to 40 % of the records in a response boundary file may be <br />performed before the Maximum Limit is exceeded <br />8 Digital Drive, Suite 200, Novato, CA 94949 • (888) 654-4GDR (4437) • Phone (415) 884-4437 • FAX (415) 884-4407 • www.gdr.com <br />4 <br />