River Discharge Forecast - Flood Risk by Coordinates
Pricing
from $1.00 / 1,000 results
River Discharge Forecast - Flood Risk by Coordinates
Daily river discharge forecast for any coordinates as flat rows - the modelled flow in cubic metres per second. Free public API, no key.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
alaudin burki
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Security
Limited permissionsShare
River Discharge Forecast — Flood Risk by Coordinates
Daily river discharge forecast for any coordinates as flat rows — the modelled flow in cubic metres per second. Free public API, no key.
What you get
latitude, longitude, elevationM, date, riverDischargeM3s.
The source returns parallel arrays (times and values separately), so the coordinates are copied from the response root onto every row.
Sample output
Limitations
- A modelled flow, not a gauge reading. It is a hydrological model at the grid cell, so it will differ from a real station on the same river.
- No flood threshold is applied. The number is discharge; whether that is dangerous depends on the river, which this API does not tell you.
- One coordinate per run, up to 92 days ahead.
- A low discharge means little flow, not safety — a dry river and a regulated one both read low.
Pricing
Pay per result.
Fields
| Field | Type | What it holds |
|---|---|---|
latitude | number | Latitude in decimal degrees (WGS 84). A STRING from some sources and a number from others — check the README per Actor. |
longitude | number | Longitude in decimal degrees (WGS 84). A STRING from some sources and a number from others — check the README per Actor. |
elevationM | number | Elevation above sea level in METRES. |
date | string | ISO 8601 date associated with this record. |
riverDischargeM3s | number | River discharge in CUBIC METRES PER SECOND, as forecast. This is a modelled flow from a hydrological model, not a gauge reading. |
What makes this different
Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.
- River Discharge Forecast - Flood Risk by Coordinates declares all 5 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of River Discharge Forecast include latitude, longitude, elevationM, date and riverDischargeM3s.
- River Discharge Forecast needs no API key, login or account of any kind before its first run.
- Every one of River Discharge Forecast's 5 inputs is optional, so it runs with no configuration at all.
- River Discharge Forecast documents
latitudeas: Latitude in decimal degrees (WGS 84). A STRING from some sources and a number from others — check the README per Actor. - Every number published about River Discharge Forecast is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- River Discharge Forecast is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.
FAQ
What does River Discharge Forecast return?
It returns 5 documented output fields — latitude, longitude, elevationM, date and riverDischargeM3s — each with a declared type and a written description. The full schema is below.
What does River Discharge Forecast require to run?
Nothing. All 5 inputs are optional and ship with working defaults.
Does River Discharge Forecast need an API key?
No. It reads only public data and asks for no account.
How is River Discharge Forecast billed?
Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.
