← All sources
DailyLive-testedOfficial public-page backend
Environment / Hydrology
NEA current-day river gauge levels
Official current-day river-gauge records with station IDs, coordinates, water level, date, and warning state, including one Vere–Tbilisi gauge at Svanidze.
01
Provenance and access
How the data is reached
Unauthenticated JSON GET used by the official NEA river page.
Reuse status
Unclear; no explicit data license or API terms found
Official river page
https://meteo.gov.ge/hydrometeorology/Rivers ↗- Method
- GET
- Format
- HTML
- Authentication
- None observed
River-pin JSON
https://meteo.gov.ge/En/Hydrology/GetRiversPin ↗- Method
- GET
- Format
- JSON
- Authentication
- None observed
No published rate limit
02
Field-level detail
What is actually returned
livereferencederivedhistoricalunknown
Gauge record
One GetRiversPin array item.
| Field / path | Type | Null? | Example | Meaning | Freshness |
|---|---|---|---|---|---|
HydrologicalDataRecordId | integer | No | 38764 | Measurement-record ID | reference |
HydroMonitoringStationId | integer | No | 13 | Monitoring-station ID | reference |
ElevationValue | number | No | 116 | Water level in centimetresInterpretation confirmed by official rendered page despite ambiguous field name | live |
HydroMonitoringStationName | string | No | Vere-Tbilisi(Svanidze) | Gauge/station name | reference |
RiverName | string | No | Vere-Tbilisi(Svanidze) | River/display name | reference |
HydroMonitoringStationLatitude | number | No | 41.71410732444746 | Gauge latitude | reference |
HydroMonitoringStationLongitude | number | No | 44.74187171408082 | Gauge longitude | reference |
MeasureTime | date string | No | 7/22/2026 | Observation dateU.S.-style date; no time/offset | live |
HydroWarningStateId | integer | No | 10 | Source warning-state code | derived |
HydroWarningStateDescription | string | No | No Change | Source warning/status description | derived |
Rendered page additions
Values visible on the official page but absent from GetRiversPin.
| Field / path | Type | Null? | Example | Meaning | Freshness |
|---|---|---|---|---|---|
signal_threshold_cm | number (HTML) | Unknown | 210 | Station signal threshold | reference |
danger_threshold_cm | number (HTML) | Unknown | 260 | Station danger threshold | reference |
observation_datetime | datetime (HTML) | No | 22.07.2026 00:00 | Displayed observation time | live |
water_level_cm | number (HTML) | No | 116 | Displayed water level | live |
status | string (HTML) | No | normal range | Human warning status | derived |
03
Representative evidence
Sample records
Vere–Tbilisi gauge
Retrieved 2026-07-22T13:37:00+04:00
{"HydrologicalDataRecordId":38764,"HydroMonitoringStationId":13,"ElevationValue":116,"HydroMonitoringStationName":"Vere-Tbilisi(Svanidze)","RiverName":"Vere-Tbilisi(Svanidze)","HydroMonitoringStationLatitude":41.71410732444746,"HydroMonitoringStationLongitude":44.74187171408082,"MeasureTime":"7/22/2026","HydroWarningStateId":10,"HydroWarningStateDescription":"No Change"}04
Boundaries
Reliability, caveats, and privacy
What held up
- HTTP 200 JSON returned 16 records
- Official page independently confirmed level units and station thresholds
- Latest value can be cached with its MeasureTime
What can go wrong
- Daily/current-day rather than minute-level telemetry
- One Tbilisi gauge is not citywide flood coverage
- API date lacks time/offset
- Warning-state codebook is undocumented
- Page has described river monitoring as test mode
05
Cross-source possibilities
Ideas using this source
06
Source trail
Primary pages and documentation
- PrimaryOfficial NEA river page ↗
https://meteo.gov.ge/hydrometeorology/Rivers - PrimaryRiver JSON ↗
https://meteo.gov.ge/En/Hydrology/GetRiversPin