Open-Meteo GloFAS river-discharge series near Tbilisi

Open-Meteo's Flood API exposes daily river-discharge forecasts and ensemble statistics derived from the European Commission's GloFAS model at a coordinate near Tbilisi. The tested query returned past and forecast daily discharge, mean, minimum, maximum, median and 25th/75th percentiles in cubic metres per second. It is model-grid output, not a gauge measurement or official flood warning; the very small tested values make reach selection and river-network alignment especially important.

Provenance and access

How the data is reached

Unauthenticated HTTPS JSON for open-access use. Point is snapped to a model cell and returned in GMT.

Reuse status

CC BY 4.0 attribution to Open-Meteo plus underlying Copernicus/GloFAS acknowledgement and Open-Meteo terms

Read license or terms ↗

Tbilisi flood query

https://flood-api.open-meteo.com/v1/flood?latitude=41.7151&longitude=44.8271&daily=river_discharge,river_discharge_mean,river_discharge_max,river_discharge_min,river_discharge_median,river_discharge_p25,river_discharge_p75&past_days=5&forecast_days=5 ↗

Method: GET
Format: JSON
Authentication: None

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

Flood response metadata

Returned model-cell context.

4 fields

Field / path	Type	Null?	Example	Meaning	Freshness
`latitude / longitude / elevation`	numbers	No	41.725006 / 44.825012 / 590	Selected model-grid coordinate and elevation	reference
`generationtime_ms`	number	No	1.6794	Server computation time	derived
`utc_offset_seconds / timezone / timezone_abbreviation`	integer / strings	No	0 / GMT / GMT	Time context	reference
`daily_units`	object	No	all discharge variables: m³/s	Units dictionary	reference

Daily river-discharge arrays

All arrays align to daily.time.

5 fields

Field / path	Type	Null?	Example	Meaning	Freshness
`daily.time`	array<date>	No	2026-07-17…2026-07-26	Past and forecast date axis	derived
`daily.river_discharge`	array<m³/s>	No	[0.05,0.03,0.02,0.16,0.20,0.02,…]	Primary daily modeled discharge	derived
`daily.river_discharge_mean / median`	arrays<m³/s>	No	0.21 / 0.20 for 2026-07-21	Ensemble central tendency	derived
`daily.river_discharge_min / max`	arrays<m³/s>	No	0.19 / 0.36	Ensemble range	derived
`daily.river_discharge_p25 / p75`	arrays<m³/s>	No	0.20 / 0.21	25th and 75th percentiles	derived

Representative evidence

Sample records

Tbilisi-near grid discharge

Retrieved 2026-07-22 13:45 Asia/Tbilisi

JSON

{"latitude":41.725006,"longitude":44.825012,"daily_units":{"river_discharge":"m³/s"},"daily":{"time":["2026-07-21","2026-07-22","2026-07-23"],"river_discharge":[0.2,0.02,0.02],"river_discharge_mean":[0.21,0.02,0.01],"river_discharge_max":[0.36,0.03,0.03]}}

Boundaries

Reliability, caveats, and privacy

What held up

Endpoint returned complete past and forecast arrays
Ensemble percentiles expose uncertainty
Returned grid coordinate is explicit

What can go wrong

Not an official warning or gauge observation
Nearest model cell may map to a minor reach rather than the desired Mtkvari segment
Zero or tiny flow can indicate poor reach selection or grid limitations
Use river geometry and local gauge/warning context before interpretation

Cross-source possibilities

Ideas using this source

Environment & memory

Unseen Landfill Gravity

What lies geometrically downhill or downstream from a landfill parcel?

Joined with 3 other sources →

Source trail

Primary pages and documentation

DocumentationOpen-Meteo Flood API ↗
https://open-meteo.com/en/docs/flood-api
ContextGloFAS service ↗
https://global-flood.emergency.copernicus.eu/
DocumentationOpen-Meteo terms ↗
https://open-meteo.com/en/terms