On Mar 10, 12:36 pm, Coen de Jong <co.dej...@gmail.com> wrote: > Sorry to say this but I don't get what you are saying.. Running out of > precision? Increase in 2? SVG will have an overflow? Clipping content?
Precision is not the issue. Two signed integers (one for X & one for Y) can represent any pixel position in zoom levels 0 - 23. SVG must allocate space for drawing. If your SVG box is 1000 pixels by 1000 pixels, it requires 1 million pixels which is 4 million bytes (RGBA). Clipping is also irrelevant. The SVG box is already clipped at its edges. A clipping path is used to define a non-rectangular mask within the drawing space. The actual display is limited to drawing within the clipping path. The real issue involves poly segments crossing your SVG box. One or both of the end points of a poly segment may exceed your SVG box. But, a piece of the poly segment may be within your SVG box. You will have to interpolate the end points of the poly segment to equivalent end points at the edge of your SVG box. Otherwise, you will be attempting to draw beyond the space allocated for drawing. A little extra space might be available at the margins of the SVG box but the amount might be different for different browsers. Have you considered using the API to draw your polys ? You could draw your arrows in an "OverlayView". You could use CANVAS rather than SVG. I believe every common browser with support for SVG also has support for CANVAS. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. 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.
