rangefinder
search a catalogue or a tile server, draw a region, compose from the raw pixels
source
a published starc store: manifest.json, a listable
bucket, or consolidated tables (see docs/starc.md)
reads index/inventory.parquet, registry/tiles.parquet and
registry/BANDS.txt; the bucket itself cannot be listed
a GDAL VRT that mosaics many COGs: it is read once as the
index of every file and where it sits
any public, CORS-enabled GeoTIFF; the header gives the
footprint, CRS and bands
a Zarr v2 or v3 store with consolidated metadata, or a
Kerchunk / VirtualiZarr reference JSON (NetCDF-4, HDF5, GRIB2 read in place), with regular
1D x/y coordinates; whole chunks are read, so the chunk shape sets the cost of a view
tiles are warped onto the map grid like any COG, so
polar and lon/lat pyramids work too; the server must allow CORS
region
no region yet: drag a box after "draw on map"
scenes
leave a date blank for an open range
composite
| min | max | |
|---|---|---|
| R | ||
| G | ||
| B |
limits fill in from the percentiles; typing one switches to manual
ready
point
click the image to pin a point and plot its values through the days
export
the GeoTIFF holds the values; the VRT points GDAL at the source files
inspect tiles
tile sources: grid, probe and walk work on the current map
view; any source: "last read" shows what a load fetched
Sources: a STAC
/search (default Earth Search, Sentinel-2
L2A on AWS Open Data), a published starc store, the wildtiles inventory,
a GDAL VRT mosaic, pasted COG URLs, an XYZ / WMTS tile server, or a
Zarr store. The
timeline under the map scrubs the days (drag it, or the arrow keys);
days already read come back instantly. Pixels are read straight from
the COGs (or tiles) by HTTP range request at the overview level that
suits the region, warped onto one Web Mercator grid and mosaicked
least-cloudy-first. Stretch, ramps, hillshade and composition happen
here on the raw numbers. The URL hash is a permalink.