processing geospatial data at scale @locationtech

89
PROCESSING GEOSPATIAL DATA @ SCALE Rob Emanuele GEO(MESA/WAVE/TRELLIS/JINNI)

Upload: rob-emanuele

Post on 12-Apr-2017

458 views

Category:

Software


1 download

TRANSCRIPT

Page 1: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Rob Emanuele

GEO(MESA/WAVE/TRELLIS/JINNI)

Page 2: Processing Geospatial Data At Scale @locationtech

What we’ll be covering…

What does “processing geospatial data at scale” mean?

Background on big data frameworks

What is LocationTech?

Overview of LocationTech projects for processing big geo data.

Page 3: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 4: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 5: Processing Geospatial Data At Scale @locationtech

Large geospatial data

Landsat 8 on AWS: 465,68 scenes @ ~800 MB each. That's 355 TB and counting.

OpenStreetMap edit history: 75 GB compressed.

3 years of geotagged tweets: 3 TB

Page 6: Processing Geospatial Data At Scale @locationtech

NED 1/3 arc second

Page 7: Processing Geospatial Data At Scale @locationtech

NED 1/3 arc second

Page 8: Processing Geospatial Data At Scale @locationtech

NED 1/3 arc second

Page 9: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 10: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 11: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 12: Processing Geospatial Data At Scale @locationtech
Page 13: Processing Geospatial Data At Scale @locationtech

Project to build a better search engine, back in the early 2000’s.

Worked for small datasets, but was not scalable.

Page 14: Processing Geospatial Data At Scale @locationtech

The Google papers

Page 15: Processing Geospatial Data At Scale @locationtech

After reading the papers, Nutch developers added a distributed file system and MapReduce model to Nutch.

In 2006, those portions were spun out of Nutch to form…

Page 16: Processing Geospatial Data At Scale @locationtech
Page 17: Processing Geospatial Data At Scale @locationtech

Apache Hadoop

Heavily supported by Yahoo, which moved it’s large data processing to Hadoop.

by 2007, Twitter, Facebook, LinkedIn and many others were doing serious work with Hadoop

2008 Hadoop graduated to a top level Apache project

Page 18: Processing Geospatial Data At Scale @locationtech

Hadoop

Source: http://cs.calvin.edu/courses/cs/374/exercises/12/lab/MapReduceWordCount.png

Page 19: Processing Geospatial Data At Scale @locationtech

Matei Zaharia

Worked with Hadoop at UC Berklee

Noticed Hadoop was not a good fit for Machine Learning algorithms and other iterative models.

So in 2009, he created…

Page 20: Processing Geospatial Data At Scale @locationtech
Page 21: Processing Geospatial Data At Scale @locationtech
Page 22: Processing Geospatial Data At Scale @locationtech

Open sourced in 2010 under BSD license

Maintained by UC Berkeley’s AMPLab

Donated to the Apache Software Foundation in 2013 and relicensed as Apache 2.0

Graduated to a top level Apache project in 2014

Apache Spark

Page 23: Processing Geospatial Data At Scale @locationtech

Apache Spark

a distributed computation engine.

An API that lets you work with distributed data as a collection.

Written in Scala, with language bindings for use with Java, Python, and R.

Page 24: Processing Geospatial Data At Scale @locationtech
Page 25: Processing Geospatial Data At Scale @locationtech
Page 26: Processing Geospatial Data At Scale @locationtech
Page 27: Processing Geospatial Data At Scale @locationtech
Page 28: Processing Geospatial Data At Scale @locationtech
Page 29: Processing Geospatial Data At Scale @locationtech
Page 30: Processing Geospatial Data At Scale @locationtech

2006

Page 31: Processing Geospatial Data At Scale @locationtech
Page 32: Processing Geospatial Data At Scale @locationtech

Apache Accumulo

Created by the NSA in 2008

Donated to the Apache Foundation in 2011

Graduated to a top level project in 2012

Almost defunded by the US government the same year.

Page 33: Processing Geospatial Data At Scale @locationtech

(Sec. 929) Prohibits any DOD component from utilizing the cloud computing database developed by the National Security Agency (NSA) and known as "Accumulo" after the end of FY2013, unless the DOD CIO certifies that: (1) there are no viable commercial open source databases that have such security features, or (2) Accumulo itself has become a successful open source database project. Requires DOD and intelligence community officials to coordinate the use by DOD components of cloud computing infrastructure and services offered by the intelligence community for purposes other than intelligence analysis.

Page 34: Processing Geospatial Data At Scale @locationtech

(Sec. 929) Prohibits any DOD component from utilizing the cloud computing database developed by the National Security Agency (NSA) and known as "Accumulo" after the end of FY2013, unless the DOD CIO certifies that: (1) there are no viable commercial open source databases that have such security features, or (2) Accumulo itself has become a successful open source database project. Requires DOD and intelligence community officials to coordinate the use by DOD components of cloud computing infrastructure and services offered by the intelligence community for purposes other than intelligence analysis.

Page 35: Processing Geospatial Data At Scale @locationtech

Data Node

Data Node

Data Node

Name Node

Master

Tablet Server

Tablet Server

Tablet Server

Accumulo

BigTable clone (columnar database)

Records stored on HDFS

Lexicographically sorted table index

Page 36: Processing Geospatial Data At Scale @locationtech
Page 37: Processing Geospatial Data At Scale @locationtech
Page 38: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 39: Processing Geospatial Data At Scale @locationtech

PROCESSING GEOSPATIAL DATA @ SCALE

Page 40: Processing Geospatial Data At Scale @locationtech
Page 41: Processing Geospatial Data At Scale @locationtech
Page 42: Processing Geospatial Data At Scale @locationtech
Page 43: Processing Geospatial Data At Scale @locationtech

WHAT IS ?

Page 44: Processing Geospatial Data At Scale @locationtech
Page 45: Processing Geospatial Data At Scale @locationtech
Page 46: Processing Geospatial Data At Scale @locationtech
Page 47: Processing Geospatial Data At Scale @locationtech

GEOJINNI(FORMERLY SPATIALHADOOP)

Page 48: Processing Geospatial Data At Scale @locationtech

Spatial language Built-in spatial data types

Spatial Indexes Spatial Operations

Page 49: Processing Geospatial Data At Scale @locationtech
Page 50: Processing Geospatial Data At Scale @locationtech

72 Frames × 14 Billion points per frame Total = 1 Trillion points

Generated in three hours on a 10-node cluster

HEAT MAP FROM 2009 TO 2014 MONTH-BY-MONTH

Page 51: Processing Geospatial Data At Scale @locationtech
Page 52: Processing Geospatial Data At Scale @locationtech
Page 53: Processing Geospatial Data At Scale @locationtech
Page 54: Processing Geospatial Data At Scale @locationtech

Geo +

accessed through

Page 55: Processing Geospatial Data At Scale @locationtech
Page 56: Processing Geospatial Data At Scale @locationtech
Page 57: Processing Geospatial Data At Scale @locationtech
Page 58: Processing Geospatial Data At Scale @locationtech
Page 59: Processing Geospatial Data At Scale @locationtech
Page 60: Processing Geospatial Data At Scale @locationtech
Page 61: Processing Geospatial Data At Scale @locationtech
Page 62: Processing Geospatial Data At Scale @locationtech

SELECT tweet.text, user.name FROM tweet, userWHERE bbox(tweet.location, -115, 45, -110, 50) AND tweet.user_id = user.user_id

+

Page 63: Processing Geospatial Data At Scale @locationtech
Page 64: Processing Geospatial Data At Scale @locationtech

GeoTrellis

a Scala library for geospatial data types and operations.

enables Spark with geospatial capabilities (mainly raster, currently working on vector)

storage and query raster from HDFS, Accumulo, and S3 (Cassandra support in development)

0.10 is released!

Page 65: Processing Geospatial Data At Scale @locationtech
Page 66: Processing Geospatial Data At Scale @locationtech
Page 67: Processing Geospatial Data At Scale @locationtech
Page 68: Processing Geospatial Data At Scale @locationtech
Page 69: Processing Geospatial Data At Scale @locationtech

Polygonal Summaries

Page 70: Processing Geospatial Data At Scale @locationtech

Polygonal Summaries

Page 71: Processing Geospatial Data At Scale @locationtech

100 spot instance m3.xlarge workers @ $0.04 / hr = $4.00 / hr

400 CPUs / ≈1.5 TB memory

1 master m3.xlarge on-demand instance @ $0.26 / hr

EMR cluster charge, $0.07 / hr

$4.37 / hr

Rendering elevation with hillshade + NLCD on AWS EMR

Page 72: Processing Geospatial Data At Scale @locationtech
Page 73: Processing Geospatial Data At Scale @locationtech
Page 74: Processing Geospatial Data At Scale @locationtech
Page 75: Processing Geospatial Data At Scale @locationtech
Page 76: Processing Geospatial Data At Scale @locationtech

Geo +

accessed through

GEOWAVE

Page 77: Processing Geospatial Data At Scale @locationtech

Index typeZ-order spatial &

spatiotemporal binned by week

Hilbert in N-dimensions with tiered indexing and

binning

Backends supported

Accumulo (main), Cassandra, HBase,

DynamoDB, Google cloud Bigtable

Accumulo (main), HBase

Servers supported GeoServer GeoServer, MapnikProcessing

Frameworks supportedHadoop, Spark, Storm,

Kafka Hadoop, Spark

Language Scala Java

Page 78: Processing Geospatial Data At Scale @locationtech

Index typeZ-order spatial &

spatiotemporal binned by week

Hilbert in N-dimensions with tiered indexing and

binning

Backends supported

Accumulo (main), Cassandra, HBase,

DynamoDB, Google cloud Bigtable

Accumulo (main), HBase

Servers supported GeoServer GeoServer, MapnikProcessing

Frameworks supportedHadoop, Spark, Storm,

Kafka Hadoop, Spark

Language Scala Java

Page 79: Processing Geospatial Data At Scale @locationtech

Tiered Indexing

Page 80: Processing Geospatial Data At Scale @locationtech

Tiered Indexing

Page 81: Processing Geospatial Data At Scale @locationtech

Binning (time dimension)

1997 1998 1999

Page 82: Processing Geospatial Data At Scale @locationtech

Binning (arbitrary dimensions)

Time

Elevation

Velocity

Page 83: Processing Geospatial Data At Scale @locationtech
Page 84: Processing Geospatial Data At Scale @locationtech

Collaboration

Page 85: Processing Geospatial Data At Scale @locationtech

Collaboration

Page 86: Processing Geospatial Data At Scale @locationtech
Page 87: Processing Geospatial Data At Scale @locationtech

• Working together to learn to collaborate

• Making the connections necessary that allow collaboration to flourish

Page 88: Processing Geospatial Data At Scale @locationtech

• Join the locationtech-iwg mailing list

• Share you big geospatial data challenges

• Propose projects

Get involved!

Page 89: Processing Geospatial Data At Scale @locationtech

THANK YOU

@lossyrob

gitter.im/geotrellis/geotrellis

github.com/geotrellis/geotrellis

[email protected]