Google Maps API v3: SVG graphics clip / disappear when zooming -


test link: http://kwestievan.nl/reizen

what i'm doing here: implemented own overlayview draw curved lines marker marker arrowheads @ end of each line svg. add div element map of width , height contain line , arrowhead. put inline svg code in div let browser draw line , arrow.

if viewed in safari or chrome annoying , unexpected behavior occurs. in safari whole svg graphic disappears beyond zoom level, , in chrome arrowheads @ end of line disappear , re-appear @ random zoom levels seems. in firefox , opera behavior not happening , arrowheads visible @ zoom level.

don't mind red boxes and/or displacement of arrows. that's work in progress.

what going on here? svg not compatible google maps or doing wrong?

the marker infowindow shadow? marker shadow set same values infowindow. duplicate variable maybe? change name of marker shadow 'path'. may have inadvertently used same identifier marker path name infowindow shadow path.

i agree star. started creating complex svg paths polyline icons , half disappear when placed in positions , zoom levels (i.e., when straddle 2 map tiles). it's blamed on geodesic correction.

in firefox svg outer line randomly float around screen in larger scale. closure issue. fixable though.

i dont see why polyline , icons can't sit above map layer , therefore avoid idiosyncrasies.

basically have wasted lot of time , disappointed results of placing svgs on polyline. did want sell bus scheduling , mapping script transit companies. graphically not standard feel comfortable with. i.e, buses half disappearing , reappearing on next tile.

i going use markers bus icons appear sit on layer above map , therefore don't have geodesic attachments.

by way. can create arcs using polyline , polygon.


Comments

Popular posts from this blog

delphi - How to convert bitmaps to video? -

jasper reports - Fixed header in Excel using JasperReports -

python - ('The SQL contains 0 parameter markers, but 50 parameters were supplied', 'HY000') or TypeError: 'tuple' object is not callable -