import React from 'react';
import { type MapMarkerData } from './map-marker';
import { type GeoJsonInput } from './map-geojson';
export interface MapStaticProps {
    markers: MapMarkerData[];
    /** Reference outline drawn behind the markers, in the same projection. */
    baseGeojson?: GeoJsonInput | null;
    /** Resolved literal colors, keyed by token name. */
    colors: Record<string, string>;
    /** Fallback marker color when a marker declares no token. */
    defaultColor: string;
    outlineColor: string;
    selectedIndex: number | null;
    selectable: boolean;
    onActivate: (index: number) => void;
    onHoverChange: (index: number, hovering: boolean) => void;
    fitPadding: number;
}
/**
 * Plots the data layer with no Google Maps script at all.
 *
 * @description
 * The basemap tiles are the one thing an API key genuinely buys; everything else
 * the map draws is ordinary DOM. When the key is missing — a blocked corporate
 * network, an exhausted quota, a deployment that may not call Google — this
 * renderer keeps the markers, their proportional sizes, tooltips, selection and
 * keyboard navigation intact instead of replacing the whole panel with a setup
 * prompt.
 *
 * Positions come from a shared Web Mercator projection, so a `baseGeojson`
 * outline stays registered with the points drawn on top of it. Without that
 * outline the view answers "how many" but not "where": pass boundaries whenever
 * the geography matters.
 */
export declare function MapStatic({ markers, baseGeojson, colors, defaultColor, outlineColor, selectedIndex, selectable, onActivate, onHoverChange, fitPadding, }: MapStaticProps): React.JSX.Element;
/** Classes that make the keyless surface visibly not a real map. */
export declare const MAP_STATIC_FRAME_CLASS: string;