Tbilisi Municipal Services Map operational and reference layers

Official map visibly catalogs temporary traffic schemes, street rehabilitation, transport, parking, applications, cadastral, boundary, greenery, and hydrography layers. Candidate backend paths named in the public client all returned 404 to direct tests, so record schemas remain unresolved.

Provenance and access

How the data is reached

Public interactive map. JavaScript API base and method names found, but direct GET and POST tests returned 404.

Reuse status

Unclear

Official map

https://ms.gov.ge/msmap/ ↗

Method: GET
Format: HTML/interactive map
Authentication: None observed

Candidate API base

https://api.municipal.gov.ge ↗

Method: GET/POST
Format: Unknown
Authentication: Unknown

Candidate paths /core-api/v1/search/tbilisi-roads-maintenance, /core-api/v1/private-parking-lots/, /core-api/v1/zonal-parking/search-by-location returned 404

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

Known catalog/UI state only

Not a record schema; fields exposed by public map navigation/catalog.

4 fields

Field / path	Type	Null?	Example	Meaning	Freshness
`layer/category label`	string (UI)	No	temporary traffic schemes	Visible public map layer name	reference
`lrId`	query parameter	Yes	varies	Selected layer/resource state	reference
`objId`	query parameter	Yes	varies	Selected object state	reference
`orgId`	query parameter	Yes	varies	Selected organization state	reference

Representative evidence

Sample records

Boundaries

Reliability, caveats, and privacy

What held up

Official map and layer catalog were page-verified
Candidate API base and paths were extracted from shipped JavaScript

What can go wrong

No record endpoint validated
Direct candidate path tests returned 404
Mixed live/reference layer semantics
Do not invent fields from client method names

Source trail

Primary pages and documentation

PrimaryOfficial Municipal Services Map ↗
https://ms.gov.ge/msmap/