Book Image

Geospatial Data Analytics on AWS

By : Scott Bateman, Janahan Gnanachandran, Jeff DeMuth
Book Image

Geospatial Data Analytics on AWS

By: Scott Bateman, Janahan Gnanachandran, Jeff DeMuth

Overview of this book

Managing geospatial data and building location-based applications in the cloud can be a daunting task. This comprehensive guide helps you overcome this challenge by presenting the concept of working with geospatial data in the cloud in an easy-to-understand way, along with teaching you how to design and build data lake architecture in AWS for geospatial data. You’ll begin by exploring the use of AWS databases like Redshift and Aurora PostgreSQL for storing and analyzing geospatial data. Next, you’ll leverage services such as DynamoDB and Athena, which offer powerful built-in geospatial functions for indexing and querying geospatial data. The book is filled with practical examples to illustrate the benefits of managing geospatial data in the cloud. As you advance, you’ll discover how to analyze and visualize data using Python and R, and utilize QuickSight to share derived insights. The concluding chapters explore the integration of commonly used platforms like Open Data on AWS, OpenStreetMap, and ArcGIS with AWS to enable you to optimize efficiency and provide a supportive community for continuous learning. By the end of this book, you’ll have the necessary tools and expertise to build and manage your own geospatial data lake on AWS, along with the knowledge needed to tackle geospatial data management challenges and make the most of AWS services.
Table of Contents (23 chapters)
1
Part 1: Introduction to the Geospatial Data Ecosystem
4
Part 2: Geospatial Data Lakes using Modern Data Architecture
10
Part 3: Analyzing and Visualizing Geospatial Data in AWS
16
Part 4: Accessing Open Source and Commercial Platforms and Services

Considering temporal dimensions

All of the concepts we have reviewed in this chapter become amplified by the dimension of time. For example, imagine you are ingesting and storing location-based data for marathon runners in the United States. Let’s say this number is around 500,000. Creating a heat map to show concentrations of where marathon runners live already means dealing with a reasonably large dataset. Now, consider the locations of each race that the runners participated in over the course of a year. You get even better location insights into the marathon activity over the year, but you are likely dealing with millions of data points. The data grows exponentially when you start to look at GPS data from fitness trackers along the marathon routes. There are over 1,000 marathons each year in the US, and the largest marathons have over 10,000 finishers. Multiply that by the GPS location of each runner, and even at 10-second intervals, the data volumes become enormous. Conventional...