Query by object version number

[mvexel]

It is already possible to query by user / uid, so querying by version should not be too hard..I hope?

I would want to query

• by exact version number
• by min / max version number

[mmd-osm]

Thanks for the suggestion! I have some follow-up question/comment on it.

Like the user/uid query, querying by exact version number would only return those objects, which currently have that version number in question.

Let's say an object currently has version 3 and you query for version 2. In that case the query would NOT return the data from version 2, but instead no result at all. Is this how you intend this to work? That would be quite easy to do.

-- or --

Should the exact version number return the object as it was back then (even if there's a newer version in the meantime)?

In general, the query would always refer to a particular point in time (either current time, or some given time via [date:xxxx-yy-zz...]) and always consider the version available at that time for querying.

Can you shed some light on the use cases you have in mind for this query, maybe?

[mmd-osm]

Maybe similar? openstreetmap/openstreetmap-website#1067

[tilmanb]

Let's say an object currently has version 3 and you query for version 2. In that case the query would NOT return the data from version 2, but instead no result at all. Is this how you intend this to work? That would be quite easy to do.

Yes, that would be helpful. Call this filter current_version, and usage should be

way[landuse](current_version:7)({{bbox}});

to get all landuses in the BBOX that are currently at version 7.

If this is easy to implement, implement it :-) and there will be an abundance of happyness :-)

[drolbr]

The first option is now implemented in 46b45ad.
This means that you can now filter a set of results for those elements that have a specific version or a specific changeset.

[maning]

Is this deployed in overpass turbo already?

[drolbr]

Yes, on the dev server: http://overpass-turbo.eu/s/prE

[mvexel]

Very cool. The link above does not currently work -- did you decommission that API endpoint?
Do you have visibility on a production release for this?

[mvexel]

Figured it out, it was a mixed content block from chrome. I have HTTPS everywhere installed so I was automatically redirected to the https site, but the link in the query was of course still http 🦐