mmd

Well, in the prototype, all regex are handled by pcre now (there's no way to switch between pcre and posix regex yet). It sort of works on my local machine,...

@pyrog : In the meantime, you could do a few tests with PCRE enabled on the test instance: http://overpass-turbo.eu/s/b1e Here's another example which will return ways with a single building=\*...

PCRE has shown some performance regressions with certain UTF-8 characters during performance testing, see http://wiki.openstreetmap.org/wiki/User:Mmd/Overpass_API/Performance_Project_2016. Example: ``` node["name"~"[قق][اا][لل]"] ``` I would recommend to leave POSIX as default, and enable PCRE...

Issue should be closed, follow up is in #332

I guess you're raising this issue in the wrong repo, Overpass API has no user interface. You need to raise it here instead: https://github.com/tyrasd/overpass-turbo/issues Also, there's not much point adding...

Quoting from: https://listes.openstreetmap.fr/wws/arc/overpass/2022-01/msg00001.html > From version 0.7.57 on, the database backend can handle very large > objects. > > Is there any way to proceed with the current installation? >...

barrier=fence is indeed not supported at this time - besides the `ref` value in your query is not correct, as is it missing a certain offset value for ways. Nevertheless,...

As you're effectively proposing a breaking change here, I believe this would only be possible by introducing another "out" modifier, which would have to be implemented for every other output...

By the way, this pretty much works as documented here: https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#out _center: This adds only the center of the above mentioned bounding box to ways and relations._

Found your post on Slack. I'd say you don't really need XML output for your use case anyway. CSV would do fine, processing issues can be recognized using an additional...