ArcGIS Parks and Gardens Information Model expanded: A solution for improving plant records data management
Subject
Abstract
Many gardens are managing plant records independent of each other in two distinct systems; a plant records database and mapping software. This causes unnecessary data entry duplication and consistency errors. BGBASE and IrisBG are among the most used database systems for recording plants, ArcGIS is a robust system for mapping gardens but is currently used by only 10% of gardens. The current Parks and Gardens Information Model for ArcGIS provides a free geodatabase structure for databasing and mapping gardens. The current model focuses on garden infrastructure with some capacity for storing plant collections data, the current capacity is not suitable as a single repository for plant records data. In order to expand the current model, a thematic analysis was performed, comparing the current model, BGBASE and IrisBG. Tables from all three systems were categorized by theme, with 21 themes identified across all three systems. Fields from system tables were used to identify sub-themes within each theme. Key functionality within each theme was also identified. A survey of the user community was performed to identify which themes and functionality are most important when documenting plant collections. The user community identified 11 themes and 6 functions as important. Implementation of these themes and functions was completed by adding subthemes absent from the current ArcGIS model and common to both BGBASE and IrisBG to the current ArcGIS model. A total of 10 new tables, 1 point feature class and 31 new relationships were added. Sample plant records data was migrated into the new model and the new model was validated by performing the 6 functions identified as important by the user community in the survey. The new model was able to perform all functions in a similar number of steps as they are performed in BGBASE and IrisBG. The new model has significant improvements in both data schema capacity and functionality and can be used as a single system for plant records, based on input from the user community. Uptake of this model by the user community will improve the efficiency, effectiveness and accuracy of plant records data.