On Feb 16, 10:09 am, Chadwick Meyer <chadw...@gutensite.com> wrote: > I recently discovered that the custom markers on my maps were being > hidden behind the Google Maps tiles. You can clearly see the edge of > the grid where the markers are being cut > off.https://skitch.com/gutensite/8n8n5/find-parking-park-circa-mobile-app... > (original page, that is now fixed:http://www.parkcirca.com/Parking) > > I am using Google's latest Google Maps API Version: 3.8
Is it this issue in the issue tracker? http://code.google.com/p/gmaps-api-issues/issues/detail?id=3921 If so you might want to "star" it. -- Larry > > To my surprise not many have complained about this recently (I looked > extensively). I discovered that this is caused by the new Canvas tiles > that are used to optimize the page. If you inspect elements, you can > see that the markers are actually tile layers. If I turn off > 'optimized' (see code below) the markers display correctly! > > var point = new google.maps.Marker({ > 'position': position, > 'map': this.options.map.construct, > 'icon': marker_data.custom_icon, > 'title': marker_data.title, > 'optimized': false > > }); > > What is interesting is that if you use the default markers, the tiles > do NOT hide the default markers (code > below).https://skitch.com/gutensite/8n8g3/find-parking-park-circa-mobile-app... > > var point = new google.maps.Marker({ > 'position': position, > 'map': this.options.map.construct, > 'title': marker_data.title > > }); > > But the reason for this, is because somehow Google seems to be adding > creating the canvases differently for their default markers. When a > marker overlaps a tile they make sure that part of it shows up on each > adjacent canvas > tile.https://skitch.com/gutensite/8n88g/find-parking-park-circa-mobile-app... > > I inspected the elements and deleted certain tiles, and you can see > that the other half of the default marker still is shows up on the > adjacent > tile.https://skitch.com/gutensite/8n8e8/find-parking-park-circa-mobile-app... > > So I guess the question is, am I doing something wrong that is causing > Google Maps API to treat my custom markers inferior? Or is this a bug > in the API that no one has reported yet? -- 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.
