Data Collection Methodology
Fill in the specifics of your collection process below. This is a starting template.
Overview
The tree and shrub inventory covers American University’s campus. Data is maintained by
AU Geospatial staff and periodically exported from the source GIS system (Esri
ArcGIS/Field Maps) as a GeoJSON feature layer.
- Field data collection app: e.g., Esri Field Maps / Survey123 — specify version
- GNSS/positioning hardware: e.g., handheld GPS unit, model, stated accuracy
- Backend system: e.g., ArcGIS Online / Enterprise feature service name
- Attribute schema source: link to or describe the domain/field definitions used by field staff
Field Protocols
- How trees are identified (species keys, arborist review, etc.)
- How DBH, height, and condition are measured/assessed
- Update cadence (e.g., annual survey, event-driven updates for removals/plantings)
- QA/QC steps applied before publishing an export
Known Limitations
- Note any systematic gaps (e.g., shrubs undercounted, older records missing DBH/height)
- Note positional accuracy caveats
Export & Publication Process
- Export current inventory layer from the source system as GeoJSON (EPSG:4326).
- Place the export in
data/raw/ as an untouched copy.
- Copy (or lightly clean) into
data/geojson/ as the canonical published file.
- Run
python3 scripts/convert_formats.py to regenerate the CSV and GeoPackage copies in data/csv/ and data/gpkg/.
- Update the citation/version date in
CITATION.cff.