ProtecteddefaultThe map's colour for what carries no color under a config without a top-level color. It is
the accent when a theme has set one, otherwise a colour that follows the active light/dark theme.
The events interface for handling user interactions with the polygons.
The module's events, with on and off for handlers and where for scoping.
ProtectedlightCurrent light/dark map theme, re-read on every layer/data build so style switches repaint.
The MapLibre source and layer IDs of all sources this module creates and manages.
A record mapping each source name to its MapLibre source ID and an array of the IDs of that source's layers.
Applies a configuration to this module.
The module updates its behaviour and appearance to match. It stores the configuration and reapplies it automatically when the map style changes.
The configuration to apply. Pass undefined to reset it to the default values.
The given configuration replaces the current one rather than being merged into it. To change one part of it, use updateConfig.
Use it for settings your code writes. It takes every setting, typed, including the ones no knob covers (layer specs, callbacks, MapLibre expressions), and checks no value at run time. For settings held as data, from a control, storage or a language model, use setKnobs.
// Apply a new configuration
myModule.applyConfig({ visible: true, color: '#E63312' });
// Reset to default configuration
myModule.applyConfig(undefined);
Takes the event state off one of the shown features.
Takes the given event states, or all of them, off the shown features.
Optionaloptions: ClearEventStatesOptionsReturns a shallow copy of the current module configuration, or undefined if none is applied.
A shallow copy of the current configuration, or undefined. It is a copy so that you
can't modify the internal state by accident.
Only the top-level properties are copied. Nested objects and arrays still reference the original configuration. This is enough for most use cases, but keep it in mind with complex configurations.
// Apply a configuration
myModule.applyConfig({ visible: true, color: '#E63312' });
// Later, retrieve the current configuration
const currentConfig = myModule.getConfig();
console.log(currentConfig); // { visible: true, color: '#E63312' }
// When no config is applied
myModule.resetConfig();
console.log(myModule.getConfig()); // undefined
Returns the ids of the shown features that have an event state, by state.
The read side of setEventState and clearEventStates, reflecting those and
the states user interactions put. The ids are those getShown() and the event handlers hand
back, so each can go straight back into setEventState.
Returns the polygons and labels currently drawn, as prepared for display.
Whether the module is set to be shown: its visible setting, true unless set. A shown
module with nothing shown draws nothing. getShown() returns what is shown.
Resets this module's configuration to its default values.
It clears any applied configuration and restores the module to its initial state, the same
as calling applyConfig(undefined).
The module then behaves as if no configuration was ever applied. Any custom settings, styling or behaviour changes are replaced with default values.
// Apply some configuration
myModule.applyConfig({ visible: true, color: '#E63312' });
// Later, reset to defaults
myModule.resetConfig();
Puts an event state on one of the shown features, as a user interaction would.
The state is what the module's own layers draw (place pins and entry points, route outlines,
geometries, details-module incidents, area-analytics cells), what layers of yours read with
['get', 'eventState'], and what getEventStates returns. It lasts as long as the shown
feature does, through setVisible, style and configuration changes, but not a new
show, a clear or a setStyle with resetState.
Shows or hides everything the module draws.
Stored as visible in the configuration. Showing and clearing data never change it. A hidden
module keeps its data, through style changes too, and draws it again on setVisible(true).
Showing leaves hidden what the configuration turns off: a route section type that is off, the layers a place marker type does not use.
Displays the given polygon geometries on the map.
The polygon features to display, as a FeatureCollection.
Feature properties:
title: The text of the center and border labels, unless label.title or lineLabel.title sets
theirs. Without one, a text label.title, then address.freeformAddress, fills it incolor: Override fill colour per featurefillStyle: Override the module's fill.style per featureid: The id that event states and event handlers use, generated when missing. A feature's
top-level id isn't read, so the top-level id of a geometry data result matches nothingSingle polygon:
await geometries.show({
type: 'FeatureCollection',
features: [
{
type: 'Feature',
bbox: [4.88, 52.37, 4.89, 52.38],
geometry: {
type: 'Polygon',
coordinates: [[[4.88, 52.37], [4.89, 52.37], [4.89, 52.38], [4.88, 52.37]]]
},
properties: {
title: 'Amsterdam Center',
color: '#FF5733'
}
}
]
});
Changes part of the configuration and keeps the rest.
The given properties are laid over the current configuration one level deep, so a nested
object you pass replaces the one that was there. The result is applied with
applyConfig. This works the same on every module, whatever its applyConfig does with
a whole configuration.
The properties to change.
Use it for settings your code writes, as applyConfig: typed, and not checked at run time. To change nested values and keep the ones beside them, or to set values held as data, use setKnobs, which reaches each by its path and checks it.
routing.applyConfig({ displayUnits: { distance: { type: 'imperial_us' } }, color: '#0a3653' });
routing.updateConfig({ color: '#c2185b' }); // displayUnits stays imperial
applyConfig to apply a whole configuration
StaticcreateWaits until the map is ready for any interaction, then creates an instance of the module.
Optionalconfig: GeometriesModuleConfig
The optional module configuration.
GeometriesModule owns the sources and layers it adds, all suffixed per instance.
Every call therefore returns a new, independent instance, so you can put several on the
same map, each managing a different set of geometries with different styles.
The module that displays polygon areas with custom styling on the map.
It visualizes geographic areas (polygons) with customizable colours, borders, and labels. Use it to display search results, administrative boundaries, service areas, or any polygon-based geographic data.
Remarks
Features:
Data format:
Styling:
Example
Basic usage:
Example
Custom styling:
Example
Multiple geometries with different colors:
Example
Event handling:
See
Geometries Guide