GeoLeaf Core API - v3.19.0
    Preparing search index...

    Interface GeoLeafConfig

    Root GeoLeaf configuration object (JSON shape)

    interface GeoLeafConfig {
        map?: MapConfig;
        data?: DataConfig;
        ui?: UIConfig;
        logging?: LoggingConfig;
        basemaps?: Record<string, BasemapConfig>;
        layers?: LayerConfig[];
        modules?: Record<string, Record<string, unknown>>;
        layerManagerConfig?: Record<string, unknown>;
        performance?: Record<string, unknown>;
        debug?: boolean;
        profiles?: Record<string, unknown>;
    }
    Index
    map? data? ui? logging? basemaps? layers? modules? layerManagerConfig? performance? debug? profiles?
    map?: MapConfig
    data?: DataConfig
    ui?: UIConfig
    logging?: LoggingConfig

    Logging verbosity.

    basemaps?: Record<string, BasemapConfig>

    Named basemap definitions, keyed by basemap ID.

    layers?: LayerConfig[]

    GeoJSON / vector layer references loaded from configFile paths.

    modules?: Record<string, Record<string, unknown>>

    Per-plugin configuration blocks, keyed by module id (Plugin Contract v1, INV-CONFIG) — e.g. modules.offline, modules.editor, modules.print. The keys inside each block belong to the owning plugin/capability; the core treats them as opaque.

    ⚠️ This example cited modules.addpoi until 17/08/2026: that plugin MERGED into editor, and the key it named can no longer be read by anyone. A canonical example designating a vanished module gets copied around.

    layerManagerConfig?: Record<string, unknown>

    Layer manager panel configuration (e.g. title).

    performance?: Record<string, unknown>

    Performance tuning options.

    debug?: boolean

    Enable verbose debug logging.

    profiles?: Record<string, unknown>

    Runtime cache of loaded profile payloads, keyed by profileId. Populated by ProfileModule.

    Settings
    Member Visibility

    On This Page
    Properties