Snap to OSM - hangs browser & app
I've been trying to trace out a basic route (albeit in a dense urban area), but the "snap to OSM" feature is hanging firefox, chrome & android app. It's as good as unusable.
https://drive.google.com/file/d/1l8lbmqrvI1FCCSOcRH2K9XR5Rz6dQr_d/view?usp=sharing
Anyone else experiencing this?
It's "better" in a remoter area of the map, but still sluggish and unpleasant to use.
Comments
2 comments
Hi Coops - Yes, I experience the same issue when I have Snap to OSM selected & am working in areas with a high density of roads/paths. A work-around I have found useful is to zoom in a little and have less available paths. Not ideal, but when you have to use it, this should work.
However, I never use Snap to OSM because of this issue and hope the default is changed to 'None' at some point.
I am running into the same problem trying to snap to OSM with polygon sizes approximately 15k to 20k acres. One idea I have is if they can make snap to an option during edit as well as initial creation, kind of same concept as changing a route on google maps by dragging the initial route. Draw a rough polygon, or in your case a line, and then zoom in and be able to snap to the actual points you want to adjust. makes it a little more forgiving than trying to trace your entire route moving the map as you go. When I've been doing the polygons there were many times I would click the wrong spot and it would close the polygon causing me to need to restart again tracing along OSM.
Please sign in to leave a comment.