-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grouping items #395
Comments
|
Similar: Gibt es bereits ein Tool (/eine overpass-Abfrage?) o.ä., alle verwendeten keys/tags für einen bestimmten Bereich (Ort; bbox) sich in einer schlichten Liste nur mit der Zahl ihres Vorkommens anzeigen/'auswerfen' zu lassen? |
|
looks like this is implemented in 0.7.55: #467 (comment) (second example in "for" section)? |
Yes, exactly, @mojodna's example 3 can be written as follows now: [out:csv(count, "building:condition"; true)]
[bbox:23.6948,90.3907,23.7248,90.4235];
way[building];
for(t["building:condition"])
{
make stat "building:condition"=_.val,
count = count(ways);
out;
};Result: |
I've read this great blog post by @mojodna the other day: https://aws.amazon.com/de/blogs/big-data/querying-openstreetmap-with-amazon-athena/
Case study 3 highlights a GROUP BY use case, where the number of buildings is shown along with the building:condition. Currently, it's only possible to return all buildings via Overpass, without the grouping.
(runtime: 92ms)
Running the result through
sort | uniq -cwill return the desired result.So, counting is of course possible. However, identifying each different building condition and counting the objects for each of those conditions doesn't seem to be feasible as of today.
Minimal approach:
foreachto handle derived objects as wellThe text was updated successfully, but these errors were encountered: