Introduction
The spatial database design class taught me how to create and manage a database. The final project focused on developing our own database from scratch. The idea for my database came from my time volunteering at the Utah’s Hogle Zoo. As a volunteer, I have participated in many Boreal Toad surveys. The Utah Department of National Resources (DNR) uses the information from our surveys to help track the Boreal toad populations throughout Utah. These surveys done by both the DNR and Volunteers are very important because there are 114 survey sites for boreal toads in Utah. If the DNR had a geospatial database for their data, they would be able to expand their analysis of Boreal Toad population health. This is a very important task because boreal toad populations as well as other amphibians are being killed by chytrid fungus. The chytrid fungus is deadly because it coats an amphibian’s skin. The direct cause of death is unknown, but given that amphibians drink and breathe through their skin could make both those tasks difficult. High altitude species like the boreal toad are particularly vulnerable. This vulnerability is due in part to the specific survival conditions living above 5000 feet and near marshy wetlands or lake regions. The need for a boreal toad database is very critical to receive the most current information on boreal toad health.
The goal of this database is to hold everything from toad sightings to DNR stations. There will be a lot of static data including DNR regions, DNR stations, trails, and survey sights. These will have little to no change over the years. The dynamic layer will be the Boreal Toad sightings. That layer will grow larger with every toad sighting. The database will help organize these layers in one location for easy access.
Methodology
When creating this database, I began with the very basics. Before creating the actual database, I created an entity-relationship model. The model allowed me to visualize the basic structure of the database. The next step was to create a relational model which identified how each layer was related to each other (Figure 1). Without these models as a guide, creating the database would have been extremely challenging. A lot of time went into these models which made the creating the final database a smooth process.
In order to create this database I had to develop almost all the required layers from scratch. I had to digitize DNR region boundaries and DNR station locations. The Utah lake layer, acquired from the Utah Automated Geographic Reference Center (AGRC), was reduced to the study region which included only a dozen survey sites. Besides digitizing, I created excel tables applying a latitude and longitude to each input. These tables were then loaded using the “table to xy” tool in ArcGIS Pro. Once the layers were finished the relationship classes were added to connect the various point and polygon features.
Results
Below are screenshots of the final database with all the associated layers and relationship classes (Figure 2). The relationship classes link a variety of layers including field site and toad data. The screenshot shows how to access the related data for the specific selection (Figure 3).
Conclusion
The final geodatabase contained an assortment of geometry layers including points and polygons. Although it was difficult to develop the required layers it was a great learning experience. The final presentation was to demonstrate the functionality of the database and prove that the relationship classes would link to the other data layers.
Skills
- Database Design
- Data Models and Structure
- Structured Query Language
Melissa Gfeller 