matt on 21 Aug, 2018 01:47 AM
Beyond the complexity of figuring out what order those markers should be assembled in for non-trivial polygons, I'm struggling to figure out the why - both why they want to approach the problem this way, and what the justification for auto-connecting the markers is vs simply tracing the polygon out by hand.
I think just allowing new lines/polygons to snap-to markers would satisfy our use case. This would eliminate the need for any new UI or automatically assembling routes for complex polygons.
Put another way, the problem is that it is currently impossible to draw a polygon *exactly* between markers. You have to zoom in and sort of click *close to* the marker. They want the *exactness* of a polygon whose vertices are *exactly* equal to marker positions.
One limitation of your team creating "areas/sectors" in this fashion is that if they wish to use the where-to function to get to a specific spot within or outside of this "area" then they will lose the polygon that is created. Our team used to use this function sometimes to create route lines to stay within an assigned area but utilizing polygons and area assignments via SARTopo has been much more efficient for us since adapting it. Just something to consider.
matt on 22 Aug, 2018 03:27 AM
You can now click on markers while drawing a line, but it drops where you click without snapping to the marker itself, so it's not 100% exact. The drawing code uses DOM clicks, while marker clicks come through the Google Maps API, so snapping to markers would be difficult - it would have to be integrated with the other line-drawing snap-to code, but doing so wouldn't be trivial.
Honestly this feels like a use case very specific to old-school GPSs (getting navigable waypoints for the corners) and I still don't really understand why having the duplicate information is useful with a modern GPS that can show the segment on top of a topo map. However I could see possibly doing the reverse, ie adding a marker at each vertex on an existing line / polygon. There's already a Modify -> Create Points option, and it would probably be feasible to create a marker for every existing point rather than distance intervals.