Landmarks topic

Use the landmarks module to work with structured points of interest (POIs) provided by search or map selection and their persistent collections. This system provides models, services, and session objects to create, store, query, and display rich landmark data (names, addresses, coordinates, categories, images and extra metadata) so you can power POI browsing, search, mapping and routing features in your app.

• Landmark: Represents a single place with rich metadata such as coordinates, name, description, address, images, contact data and optional waypoint track data. Use this class to create, read and modify individual POIs that are used throughout the SDK for display, search and routing.
• EntranceLocations: Experimental container for named entrance points and access types (for example pedestrian or vehicle). Still experimental and available only for some landmarks.
• LandmarkCategory: Model that defines a logical hierarchal grouping for landmarks. Each category has an identifier, a localized display name and an optional image; categories are used to classify and filter POIs.
• LandmarkStore: Persistent collection that stores landmarks and categories. Use it to persist user-created POIs, import datasets, manage categories and run store-level operations such as bulk imports or fast update sessions. Used within search, display of custom POIs, alerting and more.
• LandmarkStoreService: High-level service for creating, discovering and registering LandmarkStore instances. Use this to obtain store references, enumerate stores and access special SDK-provided store identifiers.
• LandmarkStoreCollection: View-level collection of store/category visibility settings. Typically accessed from map view preferences, it controls which stores and categories are visible on the map and provides helper methods for toggling and querying those settings.
• LandmarkBrowseSession: Snapshot-based, paged session for iterating landmarks from a LandmarkStore. Create sessions to page, filter and order large stores efficiently without reflecting live changes made after session creation.
• LandmarkStoreListener: Event listener that receives store lifecycle and content change notifications (landmarks added/updated/removed, categories changed, browse-session invalidation).

Landmark components form a complete POI management subsystem: Landmark models hold the individual place data, LandmarkCategory provides classifications, LandmarkStore persists collections and supports imports and bulk operations, while LandmarkStoreService manages store lifecycle. LandmarkStoreCollection exposes store visibility for map views and LandmarkBrowseSession enables efficient paging of store content. Together these pieces let you build consistent UI flows for browsing, searching and editing POIs while enabling reliable map rendering and routing integrations.

Use Landmark for single-object workflows (create, edit, display). Use LandmarkStore when you need persistence, bulk import, category management or store-scoped queries. Use LandmarkBrowseSession to page results for list UIs and avoid re-querying large datasets directly. Register a LandmarkStoreListener to keep your UI synchronized with store changes and prefer LandmarkStoreService to create or discover stores.

Learn more about Landmarks: https://developer.magiclane.com/docs/flutter/guides/core/landmarks