Laserfiche WebLink
<br /> Section 5: Proposed Scope & Techniques 17 <br /> Digital Checks of Mapped Features' Themes <br /> Each layer will be isolated and checked for continuity i.e., must 'stand by itself without gaps or duplicates. <br /> We will also export the layer definition table, compare it against the specifications document, and remove, <br /> rename, or revise any that do not match. The same process will be used for symbol and text style <br /> definitions. System variables (e.g. ltscale, viewres, visretain, limits, views, etc) will be similarly checked <br /> against the specifications document. A final purge will eliminate extraneous data in the files' definition <br /> table. <br /> Thematic Mapping and Database Checking <br /> Two standard methods are used to check for database consistency. First, an independent database is joined <br /> with the feature's attribute table. This will provide two important QC evaluations: 1) lengths will be <br /> compared and delta values calculated and added to the feature's attribute table as a percentage difference. <br /> This will be extracted into a report and supplied to the City with discrepancies of greater than 10% <br /> highlighted; 2) ID numbers without a matching ID in the source table will drop out (full outer join), <br /> creating a subset table of missing labels. These will be individually checked and updated. <br /> QC of Feature Attributes <br /> A more difficult problem to QC is determining typographical errors for feature attributes. Tests will <br /> include: 1) Duplicates Test, 2) Sequence Test, and 3) Unmatched errors test (compare databases, finds <br /> updates individual typos). For each list, each potential will be researched by comparing the coverage to the <br /> source map. If the problem cannot be resolved (i.e. insufficient map information), an APN Exceptions List <br /> will be created and provided to the City. <br /> Lynx Technologies City of Redwood City Street Lighting GIS Project <br />