I found out how to fix it! Just needed to use a higher number at element limit, as it limits the ram use to that amount answered 12 Jan '19, 13:38 leanderleza |
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
I found out how to fix it! Just needed to use a higher number at element limit, as it limits the ram use to that amount answered 12 Jan '19, 13:38 leanderleza |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Question tags:
question asked: 11 Jan '19, 13:59
question was seen: 1,840 times
last updated: 12 Jan '19, 13:38
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
Could you paste the actual text of your query in to the question, the screenshot is not legible.
It is legible in the RSS notification I got:
<osm-script timeout="180" element-limit="20000000"> <union> <area-query ref="3600034719"/> <recurse type="node-relation" into="rels"/> <recurse type="node-way"/> <recurse type="way-relation"/> </union> <union> <item/> <recurse type="way-node"/> </union> <print mode="body"/> </osm-script>
As far as I can tell this will return all relations (and ways and nodes) in Graz which appears to be too much information.