GeospatialPython
diff --git a/‎docs/advanced/picking.md‎
Lines changed: 13 additions & 0 deletions b/‎docs/advanced/picking.md‎
Lines changed: 13 additions & 0 deletions
diff --git a/‎docs/get-started/interactivity.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/get-started/interactivity.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎…ewport-animation-first-person-map/app.js‎ ‎…mental/multi-viewport-transitions/app.js‎examples/wip/viewport-animation-first-person-map/app.js renamed to examples/experimental/multi-viewport-transitions/app.js b/‎…ewport-animation-first-person-map/app.js‎ ‎…mental/multi-viewport-transitions/app.js‎examples/wip/viewport-animation-first-person-map/app.js renamed to examples/experimental/multi-viewport-transitions/app.js
diff --git a/‎examples/wip/first-person-map/index.html‎ ‎…al/multi-viewport-transitions/index.html‎examples/wip/first-person-map/index.html renamed to examples/experimental/multi-viewport-transitions/index.html b/‎examples/wip/first-person-map/index.html‎ ‎…al/multi-viewport-transitions/index.html‎examples/wip/first-person-map/index.html renamed to examples/experimental/multi-viewport-transitions/index.html
diff --git a/‎…amples/wip/first-person-map/package.json‎ ‎…/multi-viewport-transitions/package.json‎examples/wip/first-person-map/package.json renamed to examples/experimental/multi-viewport-transitions/package.json b/‎…amples/wip/first-person-map/package.json‎ ‎…/multi-viewport-transitions/package.json‎examples/wip/first-person-map/package.json renamed to examples/experimental/multi-viewport-transitions/package.json
diff --git a/‎…s/wip/first-person-map/webpack.config.js‎ ‎…i-viewport-transitions/webpack.config.js‎examples/wip/first-person-map/webpack.config.js renamed to examples/experimental/multi-viewport-transitions/webpack.config.js b/‎…s/wip/first-person-map/webpack.config.js‎ ‎…i-viewport-transitions/webpack.config.js‎examples/wip/first-person-map/webpack.config.js renamed to examples/experimental/multi-viewport-transitions/webpack.config.js
diff --git a/‎examples/wip/first-person-map/app.js‎ ‎…mples/experimental/multi-viewport/app.js‎examples/wip/first-person-map/app.js renamed to examples/experimental/multi-viewport/app.js b/‎examples/wip/first-person-map/app.js‎ ‎…mples/experimental/multi-viewport/app.js‎examples/wip/first-person-map/app.js renamed to examples/experimental/multi-viewport/app.js
diff --git a/‎…viewport-animation-3d-heatmap/index.html‎ ‎…s/experimental/multi-viewport/index.html‎examples/wip/viewport-animation-3d-heatmap/index.html renamed to examples/experimental/multi-viewport/index.html b/‎…viewport-animation-3d-heatmap/index.html‎ ‎…s/experimental/multi-viewport/index.html‎examples/wip/viewport-animation-3d-heatmap/index.html renamed to examples/experimental/multi-viewport/index.html
diff --git a/‎…-animation-first-person-map/package.json‎ ‎…experimental/multi-viewport/package.json‎examples/wip/viewport-animation-first-person-map/package.json renamed to examples/experimental/multi-viewport/package.json b/‎…-animation-first-person-map/package.json‎ ‎…experimental/multi-viewport/package.json‎examples/wip/viewport-animation-first-person-map/package.json renamed to examples/experimental/multi-viewport/package.json
diff --git a/‎…t-animation-3d-heatmap/webpack.config.js‎ ‎…imental/multi-viewport/webpack.config.js‎examples/wip/viewport-animation-3d-heatmap/webpack.config.js renamed to examples/experimental/multi-viewport/webpack.config.js b/‎…t-animation-3d-heatmap/webpack.config.js‎ ‎…imental/multi-viewport/webpack.config.js‎examples/wip/viewport-animation-3d-heatmap/webpack.config.js renamed to examples/experimental/multi-viewport/webpack.config.js
@@ -69,3 +69,16 @@ calculatePickingColors(attribute) {
 [`layer.decodePickingColor()`](/docs/api-reference/base-layer.md#-decodepickingcolor-) is likely sufficient, but you may need to implement your own pair.
 - By default, the `object` field of the picking `info` object is indexed from the layer's `data` prop. Custom layers often need to define on their own terms what  constitutes meaningful information to the user's callbacks. A layer can achieve this  by overriding [`layer.getPickingInfo()`](/docs/api-reference/base-layer.md#-getpickinginfo-) to add or modify fields to the `info` object.
 - For more information about how to implement picking in shaders see: [`renderPickingBuffer`](/docswriting-shaders.md#-float-renderpickingbuffer-)
+
+
+## Custom Shaders
+
+Deck.gl layers use luma.gl's [`Picking Module`](http://uber.github.io/luma.gl/#/documentation/api-reference/shader-module). If you are writing custom shaders for your layers, please refer to above luma.gl documentation on how to add picking logic to your shaders. Also make sure to create `Model` object with `picking` module. ()
+
+```
+const model = new Model(gl, {
+  fs: CUSTOM_FS,
+  vs: CUSTOM_VS,
+  modules: ['picking', ...],
+});
+```
@@ -31,7 +31,7 @@ The picking engine returns "picking info" objects which contains a variety of fi
 
 ## Calling the Picking Engine Directly
 
-The picking engine is exposed through the [`DeckGL.queryObject`]((/docs/api-reference/deckgl.md) and [`DeckGL.queryVisibleObject`]((/docs/api-reference/deckgl.md) methods. These methods allow you to query what layers and objects within those layers are under a specific point or within a specified rectangle. They return `Picking Info` objects as described below.
+The picking engine is exposed through the [`DeckGL.pickObject`]((/docs/api-reference/deckgl.md) and [`DeckGL.pickObjects`]((/docs/api-reference/deckgl.md) methods. These methods allow you to query what layers and objects within those layers are under a specific point or within a specified rectangle. They return `Picking Info` objects as described below.
 
 `pickObject` allows an application to define its own event handling. When it comes to how to actually do event handling in a browser, there are many options. In a React application, perhaps the simplest is to just use React's "synthetic" event handling together with `pickObject`: