Logo GISdevelopment.net

GISdevelopment > Proceedings > GITA > 1999


GITA 2002 | GITA 2001 | GITA 2000 | GITA 1999 | GITA 1998 | GITA 1997 |  
Sessions

Business Applications

Data Development and Evolution

Data Distribution and Access

Engineering and Design Applications

Enterprise Integration

Enterprise Resource Planning

Exploiting Field and Mobile Technologies

Invited Track

Operations Support

People Issues

System Architecture

User Perspectives

Work Management


GITA 1999


Engineering and Design Applications


GIS-Based Data Management for Environmental Investigations

Data Transfer
Prior to the initiation of field work, we negotiated electronic deliverable formats with the selected laboratory so that they could automatically download requisite analytical data directly from their laboratory information management system to GIS\Keym’s import templates (reformatted Microsok Excel spreadsheets). This up-front coordination resulted in a data transfer system designed to eliminate manual data entry and associated transcription errors, reduce preprocessing time, and produce electronic files ready for importing.

At the same time, we began manually populating the sample tracking spreadsheet with proposed sampling information, including sample ID’s, collection intervals, and required test methods. This ensures that all requisite samples are collected and permits us to print sample container labels, thus eliminating double entry of data, unnecessary time in the field handwriting labels, and the potential for the laboratory to run the wrong test or mis-identify samples based on illegible container labels.

The analytical data were e-mailed to Woodard & Curran Inc (W&C) and electronically compiled with sample tracking information (the compiler macro also confirms that the laboratory has processed all samples). The data were then uploaded to the project database using GIS\KeyT”WinBuild, the import routine provided with the software. This routine permits input of a large volume of data at any one time without manual entry and verifies that there are no missing or inaccurate fields that would otherwise render the database useless. Data which fail this step are tagged with exception or warning codes so that they can be easily addressed. This saves significant time (we don’t inspect import templates for errors GIS\KeyT”WinBuild will identi~) and provides added assurance that data in the database will be predictably retrievable.

Physical data were manually entered into Microsoft@Excel spreadsheets and then appended to the project database. Use of electronic files in the field assures the crew that mandatory fields are completed and provides data management personnel in the office with legible information.

Data Interpretation and Reporting
Standard reporting routines provided with the software were used for data interpretation. These include automated queries for posting data to project basemaps, and drawing management tools for creating cross sections, graphs, boring logs, and contour maps. Because these routines take only minutes to run, we can evaluate our data from many perspectives in a short time-frame, and present this information in a meaningful way. Once interpretation has been completed, the figures can be inserted in the final report without additional drafting.

Page 3 of 7
| Previous | Next |

Applications | Technology | Policy | History | News | Tenders | Events | Interviews | Career | Companies | Country Pages | Books | Publications | Education | Glossary | Tutorials | Downloads | Site Map | Subscribe | GIS@development Magazine | Updates | Guest Book