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

    Interface GeoLeafOfflinePullProgressDetail

    Detail payload for geoleaf:offline:pull-progress — one page of a layer pull landed.

    🛑 A SEPARATE EVENT FROM geoleaf:cache:progress, and the motive is measured. The tile/resource download reports through cache/progress-tracker.ts, whose state is a MODULE-LEVEL singleton re-initialised per run. The feature pull runs after that run has already emitted its 100 %: feeding the same tracker would either reset a finished bar or make two producers share one mutable state. Two phases of one gesture, two signals.

    ⚠️ total is the SOURCE's total only when the source served it. OGC API Features carries numberMatched; a server omitting it leaves the loader with nothing but its own running count, and total then equals current — a bar that fills as it goes rather than a fraction of a known whole. totalIsKnown says which of the two the consumer is looking at, because a progress bar that reaches 100 % three times is worse than one that never announces a percentage.

    interface GeoLeafOfflinePullProgressDetail {
        layerId: string;
        current: number;
        total: number;
        totalIsKnown: boolean;
        percentage: number;
    }
    Index
    layerId current total totalIsKnown percentage
    layerId: string

    Layer being pulled.

    current: number

    Entities written so far, this page included.

    total: number

    The source's total when known, otherwise current — see totalIsKnown.

    totalIsKnown: boolean

    false when the server served no numberMatched: total is then a running count.

    percentage: number

    0-100, already scaled — consumers display it, they do not recompute it.

    Settings
    Member Visibility

    On This Page
    Properties