out center;– this additionally prints the center coordinate for every OSM object
out bb;– this additionally prints the bounding box coordinates for every OSM object
out geom;– this additionally prints the full coordinates of every OSM object
The first two options are particularly usefull if one is only interested in the approximate location of some features, rather than their exact outline. For example, one finds that POIs are often mapped on building outlines. By requesting only the center coordinates (
out center;), one saves transfer bandwidth and gets an overall quicker query.
Here is an example how this looks like (note that out of the 7 displayed POIs, 6 are mapped on ways in OSM): (try it on overpass turbo)
The full geometry (
out geom;) option replaces the need to use object recursions to get the geometry for a certain OSM way or relation. This also saves bandwith and generally comes with faster query execution times. (In this example it saves almost 50% of the data.)
regular expressions for keys
I know that lots of people requested this feature, and now you can finally use regular expression on keys, for example to get all nodes with some kind of name-tag:
Here, the additional tilde in front of the key indicates that the regex-search should be extended to the key as well.
This is also accessible via overpass turbo’s query wizard. Try this for example:
building=* and ~"addr:.*"~".*"
Overpass QL is now the default
Queries generated by the wizard, a template and the query examples are now printed in Overpass QL. Overpass QL has a more concise syntax, is faster to write and more and more documentation and help is available for it. (Of course anyone can still continue to write, use and execute queries in the older XML syntax.)