Limitations.
-
Another thing I would like to bring up is a major glitch that has been occurring for a very long time now. Basically, if you move something, whether it’s a point, polygon, or line, it never returns to the same spot if you undo it, it is always slightly off. This might not be an issue to some people, but it is a major annoyance for people like me who are creating very precise maps. I am a mobile user, so it isn’t very hard to accidentally move something. I spoke with someone about this a while ago, and they said they would be working on the issue. However, I haven’t heard back in a while and the glitch is still present. Thank you.
0 -
We don't explicitly have any limits on node polygons or lines, that said performance can become an issue if you have a lot of lines or very detailed polygons, but the limit is very high, in the hundreds of thousands type of deal. Though our base layer is Google, we have our rendering engine that is significantly more performant than My Maps for high volumes. We have planned performance updates for client side that will allow millions, and then even further stuff that would potentially allow billions, but for most annotation use cases this won't be needed.
What you can do is on occasion go on your desktop and run "optimize line points" to a particular zoom this will reduce excessive points or details.
Thanks for letting us know about the undo issue, this is most likely related to the projection, we will take another look. It not going back to the exact same lat,lng would be pretty annoying especially if you have points snapped.1 -
Thanks for the information. Looking forward to it all.
0
Please sign in to leave a comment.
Comments
3 comments