Architecting Utah’s �Guzzler�Database

Integrating ArcGIS Online with modern Cloud Infrastructure

​

By William Wiskes

Agenda

1. Introduction

What are Guzzlers?

Why is a multi-platform system needed?

​

2. System Architecture

Pipelines, automations, and databases.

​

3. Interactive Dashboard

Using Looker Studio, realtime dashboards can be made of the data.

​

4. Conclusion

How does this save us time and money? What could have been done differently?

Introduction

• ‘Guzzlers’ are a semi-self-sustaining water supply tank for wildlife.
• Guzzlers need periodic servicing.
• The State of Utah has ~ 2k Guzzlers each with the potential of several dozen visits
• These Guzzlers are poorly documented with a need for a system to document locations and service visits

Project Requirements

• Fieldworkers must be able to add Guzzlers as well as submit visit data in ArcGIS.
• The data must enrich itself on a schedule.
• The data are protected – the infrastructure must have the potential to build out different dashboards for different partners quickly.
• The data must be organized by time since last visit

System Architecture

ArcGIS Online

Geo-enrichment in Cloud Functions

https://github.com/wwiskes/AGOLenrichment

Geo-enrichment in Cloud Functions

Warehouse in BigQuery

Looker Studio Dashboards

Conclusion

BENEFITS

• Big Query and Looker Studio are able to deliver insights not possible in ArcGIS Online
• Cloud functions are able to enrich features and manipulate data in ways not possible in ArcGIS Online
• This system is self maintaining, scalable, and cost effective
• This system was built quickly and has the potential for use in other projects
• The front end system (Looker Studio) is very simple and allows for easy collaboration

LIMITATIONS

• Ideally the feature enrichment stage of the function should be built on trigger – not on a schedule.

QUESTIONS?