Hexagon binning for petroleum data

Hexagon binning to better view 50K

Gulf of Mexico Wells in ArcGIS Online

Andrew Zolnaifrom Ken Field, Esri

1 Sep 2015zolnai.ca

https://commons.wikimedia.org/wiki/File%3ADevelopment-driller-2.jpgBy U.S. Coast Guard photo by Petty Officer 3rd Class Barry Bena [Public domain], via Wikimedia Commons

Hexagon binningSet up bins for initial scale

BOEM well spots & infrastructure crowding

arcg.is/1SLEqb6

Hexagonal binning helps up-scale 50K wells• Ken Field on Esri blog:

Presenting point-based data on a web map is challenging because of the problem of overlapping symbology, particularly as you zoom out of the map to view data at smaller scales. So-called push-pin web maps are very easy to make with ArcGIS Online but making the map make visual sense at the smaller scales requires a little more work. In this blog entry we illustrate how data binning can be used to aggregate large point-based datasets into hexagonal polygons to overcome the problem and improve the web map across all scales.

Adapted beehive model

Workflow tip: store interim steps in default DB, final results in repository

Federal protractions, 10km hexagons & wells

1:2,500,000

Identity overlay between hexagons & wells 1

Identity overlay between hexagons & wells 2

1:5,000,000

Summary statistics

Join Summary statistics to hexagons

Hexagon 10km by mean TVD

1:5,000,0002,527 depth hexagons out of

9,970 total (all visible in frame)

Hexagon 10km by mean water depth

1:5,000,0002,527 depth hexagons out of

9,970 total (all visible in frame)

Hexagon 10km by first spud date1

• Summary Statistics 1st Spud date still date/time format• Joined table may lose added and calculated fields, so:• export it join as a table• add a FIRST_SPUD_YEAR field as short integer• and in Field Calculator do:

FIRST_SPUD_YEAR = DatePart ( “yyyy”, [FIRST_SPUD_DATE] )

Workflow tip: export to repository, not default DB as this is a final, not an interim stepCaution: depending on repository DB, date argument may change (MS SQL Server here)

Hexagon 10km by first spud date2

Note: SPUD_DATE and _YEAR are aliases

Hexagon 10km by first spud date3

1:5,000,0002,527 depth hexagons out of

9,970 total (all visible in frame)

Multiple scalesScale dependency for ArcGIS Online

Hexagon 5km by mean TVD

1:2,500,0005,340 depth hexagons (4,775

visible in frame) out of 35,028 total(12,850 visible in frame)

Hexagon 5km by mean water depth

1:2,500,0005,340 depth hexagons (4,775

visible in frame) out of 35,028 total(12,850 visible in frame)

Hexagon 5km by first spud date

1:2,500,0005,340 date hexagons (4,775 visible

in frame) out of 35,028 total(12,850 visible in frame)

Reduce data density & overlap to better post online

• Explore hive sizes as compared to data density & extent

• Adjusted scales reflect hexagon size & speed up zooming

• Suggest scripts be run using default names, then rename by scale• renaming script output can mess up Model Builder in background• Models can be corrupted, so if results are odd &/or tables misread

• either restart session• or restore original model• or convert to Python scripts See a Story Map of the same!

http://arcg.is/1USbYdZ