Rain on a 0.05° grid, per district, against the normal for the same five days.
- Source
- CHIRPS v3
- Resolution
- 0.05° grid (about 5.5 km)
- Updates
- Every 5 days (pentads)
- Latest
- 11–15 Nov 2026 · preliminary
- Licence
- CC BY 4.0
Data · India · Live
geolith turns one open raster into a map and one number for every district, so a rainfall or greenness question has a public answer for all 787 of them.
Most of India got less rain than usual
median 0.7 mm · median usual 3.2 mm · 11–15 Nov 2026
Pentad 11–15 Nov 2026
No district data
Rainfall · 11–15 Nov 2026 · Every 5 days (pentads) India, 2 datasets · every district · sources
Catalogue
Each one is a public raster, averaged over the Survey of India district boundaries, with the source printed on every page.
Rain on a 0.05° grid, per district, against the normal for the same five days.
Greenness from Copernicus, per district, against the 2019–2025 average.
On a district page
Open any district: a map, the number for this period beside its usual, and the last twelve periods to see the season move. Nothing needs a key.

Detail
The engine reads the raster’s grid, lays the district boundary over it, and weights each cell by the share of it that falls inside the district. The district’s number is the area-weighted mean of the cells it contains, so a boundary that splits a cell does not lose it.
Detail
A build’s numbers are compared with GDAL's zonal statistics on the same raster and the same boundaries, for all 787 districts. The comparison is the gate: numbers that disagree are not published.
Detail
Districts follow the Survey of India outline, so India is drawn whole and never cut at a claim line. The district shapes come from Overture Maps and OpenStreetMap; the India boundaries are the DataMeet India community's. Each district also carries its Local Government Directory code, so a row joins to government data without matching names. Source: Local Government Directory, Government of India.
See the boundaries on a live page →Use it
Every page and every embed is free: no key, no account, any site may frame one.
Read rainfall by district →Data files (CSV, Parquet, GeoParquet) and the Datasets API come with the Scale plan. A key is needed for both.
Datasets status →The engine is the geolith dataset command: it builds both outputs on one machine, from your own raster and boundaries.
Self-hosting docs →Sources and licences
Questions
A pentad is five days; a dekad is ten. Rainfall arrives in pentads and greenness in dekads, because that is how their sources publish: CHIRPS v3 sums rainfall over five days, and Copernicus composites vegetation over ten.
The period has closed but its source has not finished revising it. Rainfall is preliminary for a few days after the five-day period ends, then final; greenness settles in about the same time. A page says which it is, and a share card marks a preliminary period.
A new rainfall period every five days and a new greenness period every ten, each a few days after the period ends while the source catches up. The page shows the day the data was built.
Data files (CSV, Parquet, GeoParquet) and the Datasets API come with the Scale plan. Every page shows its numbers and its source for free; the files and the API need a Scale key. The engine that makes them can also be run on your own machine.
India today, for every district. The engine reads any raster against any boundary file, so another country is a build, not a rewrite.
The comparison is against the same ten days across 2019 to 2025, built from Sentinel-3 OLCI. A district can be green in absolute terms and still be below its own average for that time of year, which is what the sentence reports.
50,000 geocoding requests and 200,000 map tiles a month free (India tile set today; planet tiles in development). Commercial use with attribution. No card.