← All sources
Near real-timeLive-testedOpen collaborative platform

Geospatial infrastructure / Collaborative map change metadata

OpenStreetMap changeset metadata for Tbilisi

The OpenStreetMap API exposes recent changesets intersecting a Tbilisi bounding box. The tested two-day query returned 17 changesets with creation/closure times, edit counts split into created/modified/deleted objects, change bounds, discussion count, mapper identity and free-form tags such as comment, editor, hashtags and imagery/source. This is a precise audit trail of mapping activity, not a direct list of the changed roads or amenities; individual object diffs require additional changeset-download or replication processing.

01

Provenance and access

How the data is reached

Unauthenticated OSM API XML query for changesets by bbox/time. Read-only API usage must follow OSM API/usage policies; large-scale history ingestion should use replication diffs or extracts rather than repeatedly polling the main API.

Reuse status

OpenStreetMap database under ODbL 1.0; attribution to OpenStreetMap contributors required. Usernames and changeset comments are public contributor metadata and require responsible handling.

Read license or terms ↗
02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

OSM root

Document metadata attached to the XML response.

2 fields
Field / pathTypeNull?ExampleMeaningFreshness
osm@version / generatorstringsNo0.6 / OpenStreetMap serverAPI format version and producerreference
osm@copyright / attribution / licensestrings/URLsNoOpenStreetMap and contributors / copyright URL / ODbL URLRights and attribution metadatareference

Changeset

One editing transaction intersecting the bbox.

9 fields
Field / pathTypeNull?ExampleMeaningFreshness
idintegerNo186157074Changeset identifierreference
created_at / closed_atISO datetimesNo2026-07-22T05:46:04Z / 05:46:05ZEditing transaction lifetimelive
openboolean stringNofalseWhether changeset can still receive editslive
comments_countintegerNo0Discussion-comment countlive
changes_countintegerNo1Total object changesderived
created_count / modified_count / deleted_countintegersNo0 / 1 / 0Changed objects by operationderived
min_lat / min_lon / max_lat / max_londecimal degreesYes41.7197367 / 44.7091904 / 41.7199274 / 44.7096334Bounding box of changed objectsreference
uid / userinteger / stringNo20577594 / birimkulovaPublic contributor ID and display namereference
tag[]@k / @vstring pairsYescomment=roads were added #wbgeoFree-form changeset metadataObserved keys include comment, created_by, hashtags, source, host and revert fieldsreference

Replication state

Global minute-diff checkpoint used for scalable incremental processing.

3 fields
Field / pathTypeNull?ExampleMeaningFreshness
sequenceNumberintegerNoglobal sequenceLatest replication-diff sequencelive
timestampescaped ISO datetimeNoYYYY-MM-DDTHH\:MM\:SSZState timestamplive
txnMaxQueriedintegerUnknowndatabase transaction IDMaximum database transaction queriedlive
03

Representative evidence

Sample records

Recent Tbilisi changeset

Retrieved 2026-07-22 14:00 Asia/Tbilisi

Text
<changeset id="186157074" created_at="2026-07-22T05:46:04Z" open="false" comments_count="0" changes_count="1" created_count="0" modified_count="1" deleted_count="0" closed_at="2026-07-22T05:46:05Z" min_lat="41.7197367" min_lon="44.7091904" max_lat="41.7199274" max_lon="44.7096334" uid="20577594" user="birimkulova"><tag k="comment" v="roads were added #wbgeo"/><tag k="created_by" v="JOSM/1.5 (19555 ru)"/><tag k="source" v="NAPR"/></changeset>
04

Boundaries

Reliability, caveats, and privacy

What held up

  • Live API returned 17 recent changesets
  • Edit-operation counts and bounds are explicit
  • Global minute replication provides a scalable incremental path

What can go wrong

  • Changeset bbox can intersect Tbilisi even if only some edits are inside
  • Metadata does not identify exact changed objects; fetch changeset diff separately
  • Comments and source tags are user-entered and not guaranteed accurate
  • Public contributor usernames are personal data
  • Use replication for scale and honor OSM API policy

Privacy boundary

  • Do not rank, profile or harass individual mappers from uid/user fields
  • Preserve legitimate attribution while minimizing unnecessary personal-data retention
05

Cross-source possibilities

Ideas using this source