I'd like to look for recent nodes on exactly latitude -1. That's something a bit like this:
Which nearly works, except that it's not looking for recent nodes. The documentation leads me to believe that something like
ought to work, but unfortunately that gives:
Presumably, that is because the bounding box is counted as "large" (because it covers every latitude) rather than "small" (only one longitude) and therefore the "changed" part is being executed first, and obviously every node on the planet added this year results in an "out of memory" error. Is there any way to rephrase this query to only return nodes in that bounding box that were modified this year? (edit: spelling) asked 24 Nov '16, 18:12 SomeoneElse ♦ edited 24 Nov '16, 19:06 |
One Answer:
Try using the answered 24 Nov '16, 18:55 tyr_asd |
Thanks - that works!
Is there a logic to having to use "diff" before the actual query (in []) and "changed" at the level of the queried items (in () )?
@joost: Hmm, as far as I know, the operations of the two operations are actually quite different:
changed
is basically just a beefed-up version of thenewer
statement (but which is still a bit slower than that in many use cases). Whereas[diff:…]
(and[adiff:…]
) actually performs the following query twice and outputs only the difference between the two results (and also uses a different output format).OK thanks, just realized I've been using diff when I could have used the lighter changed or newer
Just for completeness, an example combining with a bounding box: