This is the documentation of version 0.63.0. Go to the latest version, 1.0.0-rc.5.
TomTom Maps for JavaScript
    Preparing search index...

    Class PlacesModule

    Map module for displaying and managing place markers.

    The PlacesModule provides functionality to display location markers (pins) on the map for points of interest, search results, or custom locations. It supports various marker styles, custom icons, text labels, and interactive events.

    Features:

    • Marker types (PlacesMarkerType): pins, circles, base-map POI look-alikes and clustered pins
    • One colour for the module's own drawing (PlacesModuleConfig.color)
    • Custom icons per POI category
    • Text labels with styling options
    • Data-driven styling via MapLibre expressions
    • Interactive events (click, hover, etc.)
    • Support for custom feature properties
    • EV charging station availability display (opt-in)
    • Entry points of places, for all of them or only hovered or clicked ones (opt-in)

    EV Charging Station Availability: When displaying EV charging stations with availability data from getPlacesWithEVAvailability, the module can:

    • Show available/total charging points (e.g., "3/10")
    • Color-code availability (green = good, orange = limited, red = none/low)
    • Display as formatted text within the station's label

    This feature is disabled by default. To enable it, set evAvailability.visible to true in the configuration.

    Common Use Cases:

    • Search result visualization
    • Custom location markers
    • Store locators
    • EV charging station maps with real-time availability
    • Delivery/pickup points
    • Saved locations display
    // Create places module with pin markers
    const placesModule = await PlacesModule.create(map, {
    icon: {
    categoryIcons: []
    },
    label: {
    title: (place) => place.properties.poi?.name || 'Unknown'
    },
    markerType: 'pin'
    });

    // Display places from search
    await placesModule.show(searchResults);

    // EV Charging Stations - Opt-in to availability display
    const evStations = await PlacesModule.create(map, {
    evAvailability: { visible: true }
    });
    const results = await discoverPlaces({ filters: { poiCategories: ['CHARGING_LOCATION'] } });
    evStations.show(await getPlacesWithEVAvailability(results)); // Shows availability

    // Granular control: Enable for searched stations only, background stations without
    const bgStations = await PlacesModule.create(map); // EV availability disabled
    const searched = await PlacesModule.create(map, {
    evAvailability: { visible: true }
    });

    // Handle clicks
    placesModule.events.on('click', (feature) => {
    console.log('Clicked:', feature.properties);
    });

    placesModule.events.on('hover', (feature) => {
    showTooltip(feature.properties.poi?.name);
    });

    Hierarchy (View Summary)

    Index
    • get sourceAndLayerIDs(): Record<keyof SOURCES_WITH_LAYERS, SourceWithLayerIDs>

      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.

      Returns Record<keyof SOURCES_WITH_LAYERS, SourceWithLayerIDs>

      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:

      • Directly manipulate layers using MapLibre's native API
      • Identify which layers on the map belong to this module
      • Set layer ordering or positioning relative to other layers
      • Access source or layer properties through MapLibre methods
      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');
      });
    • Removes all places from the map.

      Returns Promise<void>

      • Clears all displayed places, their event states and the shown connections
      • Does not reset styling configuration
      • Module remains initialized and ready for new data
      await placesModule.clear();
      
    • Removes all connection lines from the map, leaving displayed places intact.

      Returns Promise<void>

      await placesModule.clearConnections();
      
    • 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.

      Returns NonNullable<PlacesModuleConfig> | 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, 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.

      Returns EventStateIds

      The read side of putEventState and cleanEventStates: it reflects 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 putEventState.

      // Keep a list in sync with the selected feature
      const { click: [selectedID] = [] } = module.getEventStates();

      // Is this feature hovered?
      const hovered = module.getEventStates().hover?.includes(feature.id) ?? false;
    • Returns the currently shown places.

      Returns { connections: PlaceConnectionDisplay[]; places: Places<DisplayPlaceProps> }

      The places currently displayed on the map.

      places are the places given to show() as drawn: each carries the PlaceDisplayProps and its current eventState. connections are the ones given to showConnections(), including any skipped for an id no shown place has.

      const shown = placesModule.getShown();
      console.log(`Showing ${shown.places.features.length} places`);
    • 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.

      Returns boolean

    • Puts an event state on one of the shown features, as a user interaction would.

      Parameters

      Returns void

      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, not through a new show, a clear or a setStyle with resetState.

      // Select a feature from a list, as a click would
      module.putEventState({ id: feature.id, state: 'click' });

      // Hover a second one without taking the hover off the first
      module.putEventState({ index: 2, state: 'hover', mode: 'add' });
    • 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).

      Returns void

      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, color: '#E63312' });

      // Later, reset to defaults
      myModule.resetConfig();
      • applyConfig to apply a new configuration
      • getConfig to retrieve the current configuration before resetting
    • Shows or hides everything the module draws.

      Parameters

      • visible: boolean

      Returns void

      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.

      module.setVisible(false);
      await module.show(data); // stays hidden
      module.setVisible(true);
    • Displays the given places on the map.

      Parameters

      • places: ShownPlaces

        Place data to display. Can be a single Place, array of Places, or a Places FeatureCollection.

      Returns Promise<void>

      Behavior:

      • Replaces any previously shown places, and never merges with them
      • Drops the event states of the places it replaces, even of a place shown again under the same id: an event state lives on the shown feature, so re-select with putEventState by id. Places that carry properties.eventState, such as getShown().places, keep theirs
      • Drops the shown connections (see PlaceConnectionDisplay)
      • Applies current module styling configuration
      • Automatically generates labels if label config is set
      • Waits for module to be ready before displaying

      Data Sources:

      • TomTom Search API results
      • Custom place objects matching the Place interface
      • GeoJSON Point features

      ShownPlaces names the places services whose results are not places, and what shows them.

      Display search results:

      import { discoverPlaces } from '@tomtom-org/maps-sdk/services';

      const results = await discoverPlaces({ query: 'coffee' });
      await placesModule.show(results);

      Display single place:

      await placesModule.show({
      type: 'Feature',
      geometry: { type: 'Point', coordinates: [4.9041, 52.3676] },
      properties: {
      address: { freeformAddress: 'Amsterdam' },
      poi: { name: 'Amsterdam Central' }
      }
      });

      Display multiple places:

      await placesModule.show([place1, place2, place3]);
      
    • Displays connection lines between pairs of places on the map.

      Parameters

      • connections: PlaceConnectionDisplay[]

        List of connections to render. Each connection has a from and to endpoint, expressed either as a Place or as the id of a place currently shown by this module.

      Returns Promise<void>

      Behavior:

      • Replaces any previously shown connections
      • Connections whose id reference cannot be resolved against the currently shown places are silently skipped
      • When PlaceConnectionsConfig.label is set on the module config, the returned string is rendered as a label along each line, slightly offset to the side. Without a label function, no label is shown.
      • Calling show() or clear() pre-clears connections, since their endpoints may no longer be on the map.
      const places = await PlacesModule.create(map, {
      connections: {
      label: (c) => `${c.distanceMeters} m`
      }
      });
      await places.show([station, ...cafes]);
      await places.showConnections(
      cafes.features.map((cafe) => ({
      from: station.id,
      to: cafe.id,
      distanceMeters: Math.round(cafe.properties.dist ?? 0),
      })),
      );