Overpass-turbo and uMap

[yohanboniface]

Hi :)

One of the most common requests I get from uMap support, is to ease the bridge between overpass-turbo and uMap.

uMap can eat OSM data (thanks to https://github.com/tyrasd/osmtogeojson, and so thanks to you :) ), and for this one way is to use an Overpass URL.

What I usually answer to users when they want to export data to uMap is to download as geojson from overpass-turbo, and then import the file in uMap (or copy/paste it).

But uMap also allows the data to be fetched dynamically when a map is loaded. This is called "remote data" in uMap. Roughly, one creates a new layer, and set a "remote data" URL. So now each time the map is loaded, the URL is requested, and the content shown on the map (one can style the data even if it's remotely fetched). The goal is to have fresh data. See for example: http://umap.openstreetmap.fr/en/map/pere-lachaise_6765#16/48.8613/2.3953

The Overpass data URL is (unless I've missed something :) ) a bit hidden. What I usually do to get it is: export => query => click on compact => right click on the link in the new page.

That said, I see two ways to create a better bridge between Overpass-turbo and uMap:

• Make it easier to get the Overpass data URL: for example, adding a section on "Export" called "URL" where the Overpass data URL can be copy-pasted
• this one is a bit more specific: on "Export" => "Data", adding a "Create a custom map" new link, that points to http://umap.openstreetmap.fr/map/new/?importUrl={overpass-url}&importFormat=osm (that URL would be obviously configurable: for example, Swiss instance of overpass-turbo would point to http://umap.osm.ch instead).

Those are just suggestions to start a discussion. I may have missed important points, and maybe not every points of mines make sense (I'm not sure for example how overpass-turbo deals with Overpass "convert" step) ;)

Thanks in advance for your thoughts on this!

Yohan

[tyrasd]

Sorry, I don't have time for a proper answer until next week, but I can already say that I'm definitely open to this kind of enhancement! :)

"Export" called "URL"

Actually, the Export option raw data directly from Overpass API should do the trick.

[yohanboniface]

Sorry, I don't have time for a proper answer until next week, but I can already say that I'm
definitely open to this kind of enhancement! :)

Cool! When you have a bit more time, let me know if I can help :)

Actually, the Export option raw data directly from Overpass API should do the trick.

Oh, nice, good to know, thank you :)

[RobJN]

I've wrote a blog post on how to use Overpass-turbo to feed data in to uMap. There's quite a few steps so anything that could be done to improve this would be of benefit (as an enhancement). Thanks for making such a great service available to us 👍
http://www.mappa-mercia.org/2014/09/creating-an-always-up-to-date-map.html

[sfkeller]

Somebody from my Geometa Lab (Keith) is soon starting to try to resolve this issue and make a pull request to overpass-turbo.

Yohan suggested:

Make it easier to get the Overpass data URL: for example, adding a section on
"Export" called "URL" where the Overpass data URL can be copy-pasted

That's also our proposal, namely changing this query export option (*=external links):

convert to Overpass-XML*
convert to (compact*) _OverpassQL*
to:

convert to Overpass-XML*
convert to OverpassQL*
__uuencoded* / with placeholders*

Any objections?

[FFMbyBicycle]

Hi,

I want to pick up the idea from @ANGkeith from #402 (comment): using "Export" for umap, would it be possible to add "https://overpass-api.de/api/interpreter?data=" in front of the copyable data/link? Currently people have to search this secret string every time (I only found it thanks to the blog post of @RobJN), a full copyable link would be much nicer and should be easy to add. Or am I missing something here which prevents us from changing this?