SlideShare a Scribd company logo
September 14, 2022
North Dakota Parks and Recreation Department
KEEPING IT FRESH: ASSET
COLLECTOR FOR ND STATE PARKS
NDGeospatialSummit2022 - KEEPING IT FRESH: ASSET COLLECTOR FOR ND STATE PARKS
NDGeospatialSummit2022 - KEEPING IT FRESH: ASSET COLLECTOR FOR ND STATE PARKS
PROJECT GOALS
➢ Master park and trail planning
➢ More accurate inventory of park assets
➢ Inform operation and maintenance
decision making
➢ Share assets with internal staff and public
➢ Collect as much data as possible within
budget allocated
NDGeospatialSummit2022 - KEEPING IT FRESH: ASSET COLLECTOR FOR ND STATE PARKS
PEOPLE INVOLVED
Brian Fisher
Principal in Charge
Dave Kirkpatrick
Project Manager
Thomas Moore
Field Collection / Data schema
Chad Nunemacher
Web Development Lead
Andrea Travnicek
Director
Jolene Rieck
Chief of Planning & Programs
Gordon Lemmel
Parks Planner
Ryan Gardner
West Regional Manager
Justin Robinson
East Regional Manager
Christine Dirk
GIS Specialist
NDGeospatialSummit2022 - KEEPING IT FRESH: ASSET COLLECTOR FOR ND STATE PARKS
DATA NEEDS
➢ Where and how should the data be stored?
➢ What GIS layers are needed for park asset collection?
➢ How should the GIS data be propagated?
➢ What fields/field types are needed for each layer?
➢ What fields required domains(drop-downs)?
➢ What relationships are needed between layers?
➢ How should photos be handled?
DATA NEEDS
➢ Reviewed NDPR Asset Management
➢ Go Anoka Park App Schema leveraged
as schema development starting point
➢ Discussions went back and forth
between HEI and ND Parks Staff until
Schema was finalized
➢ X-Ray Used for Schema Development
and Finalized Schema Export
Field Data Collection
➢ In-Office analysis was first to see what augmentation was needed in the
field
➢ Plan logistics – Safety protocol
➢ Get an idea of what needs to be collected
➢ Add data to feature classes
➢ Each park had unique situations
➢ Network coverage, occupancy, new feature types
➢ On the fly adjustments had to be made in the field
➢ In-field collection was used to supplement the missing elements and
feature not clear in office analysis
➢ Collect features not found on CAD, plans, maps
➢ Add attributes
➢ Add photos
➢ Post field collection process was used to finalize park features and
attributes
➢ 41 feature classes
➢ 250+ attributes
Final Product - Geodatabase
➢ In-Office analysis was first to see what augmentation was needed in the
field
➢ In-field collection was used to supplement the missing elements and
feature not clear in office analysis
➢ Collect features not found on CAD, plans, maps
➢ Add attributes
➢ Add photos
➢ Post field collection process was used to finalize park features and
attributes
Technology
Esri Technology Used
Other Technology Used
Mobile Technology – R1 | iPad | Collector
BENEFITS:
OS Agnostic - IOS, Android
No custom programming
Industry standard
Familiarity HEI and ND Parks
Greater Accuracy than Ipad internal antenna
External Antenna can be extended for better signal
SBAS Corrections with 4GLTE < 3ft
Bluetooth connection to Ipad
Workflows & Migration
HEI Pilot Workflow
Migration From HEI to NDIT
FGDB
(SQL)
Final Workflow
Post Migration
https://www.parkrec.nd.gov/business/planning/rec-assets
Assets Web Application
➢ Piloting the data collection process on one park
➢ Matching HEI staff interest to project needs
➢ Optimizing field time by focusing on data collection of assets and
attributes that couldn’t be completed in-office
➢ Open dialog with state staff / checkin meetings before and after each
park
➢ On the fly adjustments
➢ Maximizing COTS for data collection framework
Keys to a Successful Project
Questions?
Contacts:
Brian Fischer
bfischer@houstoneng.com
Chad Nunemacher
cnunemacher@houstoneng.com

More Related Content

NDGeospatialSummit2022 - KEEPING IT FRESH: ASSET COLLECTOR FOR ND STATE PARKS

  • 1. September 14, 2022 North Dakota Parks and Recreation Department KEEPING IT FRESH: ASSET COLLECTOR FOR ND STATE PARKS
  • 4. PROJECT GOALS ➢ Master park and trail planning ➢ More accurate inventory of park assets ➢ Inform operation and maintenance decision making ➢ Share assets with internal staff and public ➢ Collect as much data as possible within budget allocated
  • 6. PEOPLE INVOLVED Brian Fisher Principal in Charge Dave Kirkpatrick Project Manager Thomas Moore Field Collection / Data schema Chad Nunemacher Web Development Lead Andrea Travnicek Director Jolene Rieck Chief of Planning & Programs Gordon Lemmel Parks Planner Ryan Gardner West Regional Manager Justin Robinson East Regional Manager Christine Dirk GIS Specialist
  • 8. DATA NEEDS ➢ Where and how should the data be stored? ➢ What GIS layers are needed for park asset collection? ➢ How should the GIS data be propagated? ➢ What fields/field types are needed for each layer? ➢ What fields required domains(drop-downs)? ➢ What relationships are needed between layers? ➢ How should photos be handled?
  • 9. DATA NEEDS ➢ Reviewed NDPR Asset Management ➢ Go Anoka Park App Schema leveraged as schema development starting point ➢ Discussions went back and forth between HEI and ND Parks Staff until Schema was finalized ➢ X-Ray Used for Schema Development and Finalized Schema Export
  • 10. Field Data Collection ➢ In-Office analysis was first to see what augmentation was needed in the field ➢ Plan logistics – Safety protocol ➢ Get an idea of what needs to be collected ➢ Add data to feature classes ➢ Each park had unique situations ➢ Network coverage, occupancy, new feature types ➢ On the fly adjustments had to be made in the field ➢ In-field collection was used to supplement the missing elements and feature not clear in office analysis ➢ Collect features not found on CAD, plans, maps ➢ Add attributes ➢ Add photos ➢ Post field collection process was used to finalize park features and attributes ➢ 41 feature classes ➢ 250+ attributes
  • 11. Final Product - Geodatabase ➢ In-Office analysis was first to see what augmentation was needed in the field ➢ In-field collection was used to supplement the missing elements and feature not clear in office analysis ➢ Collect features not found on CAD, plans, maps ➢ Add attributes ➢ Add photos ➢ Post field collection process was used to finalize park features and attributes
  • 15. Mobile Technology – R1 | iPad | Collector BENEFITS: OS Agnostic - IOS, Android No custom programming Industry standard Familiarity HEI and ND Parks Greater Accuracy than Ipad internal antenna External Antenna can be extended for better signal SBAS Corrections with 4GLTE < 3ft Bluetooth connection to Ipad
  • 16. Workflows & Migration HEI Pilot Workflow Migration From HEI to NDIT FGDB (SQL) Final Workflow
  • 19. ➢ Piloting the data collection process on one park ➢ Matching HEI staff interest to project needs ➢ Optimizing field time by focusing on data collection of assets and attributes that couldn’t be completed in-office ➢ Open dialog with state staff / checkin meetings before and after each park ➢ On the fly adjustments ➢ Maximizing COTS for data collection framework Keys to a Successful Project