Map Tools#

Basemaps#

Available basemaps, toggleable and switchable from the map layer controls (bottom of the map):

Which layers are enabled, the active basemap, and per-layer color correction (saturation/contrast/brightness) are stored locally per device, not synced to the server — picking a style is a personal preference, not a tenant setting. A custom tile URL can also be added from Settings → Map layers.

Overlays#

Tenant-configured extra tile layers shown on top of the basemap — a sectional chart, custom imagery, or any other {z}/{x}/{y} tile source — added by an Admin from Settings → Overlays. Unlike basemaps, which are per-device and mutually exclusive, overlays are shared tenant config and independently toggleable: any number can be on at once, and everyone sees the same list.

An overlay’s starting on/off state is set by an Admin, and can optionally differ by basemap (e.g. on by default over Topo, off over Satellite) via a per-basemap override, falling back to a general default for any basemap not explicitly set. Toggling an overlay yourself overrides that default on your device, via the overlay legend — the layered-squares button in the map controls bar, present on every map (dashboard, analytics, and the Regions and Named Points editors) once at least one overlay is configured. Your override applies only to the basemap you made it on; switching basemaps resets overlays back to that basemap’s default.

Elevation tool#

A toggleable overlay that tints the map relative to a reference elevation you set by clicking the map, plus a cursor elevation readout. Backed by a public terrain tile archive, decoded client-side — no separate elevation API calls. Mutually exclusive with the point picker (activating one deactivates the other).

Regions & Named Points#

Both are admin-managed, tenant-wide GeoJSON data sets edited from Settings → Admin → Global Settings, either by importing/exporting a .geojson file or using the built-in map editor.

Regions — polygons used to group flights geographically for Analytics. Each feature needs a Name property. Importing replaces all existing regions.

Named points — point landmarks used to label the live position (“12 km NW of Kodiak”) and to skip a slower external geocoding lookup when a point falls within a named point’s radius (maxKm, defaulting to 10 km). Each feature needs a name property and an optional maxKm. Importing replaces all existing named points.