mmd

Related to #6030, probably even a dup.

Overpass API doesn't support queries on changeset metadata at this time, but you could use the [main API](http://wiki.openstreetmap.org/wiki/API_v0.6#Query:_GET_.2Fapi.2F0.6.2Fchangesets) instead. A bit of post processing (=filtering) on the result will be...

@kolesar-andras : can you shed some more light on your use case? Applying today's logic to query _by user name_, filtering by changeset (`changeset:1234567`) would only return objects which have...

@pyrog : there are also some other approaches available to query changeset metadata. One example is [OpenStreetMap Changeset Sync for PostgreSQL](https://github.com/zhm/osmchanges-postgres).

@rmikke : it's actually in [changeset 26767766](http://www.openstreetmap.org/changeset/26767766). No, you can't find it via Overpass API. I use a dedicated database based on https://github.com/zhm/osmchanges-postgres for it.

It's this empty changeset: http://www.openstreetmap.org/changeset/26767650

Also check the discussion on https://github.com/openstreetmap/openstreetmap-website/issues/1500

By the way, OSMCha supports changeset metadata queries.

Sorry, what you wrote is totally off topic for the Overpass API repository. Also, downstream consumers include tools like osm2pgsql and many others, so your analysis is unfortunately irrelevant for...

This is purely by convention. There's a set of rules, which governs how ways and relations are treated. If they match a rule, a corresponding "area" is calculated in Overpass...