I'm always frustrated when I look for OSM entrys along a line like a hiking path or a river. Yes, it’s possible to do the query directly on overpass turbo or load all features along a line in Josm, an d take this as input for QuickOsm. But, all this require much more steps than directly using QuickOSM which is a great tool.
Describe the solution you'd like
Passing a line or an WKT directly in QuickOSM Quicksearch will avoid much work and will this kind of query much more accessible.
Describe alternatives you've considered
The alternatives are described above, but nothing is like using QuickOSM and get the results directly in Qgis.
Additional context
Maybe it could be useful to limit the number of points, so that simplifying a track is necessary. This will avoid overusage.
I'm always frustrated when I look for OSM entrys along a line like a hiking path or a river. Yes, it’s possible to do the query directly on overpass turbo or load all features along a line in Josm, an d take this as input for QuickOsm. But, all this require much more steps than directly using QuickOSM which is a great tool.
Describe the solution you'd like
Passing a line or an WKT directly in QuickOSM Quicksearch will avoid much work and will this kind of query much more accessible.
Describe alternatives you've considered
The alternatives are described above, but nothing is like using QuickOSM and get the results directly in Qgis.
Additional context
Maybe it could be useful to limit the number of points, so that simplifying a track is necessary. This will avoid overusage.
Thank you very much.