Databases and Data Management
Databases and Data Management
The National Park Services (NPS) have the data of fish species in the park system within the states of Virginia and Maryland. George Washington Birthplace Monument is one in the NPS. The system requires a database to store the fish data and a Web App to retrieve and use those data.
Two query widgets were created in the Web App (Fig.2) to retrieve data housed on the server. One query displayed the locations defined by a specific fish name, and the second query displayed the visits in a selected location. The output can also be printed in pdf format.
A server was used to house the fish data tables and relationships were established among those tables. Using ArcGIS Enterprise to create the geodatabase to house the shape files of park features, made them accessible from PostgreSQL (Fig.1). Registering the PostgreSQL database ensured that editing capability was enabled on the end of ArcMap. A Web App was then created to display the locations of the fish species based on x, y coordinates in the data.
It is common for companies to house their data on their server, and ArcGIS Enterprise together with PostgreSQL provide a way to access data via the internet. With evolving technology, companies have begun to house their data on the Cloud. And ESRI have came out with a platform to access data on the cloud via the internet. With mobile devices going mainstream, using apps to access data and even geoprocessing them will overtake software as a platform.
The northeastern United States on August 14, 2003 had a major blackout, leading to Homeland Security issues. The Federal government investigated possible locations for new high power transmission lines to increase the stability of the United States power grid. One location being investigated was New River Gorge National Park. National Park Services (NPS) required a database to store possible locations for the power lines and display the vertebrates and buildings impacted from installing the power lines.
A resulting Web App (Fig.2) was created that allowed users to select the location of their defined power lines, select the buffer distance and display the vertebrates and buildings that would potentially be impacted by the installation of the power lines.
The vertebrates species, events and location database tables were in Microsoft Access format. The data were cleaned up before exporting into text files. The text files were then loaded into PostgreSQL and an ArcGIS Enterprise geodatabase was created for the New River Gorge Park containing features such as buildings, trails, water bodies, roads, railroads and utilities. An empty feature class was created to store user-selected power line locations. Registering the PostgreSQL data tables allowed it to access the geodatabase and conversely, allowed Arc Catalog to access PostgreSQL databases (Fig.1). Web AppBuilder Developer Edition was used for its Enhanced Search Widget that allowed the user to buffer and clip with vertebrates and buildings within the buffered distance.
The Web AppBuilder has a Query Widget that has a limitation. It only processes a single input(parameter) and results in a single output. So, if the geoprocessing calls for a buffer and clip which requires two parameters, the Query Widget fails. To work around this limitation, the Web AppBuilder Developer Edition has an Enhanced Search Widget that allows the user to define the buffer distance and clip feature (two parameters) and output the result. However, the widget is not user friendly as it involves a series of steps without any instruction. It is not as straight forward as the Query Widget. The option of using Query Widget or Enhanced Search Widget is really up to user preference.