Laserfiche WebLink
Queries to extract information from HydroBase and merge it with estimated control points will <br />be coded, tested and documented. Populating the repository with the needed additional GIS <br />data will occur during alluvial model development.. Queries from HydroBase will be <br />developed within Microsoft Access using Visual Basic for Applications (VBA), while Python <br />and VBA will be used to develop the programs in ArcGIS. Event themes or geodatabases in <br />ArcGIS will be used, where appropriate, to simplify this task. <br />Two meetings are anticipated for this task. The deliverable for this task will be a technical <br />memorandum documenting the design of the GIS coverages, including a data dictionary <br />describing all data fields. It is anticipated that the Modeling GIS Repository will be a working <br />database, and thus not suitable for direct posting on public web site without additional <br />processing and documentation. All programs or queries developed for this task will be <br />documented. Source code for all programs will be provided, along with GIS coverages with test <br />data. The deliverable for this task is anticipated to be less than five pages, plus electronic <br />attachments. <br />2.3 Stream Flow Routing Program Development <br />The current process for creating stream model control files will require significant modification. <br />Currently, a complex process using several programs specific to the RGDSS is used to generate <br />stream package files. The current process utilizes stream segments that are manually defined <br />from 100k series USGS digital line graphs for stream locations, along with stream elevations <br />imported either from digital elevation models or from surveyed stream profiles. A total of four <br />major and four support programs (mksd, mkdiv, mkgage, rkret, mkq, mkstr, build and ModEx) <br />are used to process stream and diversion locations and time series data used in the State's <br />custom version of the stream package. A significant amount of RGDSS-specific code is included <br />in these programs and should be generalized and modified to use information from control <br />files, rather than including basin-specific features within the code. Modifications to these <br />programs to remove RGDSS-specific elements is underway at the present time. The Modeling <br />GIS Repository will contain the stream-related information that will be queried in a file format <br />compatible with this new DMI. As with other model enhancement activities, meetings will be <br />held initially with the State to discuss recommended approaches before proceeding with code <br />modifications or development. <br />A new DMI will be developed to generate files for the Stream Flow Routing package (SFR1), <br />using information from HydroBase and the Modeling GIS Repository. This new DMI will use <br />some of the existing programs developed for the RGDSS (potentially including the programs <br />mksd, mkdiv, mkgage, rkret, mkq, mkstr, build and ModEx), with modifications and <br />streamlining to consolidate individual processing steps. The SPDSS process will utilize the <br />State GIS repository as the source of stream and diversion locations. This GIS polyline coverage <br />will require processing to assemble a composite polyline representing an entire stream, <br />arranged in downstream order. This database already has stream names encoded, which will <br />facilitate extraction of appropriate data. Currently, the Perl program mkstr assembles stream <br />segments and interpolates elevation from a USGS digital elevation model. One of the coverages <br />in the Modeling GIS Repository will include the stream polylines that will be included in the <br />conceptual model. Another coverage will include diversions, also represented as polylines. <br />These coverages will include the interpolated elevation at each node that will be determined <br />from survey data, channel profiles and digital elevation model data. This information will be <br />