Choosing a colormap
Which VEDA tile service to change when a layer needs a new colormap
VEDA draws map tiles with three separate services. A new colormap only works in the service it was added to. So the first question is: what kind of data is your layer?
| If your layer is | Add the colormap to | For developers |
|---|---|---|
| Image files in the VEDA catalog. Most Disasters and GHG layers (COGs). | veda-backend (the raster API) | NASA-IMPACT/veda-backend, raster_api/runtime/src/cmap_data/ |
| A data cube with time and variables. Zarr, NetCDF or GRIB, such as TEMPO or model output. | titiler-multidim | developmentseed/titiler-multidim, src/titiler/multidim/main.py |
| NASA archive data found through CMR. Data read straight from a NASA data center, such as HLS. See titiler-cmr. | titiler-cmr | developmentseed/titiler-cmr, titiler/cmr/main.py |
Tip
Standard colormaps such as viridis and turbo already work in every service. If one fits your layer, set colormap_name in the layer’s configuration and nothing else needs to change.
Good to know
- If several kinds of data need the same custom colormap, it has to be added to each of those services.
- A layer that fails with “unknown colormap” usually means the colormap was added to a different service.
- Vector layers (boundaries, points) aren’t tiled, so their colors are set in the dashboard configuration (veda-config and veda-ui).
- There is a proposal for a shared colormaps library in the earthaccess organization.
Once the colormap is available, pick it in your layer’s sourceParams as described in Dataset Configuration.