Laserfiche WebLink
SECTION D: WORK PLAN <br />The road features listed above reflect outstanding discussions to coordinate two different data <br />layers that have evolved over time. The tim-based roads layer generally comes fi.om MURF <br />requests for private roads and access ways while the second layer is fi.om named private roads <br />digitized fi.om the orthophotography. Budget constraints limited our ability to compile these two <br />data sets into one layer and resolve their differences. <br /> <br />Additional feature layers are optional and will be prioritized and driven by individual <br />department's budget constraints. Each project will follow similar development: 1) documented <br />scope and cost, 2) database design, 3) prototype conversion, 4) production, and 5) City <br />acceptance. Scheduled projects will operate independent of regular maintenance and with <br />additional staffing as required. Estimated costs are provided in the Cost and Schedule section. <br />Lynx will commit 1 field crew of 2 staffusing a Ttimble ProXR GPS device and softzware for all <br />data collection. Accuracy is generally sub-meter, approaching 2 feet horizontal. <br /> <br />Lynx Technologies will also be available for specific ad-hoc projects as they are prioritized, or <br />wherever deadlines are critical. For example, Lynx is available to QC the new digital <br />orthophotography. We have internal soft~vare QC routines that we have used elsewhere such as <br />for the Tri-County / Sanborn aerial photography project in the Monterey Bay area, and for the <br />City of San Marco. <br /> <br /> C) Enterprise GIS Development <br /> <br />While maintenance and ongoing GIS services have very diverse technical needs, we believe that <br />they are intricately related toward a common goal. We intend to work with the city's GIS and IT <br />staff over the next year to transition fi.om a traditional file-based GIS to an Enterprise GIS (on <br />ArcSDE and MSSQL Server. Ultimately, we foresee integrating the existing maintenance tasks <br />so that Lynx works as an ArcSDE Client to the City's Enterprise system in either a Versioned or <br />Disconnected Editing environment. Lynx will work with City staffto develop a successful <br />design and plan a strategy to transition the data and workflows into the system. Clearly, there <br />will be a testing period in which a parallel process will take place so that the maintenance cycle <br />is not disturbed. <br /> <br /> Lynx will work with the GIS/1T Team to develop a rational model. We believe that several <br /> critical steps will help to build the data model. Specifically, we propose to: <br /> Create documents that will orchestrate the existing and proposed data and systems, <br /> Provide workflows for ongoing maintenance and transition to SDE, and <br /> · Build data schema, ER, and Data model diagrams. <br /> <br /> Additional key documents to be created over the next several months are: · Data Catalog of all theme data, <br /> · Metadata standardized using Federal Geographic Data Committee (FGDC) standards, <br /> published and available on-line to the public and City staff. <br /> · Document existing GIS usage and maintenance workflows. <br /> <br /> Lvnx Technoloffles Cit~ o£ Pleasanton GIS Page 12 o£ 1 $ <br /> <br /> <br />