Agmt03 Lynx Technologies - Laserfiche WebLink

Browse Search

Section 5: Proposed Scope & Techniques 16 4) Quality Control Communication Our quality control (QC) and quality assurance (QA) procedures are thorough and extensive starting with strong communication with the City GIS Coordinator and technical staff. Specifically, we propose to have montWy meetings that will include: I) written status report, 2) current project schedule, 3) level of effort and cost breakdown. Periodically we will include sample products (digital and hardcopy) that demonstrate progress and challenges that may arise. We also propose to meet with technical staff on as-needed basis but at least monthly. The objective of these meetings is to apprise City staff of any technical issues that may arise, and use their expertise in resolving solutions. We will be providing check plots and preliminary digital data constantly and therefore, will use this forum to discuss potentially systemic problems and solutions, and provide feedback on specific issues. Documentation The project will begin with a Specifications Document that details: 1) cartographic conventions (e.g. symbology, layer naming conventions, linetypes, annotation characteristics), 2) feature attributes, and 3) preliminary database design criteria will be submitted at the very beginning of the project. This document will form the foundation the project and needs discussion and approval in draft form at initial technical meetings. It is however, a 'living' document and therefore, will change over the course of the project. Each change will be highlighted in status reports at technical meetings. Technical Approach General We have constructed a suite of in-house utilities that standardize the data entry. For example, we have a standard template that defines the domains of both physical and descriptive attribute characteristics. We have also created custom routines that will help reduce cost and the likelihood of typographical errors. We use 100% checking for our quality control, and generally do not employ statistical methods because of the broad-based assumptions that are required. Topological Testing Coordinate errors are tested using two independent methods: once in AutoCAD Map, and again in Arclnfo. AutoCAD Map has excellent automatic coordinate evaluation and cleanup routines, but in our experience, often overlooks many errors. ArcInfo does not have the elegance of AutoCAD, but is virtually faultless. All network topologies will have a direction arrow generated for each segment. This will test that segments are digitized in the proper direction. Topologies will be tested dangles. It is our policy not to accept any coordinate errors even if they do not represent a topology error. For example, an overshoot, or duplicate arc will not generate a topology error but will not pass our quality control. Moreover, our standard is to set our fuzzy and dangle length tolerances to 0.9 feet, less than the smallest feature, and large enough to inspect for errant junctions in a coverage's geometry. Check plots. visual inspection and lOO% checks Separate staffing is employed for visual inspection of the data. We prepare check plots of all data superimposed over the scanned source documents as shown in the sample map, followed by visual inspection of all plotted elements. Each map feature will have a highlighted mark in a specific color placed through the feature while it is compared with the source document. Our standard checklist is provided to the QC staff so that all features pass a prescribed set of tests. These check plots are returned to the technical operators for correction who, in turn, highlight the corrections as they are completed in a different (standard) color. These markups will be submitted to the City along with new checkplots for review and acceptance. Lynx Technologies City of Redwood City Street Lighting GIS Project