Introduction to RegGSS
Objective: Create a one or two day class to on how to use RegGSS.
Justification: Currently, the GIS Unit provides demos of RegGSS but there is no formalized training. Considering that RegGSS system is used by most reviewers in Regulation a training class would be greatly beneficial.
Objective: Capture Missing Conservation Easements
Justification: Conservation Easements are used by Regulation when evaluating the issuance of permits. In the case of Land Management, Conservation Easements represent SFWMD property interests that must be itemized.
Note: There is a Flag in GENP which indicates that an application may potentially have a CE. Using this flag we know there are 1379 applications that may have CEs that have not been examined by the GIS Unit. False positives occur when a CE is deeded in one application and then subsequent applications continue to carry the CE Flag. Thus, the total number of applications should be about 25% less or around 1,000 . On average an application will be composed of three or four CE polygons so an estimate of the missing population is around 4,000 polygons. CEs are entered using COGO which can be time consuming. Assuming 30 minutes per polygon it would take about 50 weeks for 1 FTE.
Objective: Capture Missing Right-of-Way Permits
Justification: The maintenance of ROW permits was taken over by Regulation in early 2012. Based on the number of records in the GIS compared to the records in GENP we are aware of 7,630 missing applications. Assuming 5 minutes per polygon it would take about 15 weeks for 1 FTE.
Objective: Create a baseline set of imagery circa 1970.
Justification: SFWMD began its regulatory permit program in the mid 1970s. There is a need for baseline imagery circa 1970 right before the District began issuing permits. The University of Florida has a collection of non-georeferenced imagery from the 1970s. This project would involve georeferencing these images.
In my previous post Managing the IT Project Portfolio I talked about a project ranking methodology. In this post I list the application development project contenders. In another post I will discuss our data project contenders.
Objective: Create a Spatial Decision Support System for the review of applications and the issuance of regulatory permits.
Justification: Currently, reviewers spend many hours looking for possible conflicts by turning GIS layers off/on, users also have to sift through many Early Warning System Notifications. MyApplications would create a centralized hub for viewing geospatial information that may have an effect on the issuance of a permit.
Status: Advanced Prototype.
Objective: Modify Area of Interest (AOI) Reports to produce pre-application reports. To be used and given to reviewers and clients during pre-application meetings.
Justification: Currently, reviewers go into a pre-application meeting with limited information. This project would facilitate the creation of a report detailing: soils, land-use, transportation, property information for the property in question.
Status: Advanced Prototype.
|Drawdown MODFLOW / WINFLOW
Objective: Modify the Drawdown model to serve as a front-end to MODFLOW or WINFLOW. Drawdown is a custom built C# Theiss drawdown model that calculates a depression cone around a pumped well.
Justification: Currently, reviewers can run a simple Thiess model but more complex models are not available. This project would modify Drawdown to be a front-end to MODFLOW/WINFLOW allowing for more complex modeling.
Status: Not Started.
Objective: Create an application to facilitate the creation of a cut/fill analysis/report using gridded (LiDAR) data.
Justification: Currently, the cut/fill analysis involves a number of GIS processing steps that are not obvious to ERP Engineers. This project would allow a reviewer to select a sub-set of an elevation grid, specify an elevation, and perform a cut/fill analysis that results in a report including cubic measurements, cross sections and maps.
Status: Not Started
|Sub-Watersheds Editing Environment
Objective: Create an editing environment to allow for the capture of sub-watersheds.
Justification: Currently, when Engineers review an ERP application they need to wade through scanned documents to find sub-watershed flow diagrams which wastes time. This project creates the editing environment necessary to modify existing and create new sub-watershed.
Status: Not Started. In an initial effort we were able to extract 17,000 sub-watersheds from data in our GIS/ORACLE systems, however, the editing environment is needed to create network topology and capture new features.