Agmt03 Lynx Technologies - Laserfiche WebLink

Browse Search

Section 5: Proposed Scope & Techniques 13 Data Collection - Conduit As discussed above, the existing maps do not reflect the current routing for the street light system. Therefore, we propose to prepare D-size maps for the City after the street light pole data is collected. The maps will be printed at 200 scale and will include streets, parcels, addresses and light fixtures. The purpose of these maps is to allow the City's staff to draw the location of conduits connecting the circuitry for the street light system. Once Lynx receives the completed field maps back from the City, the conduit information will be digitized and annotated according to the steps outlined below. Construct Topology and QC Geometry The street light conduit network will be tested in AutoCAD map before processing in ArcInfo. Coordinate errors such as dangles (undershoots and overshoots), pseudo-nodes, crossing objects (missing node), and clusters (topologically insignificant points, duplicate nodes) will be eliminated. All systems will be tested for continuity by executing flood trace analysis. Once these tests pass for each system, DXF files will be created for each conduit and structure. Network topology will be built in ArcInfo 8.3 and tested again for any coordinate errors. The resulting coverages will include linked arc and node attribute tables so that nodes will be properly associated with its corresponding conduit. Conduit length will be calculated automatically. Populate feature attribute tables Feature attribute tables will be populated based on the original atlas map sheets, and the database models that arise during the pilot project. Observed attributes include: conduit size, phi, and capacity, total power (wattage) and lumen type. All data will come from the original hardcopy map sheets; supplemental information must be on these documents prior to the beginning of the project. Thus, if the City would like to update the system facilities, we will honor the time commitment and cost through the Notice to Proceed. Domains will be established for all possible fields to limit data entry error as much as possible. In addition, we'll use the same domain database in automated QC tests discussed below. Database population will be automated as much as possible to expedite the process and minimize the potential for error. For example, the utility classification, grid number, 'f' and 't', and type declaratives can be calculated in a single batch process. We recommend that each feature attribute table also have metadata items so that record level tracking can be maintained once the City begins using the GIS to update the system. We'd also recommend using a banding approach to the structure ID numbers as in the figure below. This requires slightly more effort but it will provide a very systematic approach to numbering the mapped features. This will provide users with numbers that have a geographical 'sense'. For example, 500 series numbers will also appear on the southern fifth of any map sheet. 100 8101 102 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 200 8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 300 8300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 400 8401 8403 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 500 8500 8502 I G12 Lynx Technologies City of Redwood City Street Lighting GIS Project