lat/lon/zoom Parameters

[al--]

Please allow standard lat/lon/zoom parameters to allow such kind of queries:

http://overpass-turbo.eu/?key=ref%3Amonument&template=key&lat=47.6274&lon=15.8095&zoom=14

And BTW, it would be nice if it auto-runs a query if full information is given (either by the "share" permalink or by above set of taginfo plus location (either bbox or lat/lon/zoom) parameters.

And BTW², it would be nice if the permalink feature would use shorter parameters, see http://map.project-osrm.org/ as a good example.

And one more thing: you have a nice feature to manually select a bbox. But how can I get this bbox out, as numbers? To use them as a parameter, for instance.

/al

[tyrasd]

lat/lon/zoom: Right! In fact, I was already planning to implement this shortly.

autorun: I think this would be a good idea, too.

shortlinks: Yes, I had this in mind, too. Will implement sooner or later.

bbox-selector: There is a solution/workaround for your use case: After selecting the bbox you can use Export->Query->as text to read out the replaced {{bbox}} values. I may upgrade the Export->map->current map view tool to show also the values for a manually selected bbox...

[al--]

bbox-selector: you could just make an "update" button (this could even replace the bbox-button) that updates the bbox coords either in the code window (just say a bbox definition statement) or in the url. Currently, the manual bbox selection is "kind of hidden" functionality, so you could maybe even auto-update a bbox definition statement in the code.

auto-bbox: I don't know if this could be implemented but queries like mine above give only a small result set with only a small bbox extent, so maybe this bbox could be auto-detected? -- Of course, this wouldn't make sense for e.g. a amenity query...

BTW, great feature overall, thank you!

/al

[tyrasd]

lat/lon/zoom parameters and printing manually selected bbox parameters in Export->map->"current map view" are now implemented in the master branch (and will be online in a few days, I suppose).

I'm not sure what you mean with the "update" button... Wouldn't that be what Export->Query->"as text" (plus one copy+paste step) already does? I can't think of any good use-cases for that functionality to deserve its own button :P

Concerning the "auto-bbox detection": No, unfortunately, this can't be implemented easily. But if you (the user) already knows (from taginfo for example), that a particular tag is used quite rarely, one can simply omit the statements at all and then use the "zoom to data" tool.

shortlinks and auto-running queries (going to have a second thought about that one...) will be worked on later.