← 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

02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

Gauge record

One GetRiversPin array item.

10 fields
Field / pathTypeNull?ExampleMeaningFreshness
HydrologicalDataRecordIdintegerNo38764Measurement-record IDreference
HydroMonitoringStationIdintegerNo13Monitoring-station IDreference
ElevationValuenumberNo116Water level in centimetresInterpretation confirmed by official rendered page despite ambiguous field namelive
HydroMonitoringStationNamestringNoVere-Tbilisi(Svanidze)Gauge/station namereference
RiverNamestringNoVere-Tbilisi(Svanidze)River/display namereference
HydroMonitoringStationLatitudenumberNo41.71410732444746Gauge latitudereference
HydroMonitoringStationLongitudenumberNo44.74187171408082Gauge longitudereference
MeasureTimedate stringNo7/22/2026Observation dateU.S.-style date; no time/offsetlive
HydroWarningStateIdintegerNo10Source warning-state codederived
HydroWarningStateDescriptionstringNoNo ChangeSource warning/status descriptionderived

Rendered page additions

Values visible on the official page but absent from GetRiversPin.

5 fields
Field / pathTypeNull?ExampleMeaningFreshness
signal_threshold_cmnumber (HTML)Unknown210Station signal thresholdreference
danger_threshold_cmnumber (HTML)Unknown260Station danger thresholdreference
observation_datetimedatetime (HTML)No22.07.2026 00:00Displayed observation timelive
water_level_cmnumber (HTML)No116Displayed water levellive
statusstring (HTML)Nonormal rangeHuman warning statusderived
03

Representative evidence

Sample records

Vere–Tbilisi gauge

Retrieved 2026-07-22T13:37:00+04:00

JSON
{"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