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

    Interface LayerDataConfig

    Data source configuration block in a layer config (data.vectorTiles / data.ogcApi).

    interface LayerDataConfig {
        directory?: string;
        file?: string;
        vectorTiles?: Record<string, unknown>;
        ogcApi?: OgcApiConfig;
        mapping?: string | Record<string, unknown>;
        itemsPath?: string;
        headers?: Record<string, string>;
    }
    Index

    Properties

    directory? file? vectorTiles? ogcApi? mapping? itemsPath? headers?

    Properties

    directory?: string
    file?: string
    vectorTiles?: Record<string, unknown>
    ogcApi?: OgcApiConfig

    OGC API Features source — when present, the layer is loaded from an OGC API endpoint.

    mapping?: string | Record<string, unknown>

    Name of a per-source block in mapping.json (e.g. "gbif"). When set, the raw fetched data is normalized to the GeoLeaf POI shape via that block before conversion. (ANO-083) (A legacy inline object form is tolerated by the schema but not consumed here.)

    itemsPath?: string

    Dot-path to the items array inside a non-array response (e.g. "results" for the GBIF Occurrence API { results: [...] }). Used with mapping to locate the array to normalize. When absent, the response must already be an array.

    headers?: Record<string, string>

    Custom HTTP request headers for a remote dataUrl GeoJSON source. Use for content negotiation (e.g. { "Accept": "application/geo+json" } for a PostgREST/PostGIS endpoint) or other static request headers. When present, the layer is fetched on the main thread (the worker fetch path does not forward per-layer headers); auth headers stay centralized in the Connector plugin.

    Settings

    Member Visibility

    On This Page

    Properties