# geolith Datasets docs: in development, not deployed

> geolith Datasets is in development and not deployed: raster datasets such as rainfall (CHIRPS v3) turned into a map layer and numbers per district. What it is, the data sources with their attribution, and its status.

Status: In development. In development, not deployed. No hosted API and no downloads yet. The rainfall pages on geolith.app are the first public pages built with the engine. The engine command is geolith dataset; it is not in a geolith release yet.

One raster gives two outputs: a map layer (tiles) and numbers per area, for example the rainfall of a district against its normal. Rainfall from CHIRPS v3 comes first. In development: not deployed, and api.geolith.app has no dataset endpoint.

## Features

- Map layer: Tiles coloured by value, drawn over the basemap.
- Numbers per area: Per district: the value, the normal, the difference and a short series.
- Global formats: The engine and file formats work for any country. India comes first.
- Survey of India map: India is always drawn with the Survey of India outline, never cut.
- Attribution on every output: The engine writes the source line of the data into every file it builds.
- Self-host: The geolith dataset command builds both outputs on one machine.

## Docs

- [Overview](https://docs.geolith.app/datasets/overview.md): What a raster dataset is, its two outputs, self-hosting.
- [Data sources](https://docs.geolith.app/datasets/data-sources.md): CHIRPS, Copernicus and the boundaries, with attribution.
- [Status](https://docs.geolith.app/datasets/status.md): What exists, what does not exist yet, and the gate.
