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

    Class PlacesModule

    A map module that displays and manages place markers.

    It displays location markers (pins) on the map for points of interest, search results or custom locations, with 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
    • Entry points of places, for all of them or only hovered or clicked ones (opt-in)

    Common use cases:

    • Search result visualization
    • Custom location markers
    • Store locators
    • 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);

    // 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>

      The MapLibre source and layer IDs of all sources this module creates and manages.

      Returns Record<keyof SOURCES_WITH_LAYERS, SourceWithLayerIDs>

      A record mapping each source name to its MapLibre source ID and an array of the IDs of that source's layers.

      Use these IDs 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.
      • Doesn't reset the styling configuration.
      • The module stays 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();
      
    • Returns a shallow copy of the current module configuration, or undefined if none is applied.

      Returns NonNullable<PlacesModuleConfig> | undefined

      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.

      Returns EventStateIds

      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.

      // 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.properties.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 because no shown place has their id.

      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

    • 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).

      Returns void

      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();
      • applyConfig to apply a new configuration
      • getConfig to retrieve the current configuration before resetting
    • 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, but not a new show, a clear or a setStyle with resetState.

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

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

        The places to display, as a single Place, an array of Places or a Places FeatureCollection.

      Returns Promise<void>

      Behaviour:

      • 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 setEventState by id. Places that carry properties.eventState, such as getShown().places, keep theirs.
      • Drops the shown connections (see PlaceConnectionDisplay).
      • Applies the current module styling configuration.
      • Generates labels if the label config is set.
      • Waits for the 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[]

        The connections to render. Each has a from and to endpoint, as a Place or as the id of a place this module currently shows.

      Returns Promise<void>

      • Replaces any previously shown connections.
      • Silently skips connections whose id doesn't resolve against the currently shown places.
      • If the module config sets connections.label.title, the string it returns is rendered as a label along each line, slightly offset to the side. Otherwise, no label is shown.
      • show() and clear() clear the connections first, since their endpoints may no longer be on the map.
      const places = await PlacesModule.create(map, {
      connections: {
      label: { title: (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.distance ?? 0),
      })),
      );