Re: [OSM-talk] Overpass API version 0.7.56
Thank you for the update! On 2020-04-14 07:09, Roland Olbricht wrote: > I intend to bundle them with the necessary changes to use > ways and relations directly as areas, > but that is not implemented yet. Although this sounds like a minor topic, it has quite some impact for a number of users. Rather frequently, people are puzzled that they cannot query for buildings without a housenumber node inside, or residential areas without buildings, etc. This is mainly due to a static set of rules on the Overpass server that define, which objects qualify for area queries. You've probably seen various Q site answers along the lines of: in theory it would work if your object had a name=* tag, but as it doesn't have one, sadly, you're out of luck. By eliminating those static rules in the equation and directly using (almost arbitrary) ways and relations, we expect that all those new use cases can be covered out of the box. A few examples as sneak preview: - https://overpass-turbo.eu/s/SP9 - unnamed landuse=residential ways/relations without buildings inside - https://overpass-turbo.eu/s/FaQ - misuse of barrier=line on leisure=pitch - https://overpass-turbo.eu/s/Fbv - buildings without housenumber on way and no respective nodes inside (mandatory disclaimers: actual implementation and syntax *will* change, data on the server may be outdated, server may be unavailable, prototype only!) -- ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Overpass API version 0.7.56
Thanks for the expansion of Type Shortcuts. It's going to save a lot of typing, especially with 'count'. DaveF On 14/04/2020 06:09, Roland Olbricht wrote: Dear all, I'm back with providing updates. After more than a year I'm proud to present a new release. This release provides some smaller new features. It is possible to use _angle()_ to filter ways by the angles of their inner vertices. This way, you can find e.g. non-rectangular buildings or unintended whiskers. https://dev.overpass-api.de/blog/total_0_7_56.html#angle A recurse can now be restricted by the relative position of the entry in the object. I.e. you can obtain only the first or only the last node of a way. https://dev.overpass-api.de/blog/total_0_7_56.html#memberpos The idea of _nwr_ has been extended both to variants _nw_, _wr_, and _nr_. And it is now possible with the count evaluator as well. https://dev.overpass-api.de/blog/total_0_7_56.html#type_shortcuts For the users of own instances, queries can now be passed by the command line parameter _--request=_ as well. Two larger features have been hold back because they break the database layout, and I do not want to do that too often: support for large objects (which are necessary to have Antarctica as an area) and a reoriganization of access to attribution data (changeset ids, user ids, user names). I intend to bundle them with the necessary changes to use ways and relations directly as areas, but that is not implemented yet. Best regards, Roland ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Overpass API version 0.7.56
Dear all, I'm back with providing updates. After more than a year I'm proud to present a new release. This release provides some smaller new features. It is possible to use _angle()_ to filter ways by the angles of their inner vertices. This way, you can find e.g. non-rectangular buildings or unintended whiskers. https://dev.overpass-api.de/blog/total_0_7_56.html#angle A recurse can now be restricted by the relative position of the entry in the object. I.e. you can obtain only the first or only the last node of a way. https://dev.overpass-api.de/blog/total_0_7_56.html#memberpos The idea of _nwr_ has been extended both to variants _nw_, _wr_, and _nr_. And it is now possible with the count evaluator as well. https://dev.overpass-api.de/blog/total_0_7_56.html#type_shortcuts For the users of own instances, queries can now be passed by the command line parameter _--request=_ as well. Two larger features have been hold back because they break the database layout, and I do not want to do that too often: support for large objects (which are necessary to have Antarctica as an area) and a reoriganization of access to attribution data (changeset ids, user ids, user names). I intend to bundle them with the necessary changes to use ways and relations directly as areas, but that is not implemented yet. Best regards, Roland ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
