|
I'm trying to get all the paved roads in South America through an overpass-turbo query. To lighten the load, I split them into primary, trunk, etc. Here's an example: http://overpass-turbo.eu/s/7JY This worked perfectly fine for trunk roads, but my browser crashes on the 80 mb generated for the primary paved roads. I think it's just the rendering that causes the problem. I know there's a way to skip trying to render the generated data, but I can't find the info anywhere. I just need a gpx file of the data. |
|
Just click on "Export" -> "raw data directly from Overpass API" in overpass turbo to download an .osm file (don't press run!). Then convert that .osm file into .gpx with whatever tool you have at hand. I don't think JOSM or the query form will be needed in your case, unless you want to use JOSM for osm->gpx conversion. 1
Thanks, just what I needed. I did try some of the export functions, but most only work -after- you've run the query. Funny bug though: the link refers to overpass-api.de , not www.overpass-api.de . And apparantly overpass-api.de only works with the www added. Now who to file this bug to? :)
(22 Feb '15, 00:49)
joost schouppe
Overpass Turbo bug reports should go here: https://github.com/tyrasd/overpass-turbo Overpass API bug reports should go here: https://github.com/drolbr/Overpass-API In this case, as it's the connection between the two, you could choose where to file it. Roland can enable overpass-api.de to work, and tyr_asd can add the www I presume.
(22 Feb '15, 09:40)
Sanderd17
I cannot reproduce this here. If overpass turbo works ok with the default setting "//overpass-api.de/api/", I don't see a reason, why the download shouldn't work. Maybe some funny antivirus/firewall/etc. thing?
(22 Feb '15, 09:54)
mmd
Just a note: don't forget to set [out:xml] instead of the standard json.
(03 Mar '16, 08:20)
joost schouppe
|
|
You can use "Download from Overpass API" function in JOSM. This requires the mirrored_download plugin (nasty thing in JOSM is that plugins integrate so seamlesly that you would forget you're using them). Also, couldn't get it to work (though I quit trying when I saw mnd's answer)
(22 Feb '15, 00:43)
joost schouppe
|
|
The easiest is to get the file directly from the Overpass API query form: http://www.overpass-api.de/query_form.html Just copy-paste your query in it, and press the "query" button. This way, you get the raw file, which can be even bigger than the size JOSM can handle. It also avoids having to download the meta data, when you don't need it. Or it allows you to use non-osm formats. Have you tried this out before? Copy-pasting the query won't work, as the original query has Overpass Turbo specific parts in it (like {{bbox}}). If you send that 'syntactic sugar' directly Overpass API, you'll get lots of error messages! Overpass API doesn't know about {{bbox}} and only overpass turbo will do a proper translation before sending it to Overpass API. Besides, there's still the issue of large data volume in the browser, which this answer does not address.
(21 Feb '15, 19:19)
mmd
Right, missed the {{bbox}} in the query. I normally use boundary definitions to avoid that. As for the large data volume in the browser, that's not true. The browser normally asks to store the file, so it gets written directly to the disk without sitting in browser ram. I use this method almost always when I need more data out Overpass API. Of course, your solution is nicer, as it's a link directly from Overpass turbo to Overpass API, so you don't have to remember different URLs and it requires less clicks.
(22 Feb '15, 09:37)
Sanderd17
Hmmm. I tried this now in Firefox and Chrome and both would show the query form result right in the browser window (Test query: http://overpass-turbo.eu/s/7NN --> copied over to query form). That's where my browser gets very sluggish with a lot of data. For some reason I don't get a save as file dialog. Whereas in overpass turbo, I could right click on "raw data directly from Overpass API" and just save the result in a file, without bothering too much with rendering all that JSON/XML data in the browser.
(22 Feb '15, 09:50)
mmd
Hmm, it seems to depend on the format too. Some formats are opened as text in the browser, others are treated as file. So far, XML is treated as a file in FF, while JSON is treated as in-browser text.
(22 Feb '15, 10:01)
Sanderd17
|
Now that's what I call Openstreetmap in action! Here's what it's useful for: http://www.openstreetmap.org/user/joost%20schouppe/diary/38103 :)