docs/api-reference/geo-layers/mvt-layer.md
import {MVTLayerDemo} from '@site/src/doc-demos/geo-layers';
<MVTLayerDemo />The MVTLayer is a derived TileLayer that makes it possible to visualize very large datasets through MVTs (Mapbox Vector Tiles). Behaving like TileLayer, it will only load, decode and render MVTs containing features that are visible within the current viewport.
Data is loaded from URL templates in the data property.
This layer also handles feature clipping so that there are no features divided by tile divisions.
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
<Tabs groupId="language"> <TabItem value="js" label="JavaScript">import {Deck} from '@deck.gl/core';
import {MVTLayer} from '@deck.gl/geo-layers';
const layer = new MVTLayer({
id: 'MVTLayer',
data: [
'https://tiles-a.basemaps.cartocdn.com/vectortiles/carto.streets/v1/{z}/{x}/{y}.mvt'
],
minZoom: 0,
maxZoom: 14,
getFillColor: f => {
switch (f.properties.layerName) {
case 'poi':
return [255, 0, 0];
case 'water':
return [120, 150, 180];
case 'building':
return [218, 218, 218];
default:
return [240, 240, 240];
}
},
getLineWidth: f => {
switch (f.properties.class) {
case 'street':
return 6;
case 'motorway':
return 10;
default:
return 1;
}
},
getLineColor: [192, 192, 192],
getPointRadius: 2,
pointRadiusUnits: 'pixels',
stroked: false,
picking: true
});
new Deck({
initialViewState: {
longitude: -122.4,
latitude: 37.74,
zoom: 11
},
controller: true,
getTooltip: ({object}) => object && (object.properties.name || object.properties.layerName),
layers: [layer]
});
import {Deck} from '@deck.gl/core';
import {MVTLayer, MVTLayerPickingInfo} from '@deck.gl/geo-layers';
import type {Feature, Geometry} from 'geojson';
type PropertiesType = {
name?: string;
rank: number;
layerName: string;
class: string;
};
const layer = new MVTLayer<PropertiesType>({
id: 'MVTLayer',
data: [
'https://tiles-a.basemaps.cartocdn.com/vectortiles/carto.streets/v1/{z}/{x}/{y}.mvt'
],
minZoom: 0,
maxZoom: 14,
getFillColor: (f: Feature<Geometry, PropertiesType>) => {
switch (f.properties.layerName) {
case 'poi':
return [255, 0, 0];
case 'water':
return [120, 150, 180];
case 'building':
return [218, 218, 218];
default:
return [240, 240, 240];
}
},
getLineWidth: (f: Feature<Geometry, PropertiesType>) => {
switch (f.properties.class) {
case 'street':
return 6;
case 'motorway':
return 10;
default:
return 1;
}
},
getLineColor: [192, 192, 192],
getPointRadius: 2,
pointRadiusUnits: 'pixels',
stroked: false,
picking: true
});
new Deck({
initialViewState: {
longitude: -122.4,
latitude: 37.74,
zoom: 11
},
controller: true,
getTooltip: ({object}: MVTLayerPickingInfo<PropertiesType>) => object && (object.properties.name || object.properties.layerName),
layers: [layer]
});
import React from 'react';
import {DeckGL} from '@deck.gl/react';
import {MVTLayer} from '@deck.gl/geo-layers';
import type {MVTLayerPickingInfo} from '@deck.gl/geo-layers';
import type {Feature, Geometry} from 'geojson';
type PropertiesType = {
name?: string;
rank: number;
layerName: string;
class: string;
};
function App() {
const layer = new MVTLayer<PropertiesType>({
id: 'MVTLayer',
data: [
'https://tiles-a.basemaps.cartocdn.com/vectortiles/carto.streets/v1/{z}/{x}/{y}.mvt'
],
minZoom: 0,
maxZoom: 14,
getFillColor: (f: Feature<Geometry, PropertiesType>) => {
switch (f.properties.layerName) {
case 'poi':
return [255, 0, 0];
case 'water':
return [120, 150, 180];
case 'building':
return [218, 218, 218];
default:
return [240, 240, 240];
}
},
getLineWidth: (f: Feature<Geometry, PropertiesType>) => {
switch (f.properties.class) {
case 'street':
return 6;
case 'motorway':
return 10;
default:
return 1;
}
},
getLineColor: [192, 192, 192],
getPointRadius: 2,
pointRadiusUnits: 'pixels',
stroked: false,
picking: true
});
return <DeckGL
initialViewState={{
longitude: -122.4,
latitude: 37.74,
zoom: 11
}}
controller
getTooltip={({object}: MVTLayerPickingInfo<PropertiesType>) => object && (object.properties.name || object.properties.layerName)}
layers={[layer]}
/>;
}
To install the dependencies from NPM:
npm install deck.gl
# or
npm install @deck.gl/core @deck.gl/layers @deck.gl/extensions @deck.gl/geo-layers
import {MVTLayer} from '@deck.gl/geo-layers';
import type {MVTLayerProps, MVTLayerPickingInfo} from '@deck.gl/geo-layers';
new MVTLayer<FeaturePropertiesT>(...props: MVTLayerProps<FeaturePropertiesT>[]);
To use pre-bundled scripts:
<script src="https://unpkg.com/deck.gl@^9.0.0/dist.min.js"></script>
<!-- or -->
<script src="https://unpkg.com/@deck.gl/core@^9.0.0/dist.min.js"></script>
<script src="https://unpkg.com/@deck.gl/layers@^9.0.0/dist.min.js"></script>
<script src="https://unpkg.com/@deck.gl/geo-layers@^9.0.0/dist.min.js"></script>
new deck.MVTLayer({});
Inherits all properties from TileLayer and base Layer, with exceptions indicated below.
If using the default renderSubLayers, supports all GeoJSONLayer properties to style features.
data (string | string[] | object) {#data}The remote data for the MVT layer.
See TileLayer's data prop documentation for the URL template syntax.
The getTileData prop from the TileLayer class will not be called.
uniqueIdProperty (string, optional) {#uniqueidproperty}Needed for highlighting a feature split across two or more tiles if no feature id is provided.
An string pointing to a tile attribute containing a unique identifier for features across tiles.
highlightedFeatureId (number | string, optional) {#highlightedfeatureid}nullWhen provided, a feature with ID corresponding to the supplied value will be highlighted with highlightColor.
If uniqueIdProperty is provided, value within that feature property will be used for ID comparison. If not, feature id will be used.
loadOptions (object, optional) {#loadoptions}On top of the default options, also accepts options for the following loaders:
Note that by default, the MVTLoader parses data using web workers, with code loaded from a CDN. To change this behavior, see loaders and workers.
binary (boolean, optional) {#binary}trueUse tile data in binary format to improve performance (2-3x faster on large datasets). It removes the need for serialization and deserialization of data transferred by the worker back to the main process. See here for details on this format.
Remarks:
GeoJsonLayer in the renderSubLayers callback.onDataLoad (Function, optional) {#ondataload}Called if data is a TileJSON URL when it is successfully fetched
Receives arguments:
tileJSON (object) - the loaded TileJSONgetRenderedFeatures (Function) {#getrenderedfeatures}Get the rendered features in the current viewport.
If a uniqueIdProperty is provided only unique properties are returned.
Requires pickable prop to be true.
Parameters:
maxFeatures (number, optional): Max number of features to retrieve when getRenderedFeatures is called. Default to null.Returns:
Remarks:
getRenderedFeatures every time onViewStateChange is executed, use a debounce function instead.onViewStateChange and onViewportLoad.Aside from all members of the Tile class, tile instances from the MVTLayer also include the following fields:
dataInWGS84 (Feature[]) {#datainwgs84}A list of features in world coordinates (WGS84).
Usage example:
const onViewportLoad = tiles => {
tiles.forEach(tile => {
// data in world coordinates (WGS84)
const dataInWGS84 = tile.dataInWGS84;
});
};
new MVTLayer({
id: "..."
data: "..."
onViewportLoad
})