Gets the events interface for handling user interactions with POIs.
The module's events, with on / off for handlers and where for scoping.
Supported Events:
click: User clicks on a POIcontextmenu: User right-clicks on a POIhover: Mouse enters a POIlong-hover: Mouse hovers over POI for extended timeEvent Feature Properties:
id: Unique POI identifiername: POI name in native languagecategory: POI categoryiconID: Icon sprite IDgroup: Category grouppriority: Importance level (lower = more important)Gets the source and layer identifiers for all sources managed by this module.
This property provides access to the MapLibre source and layer IDs that were created and are managed by this module. These IDs can be used to interact directly with MapLibre's API or to identify which layers belong to this module.
A record mapping each source name to its corresponding source ID and layer IDs. Each entry contains the MapLibre source identifier and an array of layer identifiers associated with that source.
The returned IDs are useful when you need to:
const ids = myModule.sourceAndLayerIDs;
console.log(ids);
// {
// mySource: {
// sourceID: 'my-source-id',
// layerIDs: ['layer-1', 'layer-2']
// }
// }
// Use with MapLibre API
const map = myModule.mapLibreMap;
ids.mySource.layerIDs.forEach(layerId => {
map.setLayoutProperty(layerId, 'visibility', 'visible');
});
Applies a configuration to this module.
This method updates the module's behavior and appearance based on the provided configuration. The configuration is stored internally and will be automatically reapplied if the map style changes.
The configuration object to apply to the module. Pass undefined to reset
the configuration to default values.
When a configuration is applied, the module updates its visual representation and behavior accordingly. The configuration persists across map style changes, ensuring consistent module behavior even when the map's base style is modified.
The given configuration replaces the current one rather than being merged into it. To change one part of it, use updateConfig.
// Apply a new configuration
myModule.applyConfig({ visible: true, opacity: 0.8 });
// Reset to default configuration
myModule.applyConfig(undefined);
Retrieves a copy of the current module configuration.
This method returns a shallow copy of the configuration object that is currently
applied to the module. If no configuration has been applied, it returns undefined.
A shallow copy of the current configuration object, or undefined if no
configuration is currently applied. The returned object is a copy to prevent
unintended modifications to the internal state.
The returned configuration object is a shallow copy, which means that while the top-level properties are copied, any nested objects or arrays are still referenced from the original configuration. This is sufficient for most use cases but should be kept in mind when dealing with complex configurations.
// Apply a configuration
myModule.applyConfig({ visible: true, opacity: 0.8 });
// Later, retrieve the current configuration
const currentConfig = myModule.getConfig();
console.log(currentConfig); // { visible: true, opacity: 0.8 }
// When no config is applied
myModule.resetConfig();
console.log(myModule.getConfig()); // undefined
Returns features currently visible in the viewport.
An object containing visible POI features with properly typed properties.
Resets the configuration of this module to its default values.
This is a convenience method that clears any previously applied configuration
and restores the module to its initial state. This is equivalent to calling
applyConfig(undefined).
After calling this method, the module will behave as if no configuration was ever applied. Any custom settings, styling, or behavior modifications will be removed and replaced with default values.
// Apply some configuration
myModule.applyConfig({ visible: true, opacity: 0.5 });
// Later, reset to defaults
myModule.resetConfig();
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 nested object that was there — and the result is applied with
applyConfig. This is the same on every module, whatever its applyConfig does with a
whole configuration.
The properties to change.
routing.applyConfig({ displayUnits: 'imperial', color: '#0a3653' });
routing.updateConfig({ color: '#c2185b' }); // displayUnits stays imperial
applyConfig to apply a whole configuration
ProtectedwaitStaticgetRetrieves a POIsModule instance for the given map.
The TomTomMap instance to attach this module to.
Optionalconfig: POIsModuleConfig
Optional initial configuration for visibility and filters.
A promise that resolves to the initialized POIsModule.
POIs Module for controlling Points of Interest displayed in the map style.
This module manages the built-in POI layer from the vector map, allowing you to show/hide POIs and filter them by category. POIs are already part of the map style and include businesses, landmarks, and other points of interest.
Remarks
What this module owns: whether the style's POIs are shown, which categories, and any custom icon a category is drawn with. Their size, label colours and zoom thresholds are
pois.*knobs on StylingModule. The knobpois.microMarkershides the micro markers within the POIs this module shows, and never shows them while this module hides the POIs. See Who owns what. poisKnobCatalogue lists the settings of its configuration a knob holds.Features:
POI Categories:
Difference from PlacesModule:
Example
Basic usage:
Example
Filter specific categories:
Example
Filter using category groups:
Example
Custom icons per category, shared with the places a PlacesModule shows:
Example
Event handling:
See
POIs Guide