> > Sorry. Your SVG overlay must have some coordinates. For example you say, I > want to draw a path from 10,10 to 15,20. Now imagine that 10,10 is Sydney > and 20,20 is New York. If you are in zoom level 0, you will have 10,10 and > 20,20. In level 1, it would be 20,20 for Sydney and 40,40 for New York. In > level N, 2^N*(10,10) and 2^N*(20,20). So, how big is you SVG size? is is > the size of the "screen" or the size of the "map"? If it is the size of the > map, you have a SVG of 2^24 (max zoom) "pixels" by the size of a tile > (2^8). Can you imagine that? You have an SVG of 2^32 pixels. Think how > things go inside the browser, having to manage all those "big" numbers is > very easy to run into overflow. >
A very easy way to detect this is to draw a thick line and observe. When you are making a zoom, the line will become a bit thinner (error of rendering in such huge coordinates). So, the way to fix this is by clipping. Your SVG need to be always as big as the screen, and you need to draw in it what corresponds to the size of the screen. Technically this should not happen if the SVG would be well designed (you can play with the attribute viewBox, but it wont help much), but... Hope it is more clear now :) -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/rm22pQWQQowJ. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
