The Editable GeoJSON layer accepts a GeoJSON FeatureCollection
and renders the features as editable polygons, lines, and points.
import DeckGL from 'deck.gl';
import { EditableGeoJsonLayer, DrawPolygonMode } from 'nebula.gl';
const myFeatureCollection = {
type: 'FeatureCollection',
features: [
/* insert features here */
]
};
const selectedFeatureIndexes = [];
class App extends React.Component {
state = {
data: myFeatureCollection
};
render() {
const layer = new EditableGeoJsonLayer({
id: 'geojson-layer',
data: this.state.data,
mode: DrawPolygonMode,
selectedFeatureIndexes,
onEdit: ({ updatedData }) => {
this.setState({
data: updatedData,
});
}
});
return <DeckGL {...this.props.viewport} layers={[layer]} />;
}
}
Inherits all deck.gl's Base Layer properties.
- Default:
null
A GeoJSON FeatureCollection
object. The following types of geometry are supported:
Point
LineString
Polygon
MultiPoint
MultiLineString
MultiPolygon
GeometryCollection
is not supported.
Note: passing a single Feature
is not supported. However, you can pass a FeatureCollection
containing a single Feature
and pass selectedFeatureIndexes: [0]
to achieve the same result.
- Default:
DrawPolygonMode
The mode
property defines the mode used to handle user interaction events (e.g. pointer events) in order to accomplish edits. This can either be a constructor for an EditMode
or an instance of EditMode
.
There are a extensive number of modes that come out-of-the-box with nebula.gl. See modes overview.
- Default:
null
An arbitrary object used to further configure the current mode.
Snapping-related modeConfig
properties:
enableSnapping
(Boolean, optional) - Enables snapping for modes that support snapping such as translate mode.additionalSnapTargets
(Object[], optional) - An array of GeoJSON Features that can be snapped to. This property only needs to be specified if you want to snap to features in other deck.gl layers. All features in thisEditableGeoJsonLayer
will be snap targets.
- Default:
[]
The selectedFeatureIndexes
property distinguishes which features to treat as selected.
-
Features are identified by their index in the collection.
-
Selection of a feature causes style accessors to render a different style, defined in function such as
getLineColor
andgetFillColor
. -
Selected features in mode
modify
will render edit handles. Only one feature may be selected while in modedrawLineString
ordrawPolygon
to draw a feature.
Note: make sure to pass in the same array instance on each render if you are not changing selection. Otherwise, nebula.gl may clear state on every render (e.g. may clear a drawing in progress if the viewport changes).
The onEdit
event is the core event provided by this layer and must be handled in order to accept and render edits. The event
argument includes the following properties:
-
updatedData
(Object): A newFeatureCollection
with the edit applied.-
To accept the edit as is, supply this object into the
data
prop on the next render cycle (e.g. by calling React'ssetState
function) -
To reject the edit, do nothing
-
You may also supply a modified version of this object into the
data
prop on the next render cycle (e.g. if you have your own snapping logic).
-
-
editType
(String): The type of edit requested. One of:-
movePosition
: A position was moved. -
addPosition
: A position was added (either at the beginning, middle, or end of a feature's coordinates). -
removePosition
: A position was removed. Note: it may result in multiple positions being removed in order to maintain valid GeoJSON (e.g. removing a point from a triangular hole will remove the hole entirely). -
addFeature
: A new feature was added. Its index is reflected infeatureIndexes
-
finishMovePosition
: A position finished moving (e.g. user finished dragging). -
scaling
: A feature is being scaled. -
scaled
: A feature finished scaling (increase/decrease) (e.g. user finished dragging). -
rotating
: A feature is being rotated. -
rotated
: A feature finished rotating (e.g. user finished dragging). -
translating
: A feature is being translated. -
translated
: A feature finished translating (e.g. user finished dragging). -
startExtruding
: An edge started extruding (e.g. user started dragging). -
extruding
: An edge is extruding. -
extruded
: An edge finished extruding (e.g. user finished dragging). -
split
: A feature finished splitting.
-
-
featureIndexes
(Array<number>): The indexes of the edited/added features. -
editContext
(Object):null
or an object containing additional context about the edit. This is populated by the active mode, see modes overview.
Consider the user removed the third position from a Polygon
's first ring, and that Polygon
was the fourth feature in the FeatureCollection
. The event
argument would look like:
{
updatedData: {...},
editType: 'removePosition',
featureIndexes: [3],
editContext: {
positionIndexes: [1, 2],
position: null
}
}
- Default:
true
Defaulted to true
for interactivity.
- Default:
10
Number of pixels around the mouse cursor used for picking. This value determines, for example, what feature is considered to be clicked and what is close enough to be snapped to.
- Default:
5
Number of layers of overlapping features that will be picked. Useful in cases where features overlap.
EditableGeoJsonLayer
renders the following sub-layers:
geojson
: a GeoJsonLayer that renders the GeoJSON features passed into thedata
property.guides
: a GeoJsonLayer that renders GeoJSON features that aid in editing.tooltips
: a TextLayer that renders tooltips used in some editing modes.
The styling and functionality of EditableGeoJsonLayer
can be customized by providing the _subLayerProps property. For example:
new EditableGeoJsonLayer({
// ...
_subLayerProps: {
geojson: {
getFillColor: (feature) => getFillColorForFeature(feature),
getLineColor: (feature) => getLineColorForFeature(feature),
}
}
})
The features being edited are rendered in the geojson
sub layer whether they are selected or not. If you want to style selected features differently than unselected features, you can accomplish it like this:
const [data] = React.useState(/* some GeoJSON */);
const [selectedFeatureIndexes] = React.useState(/* array of selected features */)
new EditableGeoJsonLayer({
// ...
data,
selectedFeatureIndexes,
_subLayerProps: {
geojson: {
getFillColor: (feature) => {
if (selectedFeatureIndexes.some(i => data.features[i] === feature)) {
return SELECTED_FILL_COLOR;
} else {
return UNSELECTED_FILL_COLOR;
}
}
}
}
})
There are two types of "guides" rendered in the guides
sub layer differentiated by properties.guideType
of each feature.
While creating a new feature in any of the draw
modes, portion of a feature which has not been "committed" yet can hold its own props. For example, in drawLineString
mode, the tentative feature is the last line segment moving under the mouse. For polygons and ellipses, this would be the whole feature during drawing. A tentative feature can be identified by checking if properties.guideType === 'tentative'
.
Edit handles are the points rendered on a feature to indicate interactive capabilities (e.g. vertices that can be moved). Edit Handles can be identified by checking if properties.guideType === 'editHandle'
.
There are also different types of edit handles differentiated by properties.editHandleType
:
existing
: this is an edit handle rendered at an existing position of a featureintermediate
: this is an edit handle rendered between existing positions (e.g. to add new positions)snap-source
: this is an edit handle being moved that can snap to asnap-target
edit handlesnap-target
: this is an edit handle that will be snapped to if the pointer moves close enough
This shows how you can override how guides are rendered:
new EditableGeoJsonLayer({
// ...
_subLayerProps: {
guides: {
getFillColor: (guide) => {
if (guide.properties.guideType === 'tentative') {
return TENTATIVE_FILL_COLOR;
} else {
return EDIT_HANDLE_FILL_COLOR;
}
}
}
}
})
Some modes will render tooltips. For example, the measure modes. These modes will render text in the tooltips
sub layer.
new EditableGeoJsonLayer({
// ...
_subLayerProps: {
tooltips: {
getSize: 32,
}
}
})