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

    Interface TilePreparationTrace

    What an offline preparation asked for, and what it left out — kept in the cache manifest so the device can say it later, off-network. Before it, a skipped zoom or a stopped enumeration was only LOGGED, and a console on a device in the field is read by nobody.

    interface TilePreparationTrace {
        zone:
            | {
                bounds: { north: number; south: number; east: number; west: number };
                minZoom: number;
                maxZoom: number;
            }
            | null;
        skippedZooms: TileZoomSkip[];
        capped: boolean;
        refusedOrigins?: { source: string; origin: string }[];
    }
    Index
    zone:
        | {
            bounds: { north: number; south: number; east: number; west: number };
            minZoom: number;
            maxZoom: number;
        }
        | null

    The download zone the user chose for vector basemaps, or null when none was chosen.

    skippedZooms: TileZoomSkip[]

    Zoom levels left out because each held too many tiles.

    capped: boolean

    true when the enumeration stopped at the total tile cap — the rest was never listed.

    refusedOrigins?: { source: string; origin: string }[]

    What the origin rule refused: one entry per source and origin — source names the basemap or the tiled layer (basemap street, layer l1), origin the origin not declared for the preparation. Empty when nothing was refused; absent from a manifest written before 3.15.0, which only logged it.