Skip to main content

Use layers as a custom Google Maps overlay.


Include the Standalone Bundle

<script src="^9.0.0/dist.min.js"></script>
<!-- or -->
<script src="^9.0.0/dist.min.js"></script>
<script src="^9.0.0/dist.min.js"></script>
<!-- usage -->
<script type="text/javascript">
const {GoogleMapsOverlay} = deck;

Install from NPM

npm install
# or
npm install
import {GoogleMapsOverlay} from '';

Vector/Raster maps

Starting with Google Maps v3.45 there are two modes of rendering Vector and Raster. To control which rendering mode is used, you need to configure the Google Map using the Google Cloud Platform.

From v8.6, the GoogleMapsOverlay class automatically detects at runtime which rendering type is used. The Vector rendering mode is in general more performant, and the GoogleMapsOverlay class offers several features not available when using Raster rendering:

  • Shared 3D space: objects drawn by the GoogleMapsOverlay class appear inside the Google Maps scene, correctly intersecting with 3D buildings and behind the contextual labels drawn by Google Maps
  • Tilting and rotating the view is supported
  • Rendering uses the same WebGL2 context as Google Maps, improving performance

Supported Features and Limitations

Supported features:

  • Layers
  • Effects
  • Auto-highlighting
  • Attribute transitions
  • onHover and onClick callbacks
  • Tooltip
  • Tilting & Rotation (Vector maps only)

Not supported features:

  • Views
  • Controller
  • React integration
  • Gesture event callbacks (e.g. onDrag*)