← All sources
LiveLive-testedOfficial public-page backend

Safety / Severe weather warnings

NEA administrative weather-warning polygons

Official machine-readable current-state warning map for 74 administrative polygons, including Tbilisi, with boundary, status color, place name, and nullable warning detail/title/icon fields.

01

Provenance and access

How the data is reached

Unauthenticated JSON GET used by the official warning map.

Reuse status

Unclear; no explicit data license or API terms found

02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

Administrative warning polygon

One GetMap array item.

9 fields
Field / pathTypeNull?ExampleMeaningFreshness
Pinsarray<object>No[{"lng":44.6,"lat":41.8},...]Polygon boundary verticesreference
Pins[*].lngnumberNo44.6Boundary longitudereference
Pins[*].latnumberNo41.8Boundary latitudereference
ColorstringNo#86c55eCurrent map-fill/status colorDo not assign a status label without official legend semanticsderived
IDinteger | string | nullYesnullActive warning/object IDlive
Infostring (possibly HTML) | nullYesnullWarning popup detaillive
VillagestringNoTbilisiAdministrative-area display namereference
Titlestring | nullYesnullOptional warning titlelive
IconIDinteger | string | nullYesnullOptional warning icon IDlive
03

Representative evidence

Sample records

Tbilisi warning state with geometry shortened

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

JSON
{"Pins":[{"lng":44.6,"lat":41.8},{"lng":44.7,"lat":41.8}],"Color":"#86c55e","ID":null,"Info":null,"Village":"Tbilisi","Title":null,"IconID":null}

Pins is deliberately shortened and is not a usable polygon fixture.

04

Boundaries

Reliability, caveats, and privacy

What held up

  • HTTP 200 JSON returned 74 areas
  • Official JavaScript was inspected to confirm the fields drive the public map
  • Stable geometry can be separated and cached from changing warning state

What can go wrong

  • Response has no measurement/publication timestamp
  • Status color semantics were not authoritatively labelled in this pass
  • All warning-specific fields were null at test time
  • Full polygons make the response large
  • Undocumented endpoint
05

Cross-source possibilities

Ideas using this source