Re: [Google Maps API v3] Specify marker as canvas instead of url?

Hi David, This is an interesting idea. Since we support browsers that lack Canvas, we usually try to avoid exposing Canvas in the public interfaces. And there *is* a workaround (toDataURL) though it's not ideal as you say. So I suggest using the workaround for now, and we'll look into supporting t

Re:[Google Maps API v3] Automatic shadows?

In browsers with Canvas one could generate a shadow image for a custom icon. However I don't think this is possible in IE7/8. So our usual approach in this case is to promote or publish a library or web service that adds this functionality on top of the API. Android brevity On Dec 21, 2011 6:17 AM

Re: [Google Maps API v3] Client side Geo-coding --- process

On Fri, Dec 2, 2011 at 8:53 AM, kShan wrote: > We are using client-side Geocoding for our product which is going live in > few weeks and I want to make sure that we won't run in to any query > restrictions when we go live. Please review the below items and share your > comments/thoughts. Thanks!

Re: [Google Maps API v3] Re: GMapsV3 - lots of MarkerImages slow down everything

; point will give me canvas optimised markers will it? > > > > > Thanks a lot. > > > > > Martin. > > > > > On Oct 14, 8:56 am, Kristóf Kótai wrote: > > > > > > This is unbelievable... > > > > I removed the scaling (which doesn't even h

Re: [Google Maps API v3] Re: GMapsV3 - lots of MarkerImages slow down everything

;full' MarkerImage constructor with all properties > set will cause non-optimised markers? > > Or could the scaled size be passed as null to acheive optimised canvas > markers? > > Martin. > > > On Oct 14, 12:37 am, Ben Appleton wrote: > > Your code trigg

Re: [Google Maps API v3] GMapsV3 - lots of MarkerImages slow down everything

Your code triggers the older DOM markers as it specifies a scale: icon: new google.maps.MarkerImage( ' http://viewranger.com/buddybeacon/v2/images/markers/marker_FF.png', new google.maps.Size(15,20), // original size new google.maps.Point(0,0), // origin new

Re: [Google Maps API v3] Reducing number of points in Directions Service Polyline?

Hi Evan, The directions service result contains a field "overview_path": http://code.google.com/apis/maps/documentation/javascript/reference.html#DirectionsResult This is pre-simplified to fit in a static map URL. Cheers Ben On Tue, Oct 11, 2011 at 6:22 AM, Evan Rolfe wrote: > Hi all, is there

Re: [Google Maps API v3] Re: Tile query without referer in http header with Webkit

, Sep 28, 2011 at 7:32 PM, surfish wrote: > Hello Ben, > > Do you have news about the double-fetch ? > > Thanks, > Olivier > > On 21 sep, 09:24, Ben Appleton wrote: > > The double-fetch is strange. I see that also in our > > google.maps.ImageMapTypeexample

Re: [Google Maps API v3] memory leaks when using .panTo

I am fixing a memory leak on pan. That fix is likely to go live next week. Thanks Ben Android brevity On Sep 24, 2011 4:57 AM, "LarryK" wrote: > Hi, > > I see a memory leak of 200K or more for each pan using .panTo method. > > Small test case: http://sandbox.kluger.com/map_demo.html > > Is this

Re: [Google Maps API v3] Re: Tile query without referer in http header with Webkit

The double-fetch is strange. I see that also in our google.maps.ImageMapTypeexample: http://code.google.com/apis/maps/documentation/javascript/examples/maptype-image.html This occurs only in Chrome, not in Firefox. We'll look into it. - Ben On Tue, Sep 20, 2011 at 5:56 AM, surfish wrote: > Chec

Re: [Google Maps API v3] Re: memory leak when moving marker

We've worked around the Chrome issue. The fix should go live in version 3.6, in the next week or two. Cheers Ben On Tue, Sep 13, 2011 at 6:53 PM, Ben Appleton wrote: > I pinned this down to a Chrome Windows memory leak: > http://code.google.com/p/chromium/issues/detail?id=96

Re: [Google Maps API v3] Re: Tile query without referer in http header with Webkit

al WMS servers require the Referer to validate the > session token. Google Maps won't able to integrate them if the > probleme is not solved. > > > On 16 sep, 01:53, Ben Appleton wrote: > > Sorry, we can't help you. It sounds like WebKit browsers may not send the > &g

Re: [Google Maps API v3] Tile query without referer in http header with Webkit

Sorry, we can't help you. It sounds like WebKit browsers may not send the referer header for cross-domain requests. Referer is often stripped for privacy by some proxy servers and browsers, so I think you'll have to fix your WMS server. - Ben On Fri, Sep 16, 2011 at 2:59 AM, surfish wrote: > Th

Re: [Google Maps API v3] Tile query without referer in http header with Webkit

Browsers don't allow JS to control the referer header. I suggest using an "access token": 1 - When you serve the HTML page, include a private hash of the date. 2 - When your JS forms a tile URL, append the access token. 3 - When your tile server receives a request, verify the access token is recent

Re: [Google Maps API v3] Re: memory leak when moving marker

I pinned this down to a Chrome Windows memory leak: http://code.google.com/p/chromium/issues/detail?id=96403 Try marker.set('optimized', false); in the meantime. Cheers Ben On Tue, Sep 13, 2011 at 2:24 PM, Ben Appleton wrote: > Aha, I spoke too soon! Although the Chrome

Re: [Google Maps API v3] Re: memory leak when moving marker

round the leak by writing marker.set('optimized', false); to revert to the old DOM-based markers. This fixes the memory leak on my setup. Cheers Ben On Tue, Sep 13, 2011 at 12:59 PM, Ben Appleton wrote: > Thanks for the link, that's very helpful. Unfortunately there is

Re: [Google Maps API v3] Re: memory leak when moving marker

Thanks for the link, that's very helpful. Unfortunately there is no leak in Chrome 14 / Windows 7. I'll try Chrome 13, but meanwhile could you specify the operating system in which you see the issue? Cheers Ben On Mon, Sep 12, 2011 at 10:09 PM, en4ce wrote: > same for me, the page crashes... yo

Re: [Google Maps API v3] What algorithm is used to find the shortest path between two points in the service Direction?

Actually it's a public algorithm: search for "highway hierarchies". Cheers Ben Android brevity On Sep 10, 2011 10:24 PM, "Chris Broadfoot" wrote: > Hi Quy, > > There's not really a name for it, but in essence it's a path finding > algorithm based on a heuristic that accounts for factors such as

Re: [Google Maps API v3] Maximum zoom level

If you observe an apparent max zoom of approximately 50, that sounds like a limitation of JavaScript's number class, which uses http://en.wikipedia.org/wiki/Double_precision_floating-point_format, which can only exactly represent numbers up to 2^52. However, JavaScript also casts numbers to signed

Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)

In version 3.4 on March 2nd we released Canvas markers: http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIv3Changelog Canvas supports about 10 times more markers than the non-optimized markers, addressing a long-standing complaint that our old markers were very slow. Unfortunately we

Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)

The problem manifests in IE7/8, in which markers are rendered as images. The IE debugger claims that http://tidesandcurrents.noaa.gov/tsunami/style.css has set a margin of 10px on all images, which causes the strange rendering that you observe. I suggest using a class to style your images. That av

Re: [Google Maps API v3] Re: 2011/8/17 - New Release (3.6)

You have 6 months in which to check your site against upcoming changes: http://code.google.com/apis/maps/documentation/javascript/basics.html#Versioning You have a simple workaround - set optimized: false http://code.google.com/apis/maps/documentation/javascript/reference.html#MarkerOptions Relat

Re: [Google Maps API v3] Limit map panning from moving beyond the poles

The stack overflow is because .fitBounds() changes the center, which calls your listener, which calls .fitBounds() again. You could work around this by checking the time since you last called .fitBounds(). I don't know of a more appropriate solution to prevent panning. Why do you want to prevent p

Re: [Google Maps API v3] Limit map panning from moving beyond the poles

That's right: the default map types use the Mercator projection, in which the poles are rendered infinitely far up/down the map. So as you pan up/down you approach the poles but cannot reach them. Have you tried limiting latitude to 85 instead? Android brevity On Aug 20, 2011 11:59 AM, "Jeremy"

Re: [Google Maps API v3] LatLngBounds extend bug?

This is because longitudes wrap around at -180 = 180 degrees. Focusing just on the longitudes: 1 - First you add the point -56 2 - Then you add the point -118. The bounds are now [-118, 56]. 3 - Lastly you add the point 126. The smallest bounds containing 126 and the previous bounds is [126, -56],

Re: [Google Maps API v3] Draw thousands of objects (markers, infowindow, polylines, circles, polygons)

Have you tried just making 1500 Maps API overlays? 5000 markers works for me in modern desktop browsers - what browsers do you have to support? - Ben On Tue, Jul 19, 2011 at 6:20 AM, AlbertoHN wrote: > Hi! The problem is that I need to draw thousands of objects (not cluster > them). the average

Re: [Google Maps API v3] Re: Dynamically adding a marker along a specific radius within a specific radial

You might also find the geometry library useful: http://code.google.com/apis/maps/documentation/javascript/geometry.html#SphericalGeometry In particular, take a look at google.maps.geometry.computeOffset: http://code.google.com/apis/maps/documentation/javascript/reference.html#spherical Cheers Be

Re: [Google Maps API v3] Speed comment - async

Could you provide a side-by-side? The speedup depends on the page structure and browser. Cheers Ben On Jul 8, 2011 8:06 AM, "Devin Rhode" wrote: > I just wanted to comment that I found a profound performance increase by > using asynchronous loading the the api vs. a plain script tag. > > In the d

Re: [Google Maps API v3] Google Maps Polygon "inner"

Hi Joel, I don't know what you refer to by "polygon.contains(point)". Can you clarify? If you refer to rendering a polygon's fill, and detecting when mouse/touch events hit the interior of a polygon, we use the following 2 rules: 1. Sequential vertices in a polyline or polygon path are connec

Re: [Google Maps API v3] How to pass parameters to callback function in the initialization script

Do you mean something like this? function callback() { initialize(ztype, zticketvar, zmonthname, zmfg, zmodel); } var script = document.createElement("script"); script.type = "text/javascript"; script.src = " http://maps.google.com/maps/api/js?sensor=false&callback=callback";; document.body.appe

Re: [Google Maps API v3] Re: Polygon in the form of a circle.

Hey John, Interesting: I agree your circles differ from ours. We currently use 500 vertices, computing LatLng for each using google.maps.spherical.computeOffset: http://code.google.com/apis/maps/documentation/javascript/reference.html#spherical then projecting to pixel coordinates using the Map's

Re: [Google Maps API v3] Re: Polygon in the form of a circle.

Hi John, google.maps.Circle correctly handles radius. Large circles do appear "egg" shaped on the map as you describe. Cheers Ben On Tue, Jul 5, 2011 at 12:49 PM, John Coryat wrote: > Be aware that a circle will not define a radius properly. Since the map > stretches the latitude in relation t

Re: [Google Maps API v3] Re: Markers array

You can do this by defining a custom .toString method, like: singleMarker.toString = function() { return this.id; }; Then you can write: myMarkers[singleMarker] = singleMarker; - Ben Android brevity On Jun 30, 2011 7:53 PM, "Richard Quadling" wrote: > On 29 June 2011 16:08, Arnaud wrote: >

Re: [Google Maps API v3] How to draw a polygon with encoded levels

Maps API v3 computes the levels in JavaScript, so you don't need to provide them yourself. - Ben On Tue, Jun 28, 2011 at 4:51 PM, Stefano Tucci wrote: > How to draw a polygon by encoded polyline, and encoded levels? > In documentation i don't see how to do it... > > > http://code.google.com/intl

Re: [Google Maps API v3] API V3 - is the fitBounds function depending of the order of markers ?

This is working as intended. The smallest bounds containing Port-au-Prince and Seoul crosses the dateline, which is the difference you see. Ben On Jun 16, 2011 6:57 AM, "wangba" wrote: > With Google maps V3. On this first test http://www.wangba.fr/test1.htmlthe > map is setting up with 3 markers

Re: [Google Maps API v3] how to create markers for nearby libraries and resturants

Yes, the Google Maps JS API v3 Places library: http://code.google.com/apis/maps/documentation/javascript/places.html On Mon, Jun 6, 2011 at 12:22 PM, Gary Zhang wrote: > Is there anything like a javascript without the daily limit and api key?\ > Thanks, > > > -- > *F

Re: [Google Maps API v3] How do I differentiate the paths of a polygon between an "outer" boundary and an "inner" boundary?

don't want to have to start from scratch? > > A library of useful apps that have been generated using the maps API > would be excellent. > > On 14 May 2011 03:30, Ben Appleton wrote: > > > > > > On Fri, May 13, 2011 at 9:09 PM, Richard Quadling > > wrote

Re: [Google Maps API v3] How do I differentiate the paths of a polygon between an "outer" boundary and an "inner" boundary?

On Fri, May 13, 2011 at 9:09 PM, Richard Quadling wrote: > On 12 May 2011 21:41, Ben Appleton wrote: > > > > On May 13, 2011 2:37 AM, "Richard Quadling" wrote: > >> > >> On 12 May 2011 14:12, Ben Appleton wrote: > >> > It sounds like

Re: [Google Maps API v3] How do I differentiate the paths of a polygon between an "outer" boundary and an "inner" boundary?

On May 13, 2011 2:37 AM, "Richard Quadling" wrote: > > On 12 May 2011 14:12, Ben Appleton wrote: > > It sounds like you have a polygon containment forest: a collection of rooted > > trees whose roots are outer polygons, children are polygonal holes, > > gr

Re: [Google Maps API v3] How do I differentiate the paths of a polygon between an "outer" boundary and an "inner" boundary?

It sounds like you have a polygon containment forest: a collection of rooted trees whose roots are outer polygons, children are polygonal holes, grand-children are polygonal islands inside holes, etc. You can certainly represent containment in JavaScript, but it's not necessary for rendering. There

Re: [Google Maps API v3] Custom Image Map Tiling issue

I don't have a debugger handy, but this sounds like a common error using %. If your implementation of .getTileUrl() uses % for tile coordinate wrapping, you need to ensure that negative values are wrapped correctly. For example: x = x % (1 << zoom) will not wrap negative x values correctly. In

Re: [Google Maps API v3] Re: distance between points v3

The geometry library is just JavaScript, no HTML5. If you find a bug please file it and we'll fix it. Thanks Ben On May 5, 2011 9:32 AM, "PeterB" wrote: > ormaybe I should upgrade my browser to something that handles > html5. That seems to have done the trick, but it might be nice to know > t

Re: [Google Maps API v3] Re: Map turning gray when loading and using TERRAIN

I don't see the issue at: http://www.bdtheque.com/carte-bds.php In IE, FF and Chrome I have tried: 1 - Load http://www.bdtheque.com/carte-bds.php 2 - Leave the page and come back at once I see no flashing or gray tiles. Can you provide additional details so we can reproduce the issue? Thanks Ben

Re: [Google Maps API v3] Street View images not loading in IE

http://code.google.com/apis/maps/documentation/javascript/examples/streetview-map.html works for me in IE7, IE8 and IE9. Can you provide some more detail to reproduce the issue? Thanks Ben On Thu, Apr 28, 2011 at 2:40 AM, Thomas Simpson wrote: > On the current (3.4) version of the API, using the

Re: [Google Maps API v3] Problem: Markers Drifting Position when Zooming

The error is where you write (links[i].coords[0].lng() + links[i].coords[1].lng()) / 2.0; This does not give the mid point of the line. To find the mid point of a line, use the geometry library's interpolate() function: http://code.google.com/apis/maps/documentation/javascript/reference.html#sph

Re: [Google Maps API v3] Issues with BlackBerry browser

Hi everyone, We've reproduced the issue on a Blackberry 5 simulator. The issue is that the Blackberry 5 browser requires the map div have an explicit z-index, else it does not display correctly. Until mid-January we were setting the z-index of the map div to 0, however developers complained that t

Re: [Google Maps API v3] Re: Thousands of polygons...

Hi Deane, Last week we released an optimization to polyline/polygon rendering. You should now be able to render thousands of polys totaling hundreds of thousands of vertices. I'm curious if this is enough for you to move off of Flash? Thanks Ben On Apr 21, 2011 8:15 AM, "DeaneVenske" wrote: > Hi

Re: [Google Maps API v3] Re: Issues with BlackBerry browser

http://code.google.com/apis/maps/documentation/javascript/examples/map-simple.html works fine for me on a BlackBerry Torch. Which BlackBerry browsers are you using? Note that BlackBerry 6 is supported, but BlackBerry 5 is not: http://code.google.com/apis/maps/faq.html#browsersupport - Ben On Sat

Re: [Google Maps API v3] Adding placemarks to map is slow (in version 2 and 3)

You might be interested to read the "Too Many Markers" article: http://code.google.com/apis/maps/articles/toomanymarkers.html That said, 325 markers is not too many. Can you show us the page where this is slow? Also, which browser are you using? In version 3.4 on Chrome and Firefox I can add 1

Re: [Google Maps API v3] Re: Issues loading Google Maps V3

Do you see the issue on an iPhone, or just a simulator? Changing the user agent is not enough, you have to use the real iOS browser to see if it works. Ben On Apr 10, 2011 10:58 AM, "Prasad" wrote: > Sorry my mistake. Please change the user agent to IPhone or access it from > Safari Browser. > >

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

am seeing here, the only thing which is guaranteed with > versioning, are the interfaces. > The underlying code is not guaranteed - notably undocumented features > which a number of us have relied on. > > On Mar 7, 12:12 am, Ben Appleton wrote: >> I'll reply in that thre

Re: [Google Maps API v3] Re: Passed arguments for 'click' event of Markers suddenly changed.

In v3.4 we've just released fast markers, which are painted into canvas tiles. So e.target will not be a marker DOM element. Instead I'd suggest getting the marker's position and placing your content accordingly. - Ben On Mon, Mar 7, 2011 at 10:14 AM, Steffen wrote: > A quick additional info, I

[Google Maps API v3] Re: Passed arguments for 'click' event of Markers suddenly changed.

Hi Steffen, I'll take a look. Meanwhile to avoid surprising changes, you can specify an API version like: http://maps.googleapis.com/maps/api/js?sensor=false&v=3.3 See the versioning documentation for more details: http://code.google.com/apis/maps/documentation/javascript/basics.html#Versioning

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

ing that as far as I see it is not working as documented > and I really don't know yet how to solve it. > > Thanks for your quick responses & Google Maps! :) > > > On Mar 6, 7:01 pm, Ben Appleton wrote: > > We preserve the documented interfaces across versions. The

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

We preserve the documented interfaces across versions. The auto-upgrade to 3.3 could only break your app if you are using undocumented interfaces. We use versioning to give sites a few months to report bugs and double-check their site against upcoming versions. On Mon, Mar 7, 2011 at 9:56 AM, Stef

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

No, you'll be auto-upgraded to 3.3. If you stick to the documented interfaces nothing should change, but to be sure you have 6+ months in which to check your site works with 3.3. - Ben On Mon, Mar 7, 2011 at 9:38 AM, Steffen wrote: > So when 3.5 is released, 3.2 will disappear, hence break all

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

We haven't changed V3.2. Can you include a link to a page that used to work but spontaneously broke? Thanks Ben On Mon, Mar 7, 2011 at 9:40 AM, geocode...@gmail.com wrote: > On Mar 6, 2:31 pm, Ben Appleton wrote: > > V3.2 is still available: > http://maps.google.com/maps/ap

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

No, we did not remove V3.2 (the frozen version). But in mid-February V3.2 became the frozen version, replacing V3.1, as documented here: http://code.google.com/apis/maps/documentation/javascript/basics.html#Versioning

Re: [Google Maps API v3] Re: Release version 3.2 (frozen) has been changed !

V3.2 is still available: http://maps.google.com/maps/api/js?v=3.2&sensor=false Why do you say it is not available? - Ben On Mon, Mar 7, 2011 at 4:08 AM, geocode...@gmail.com wrote: > On Mar 6, 7:46 am, sgiddings wrote: > > I have no problem with that Larry. > > My problem is that the version 3.

Re: [Google Maps API v3] Re: Function Closures

ing these. Cheers Ben On Thu, Mar 3, 2011 at 3:17 PM, bratliff wrote: > On Mar 2, 8:53 pm, Ben Appleton wrote: > > > The use of "function closures" for event listeners might work for a > > > few dozen markers but it does not scale well for many hundred or many >

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

higher opacity. On Thu, Mar 3, 2011 at 2:56 PM, bratliff wrote: > On Mar 3, 2:07 am, Ben Appleton wrote: > > > We will soon add a robust way to bring a marker to the front. > > You could leave the main CANVAS tiles containing many markers alone. > You could float a se

Re: [Google Maps API v3] Centering a marker in a dblclick handler doesn't work [V3.4 bug]

Hi Gary, Thanks for the simple example, I see it too. We'll take a look. If you'd like to track our progress, please file an issue in the tracker here: http://code.google.com/p/gmaps-api-issues/issues/entry?template=Maps%20API%20v3%20-%20Bug

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

Draggable markers are not rendered in Canvas. This is only noticeable when there is a mix of non-draggable and draggable markers, in which case the draggable markers pop out in front of the other markers. On Thu, Mar 3, 2011 at 12:30 PM, Esa wrote: > By the way. Draggable marker doesn't behave w

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

Esa Thanks for talking this through. On Thu, Mar 3, 2011 at 12:15 PM, Esa wrote: > Ben > > I am not happy with the answer. We don't know anything about your > zIndex formula. It used to be 'top' but you never documented it and > now you even changed the zIndex scheme. > Sorry, what do you mean

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

Some sites want to control the z-indices of their markers. If we were to add an API-computed z-index to their z-index, that could change the ordering of their markers. So if a site wants to control the z-indices of their markers, we should do exactly what they say. The issue here is that some site

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

That would set the z index to 0. We need a way to let you specify z-index of 0 versus letting the API default to z-index by height. We use null/undefined to mean "please default to z-index by height". On Thu, Mar 3, 2011 at 9:00 AM, Esa wrote: > > > > > > > setZIndex(null); > > > > > recovers t

Re: [Google Maps API v3] Function Closures

Hey Berry On Mar 3, 2011 6:47 AM, "bratliff" wrote: > > Berry, > > Your comment seems to be unrelated to the post. Please start a new > thread. > > Thanks > Ben > > Sorry > > The use of "function closures" for event listeners might work for a > few dozen markers but it does not scale well for man

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

That's correct, it restores the original z-index. On Wed, Mar 2, 2011 at 6:21 PM, Esa wrote: > So, it looks like > > setZIndex(null); > > recovers the original z-index? That is great news. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScri

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

Hi Raoul, The quick solution I proposed above works for me in Chrome, Firefox and IE: http://geoapis.appspot.com/agdnZW9hcGlzchMLEgtFeGFtcGxlQ29kZRjZswEM Are you sure you set the zIndex to 1E9? Thanks Ben On Wed, Mar 2, 2011 at 10:59 AM, Ben Appleton wrote: > Hi Raoul, > > marker.

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

seems different. > alert( site.marker.getZIndex() ); returns undefined > Can it be that getZIndex is no longer available? > > Kind regards > > Raoul > > On 2 Mrz., 00:30, Ben Appleton wrote: > > It looks like you're setting zIndex to 1 in order to bring a marker

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

No, marker zIndex is supported. When rendering markers in canvas we first sort by zIndex. On Wed, Mar 2, 2011 at 10:41 AM, bratliff wrote: > On Mar 1, 10:46 pm, Chad Killingsworth > wrote: > > This may be an unintended side affect of a new rollout. Seehttps:// > groups.google.com/d/topic/google

Re: [Google Maps API v3] Re: marker.setZIndex seems to no longer work

It looks like you're setting zIndex to 1 in order to bring a marker to the front on hover. A recent change increased the range of default marker z-indices, so 1 no longer puts the marker in front. A quick fix would be to change 1 to 1E9 (10). A more robust fix would be to assig

Re: [Google Maps API v3] Re: Markers changed to render via canvas?

Berry, Your comment seems to be unrelated to the post. Please start a new thread. Thanks Ben On Wed, Mar 2, 2011 at 9:46 AM, bratliff wrote: > On Mar 1, 8:32 pm, Ben Appleton wrote: > > Hi Adam, > > > > Fast markers just rolled out about 20 hours ago in the nightly vers

Re: [Google Maps API v3] Markers changed to render via canvas?

Hi Adam, Fast markers just rolled out about 20 hours ago in the nightly version. We usually hold off announcing releases for a day or two, to give sites a chance to report serious errors requiring a roll back. Ben On Mar 2, 2011 2:31 AM, "adamkempa" wrote: > We've seen a change to our v3 maps be

Re: [Google Maps API v3] iPad Performance issues

There are 3 Street View modes: 1. 'html4' - This uses simple tags with no perspective warping. It is fast in all browsers. 2. 'html5' - This uses Canvas 2D with perspective warping. Canvas 2D is software rendered so it has a low framerate. 3. 'webgl' - This uses WebGL. WebGL is har

Re: [Google Maps API v3] Re: Map doesn't load when touching Object.prototype in any browser

Yes - that is what causes the slowness we refer to above. On Feb 25, 2011 12:39 PM, "Martin™" wrote: > Instead of testing to see if an object property is a function you > could use the hasOwnProperty() method: > > http://www.google.co.uk/search?x=0&y=0&q=javascript+hasownproperty&ie=UTF-8&oe=UTF-8

Re: [Google Maps API v3] Displaying user input in an infowindow. Source of malware attack?

Yes, you must watch out for cross-site scripting (XSS) attacks. This is when a malicious user injects script into your info window (or other) content, for example to steal the viewer's cookie. The solution is to ensure you HTML-escape user input at the point of constructing your info window HTML.

Re: [Google Maps API v3] Re: Map doesn't load when touching Object.prototype in any browser

The native properties of Object.prototype are 'non-enumerable': http://stackoverflow.com/questions/262573/list-objects-built-in-properties With current JS engines it is not possible for you to set new, non-enumerable properties on Object.prototype, but future versions of JavaScript support this: h

Re: [Google Maps API v3] PegMan StreetView problem

This issue is fixed. The change should go live next week. Thanks Ben On Thu, Feb 24, 2011 at 9:16 AM, Ben Appleton wrote: > Haha, how silly. We'll fix that. > > Thanks > Ben > > On Wed, Feb 23, 2011 at 11:27 PM, Chewbacca wrote: > >> Hi, >> my proble

Re: [Google Maps API v3] PegMan StreetView problem

Haha, how silly. We'll fix that. Thanks Ben On Wed, Feb 23, 2011 at 11:27 PM, Chewbacca wrote: > Hi, > my problem is that after return from streetview panel, the "pegman" is > still over map when i use an ImageMapType. > When we use "standard" basemaps (ex: > google.maps.MapTypeId.ROADMAP), th

Re: [Google Maps API v3] Re: PHP generated Polygon

When we receive the JSON we recursively traverse it, promoting {lat:1, lng:2} to new google.maps.LatLng(1, 2) and likewise for any google.maps.LatLngBounds. Ben On Feb 20, 2011 8:06 PM, "sgiddings" wrote: > Hi Rossko, > > No, this is not what I am wanting to do. > > If you "capture" the s

Re: [Google Maps API v3] Removing an overlay (circle, poly, etc.) too quickly after creating it raises an error inside of the API

Thanks for the example pages, I confirm the error. If you want to be notified of the fix, please file an issue in the tracker: http://code.google.com/p/gmaps-api-issues/issues/entry?template=Maps%20API%20v3%20-%20Bug Cheers Ben On Fri, Feb 18, 2011 at 5:32 AM, John Laur wrote: > We have been ru

Re: [Google Maps API v3] Re: 2011/2/8 - New Release (Maps API 3.4)

Hi Abel, Would you mind loading this WebGL test page? http://learningwebgl.com/lessons/lesson01/index.html This page does not use the Maps API, so it will help to distinguish WebGL issues from Maps API issues. I have seen this hang on several Windows machines. Street View uses WebGL where availab

Re: [Google Maps API v3] Re: IE8 problem: polygons with 0

On Wed, Feb 9, 2011 at 2:50 AM, bratliff wrote: > On Feb 7, 10:24 pm, Ben Appleton wrote: > > Hi Berry, > > > > We have a user agent parser that extracts the rendering engine and > version > > from the browser useragent. I only apply the workaround > (width=

Re: [Google Maps API v3] Re: Resource interpreted as image but transferred with MIME type text/html.

he server side. > > Regards, > Tristan Seifert > 1 (408) 364-6384 <+14083646384> > Sent from my iPhone > > On Feb 7, 2011, at 19:52, Ben Appleton wrote: > > Don't panic, it's only a warning :-) > > I suggest you file a bug with chromium > (<h

Re: [Google Maps API v3] Re: Resource interpreted as image but transferred with MIME type text/html.

t; Help :( > > On 7 feb, 17:24, Ben Appleton wrote: > > This is a logging beacon. It records the time to load the javascript, > tiles > > and so on. The server responds with HTTP 204 which, being an empty > response, > > should not require a MIME type. Which browse

Re: [Google Maps API v3] Resource interpreted as image but transferred with MIME type text/html.

This is a logging beacon. It records the time to load the javascript, tiles and so on. The server responds with HTTP 204 which, being an empty response, should not require a MIME type. Which browser is complaining? On Feb 7, 2011 11:30 PM, "Ciul" wrote: > Hi pals. > > It is kinda rare problem. > >

Re: [Google Maps API v3] Re: IE8 problem: polygons with 0

box. I haven't yet converted to use Canvas by default, but as you.indicate this may be mucb faster than SVG. Cheers Ben On Feb 8, 2011 1:14 AM, "bratliff" wrote: > On Feb 7, 3:33 am, Ben Appleton wrote: >> We've fixed the bug. The change should go live next week. >&

Re: [Google Maps API v3] IE8 problem: polygons with 0

We've fixed the bug. The change should go live next week. Thanks to Berry for pointing out the off-by-one bug in IE8's VML implementation. Ben On Mon, Feb 7, 2011 at 9:38 AM, Ben Appleton wrote: > I see the bug too. We'll look into it. > > If you want to be notified

Re: [Google Maps API v3] IE8 problem: polygons with 0

I see the bug too. We'll look into it. If you want to be notified of a fix, please file an issue here: http://code.google.com/p/gmaps-api-issues/issues/list?can=2&q=apitype:Javascript3%20type:Defect&sort=-stars&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Internal%20Stars Thanks Be

Re: [Google Maps API v3] Re: Serious IE7/8 invalid character problem - compression issue?

What you describe sounds like the following proxy bug: 1. A resource (such as http://maps.gstatic.com/mapfiles/api-3/3/8/marker.js) is gzipped and served with HTTP response header "Content-Encoding: gzip". 2. The proxy caches the gzipped content and forwards the HTTP response header

Re: [Google Maps API v3] coordiniates order/direction for holes in polygons

To be safe, specify holes counter-clockwise and exterior loops clockwise or vice versa. On Feb 2, 2011 5:27 PM, "Vish Uma" wrote: > Hi all, > > I was wondering if anyone knew how the google maps v3 api decides that one > of the paths in the list of paths in a polygon is a hole. > > Does google ap

Re: [Google Maps API v3] Re: Problem with IE v8 and Marker.getZIndex

; the poi marker. > > Following your remarks, does this mean that I can create my own "z- > index" values, ie starting from 0, without the risk of having markers > badly positioned in the hierarchy ? > > > On Feb 1, 11:54 am, Ben Appleton wrote: > > It is inte

Re: [Google Maps API v3] Re: Problem with IE v8 and Marker.getZIndex

It is intended that you cannot access the final zIndex that has been assigned to the marker. The final zIndex assigned by the API is subject to change as it depends on the underlying implementation. You can access the zIndex that you set, which is undefined in this case. This behavior is consisten

Re: [Google Maps API v3] Cannot print direction map in IE

Hi Gordon, http://code.google.com/apis/maps/documentation/javascript/examples/directions-waypoints.html displays correctly for me in print preview in IE8 under Windows Vista. Can you give some more details to reproduce the error? Have you tried any other computers or printers? Thanks Ben On Thu,

Re: [Google Maps API v3] Re: Slow tile loading performance during zoom with ImageMapType overlay

On Thu, Jan 27, 2011 at 4:40 AM, bratliff wrote: > On Jan 26, 1:23 pm, John Laur wrote: > > > Your response does reinforce though how much work it would be to > reimplement an ImageMapType equivalent -- we will hang tight and see what > happens on the issue tracker. > > You might find > >htt

Re: [Google Maps API v3] Re: Slow tile loading performance during zoom with ImageMapType overlay

ile/releaseTile calls to ImageMapType to > better see whats going on there? > Sorry, there aren't any hooks (not even undocumented) for tracing ImageMapType's internals. You could step through the obfuscated code in a debugger (starting from a breakpoint in your .getTileUrl() implementati

Re: [Google Maps API v3] Re: Slow tile loading performance during zoom with ImageMapType overlay

t; > In firefox I do occasionally see Aborted requests in firebug, but > still most of the time I see hundreds of lines with spinners as the > downloads for each interim layer complete. > > John > > On Jan 25, 4:42 pm, Ben Appleton wrote: > > Hi John, > > > >

Re: [Google Maps API v3] Slow tile loading performance during zoom with ImageMapType overlay

Hi John, The API will initiate requests for tiles on screen, but cancels any in-flight requests after you zoom in again. It should not wait until pending requests are satisfied. Further, your browser will limit the number of concurrent requests to your tile server, so your tile server should not h

Re: [Google Maps API v3] Re: Is there a maximum path size for elevationService.getElevationAlongPath ?

ine thought it useful to place > it in a separate library to improve performance. > > - Jeff > > > > On Jan 17, 12:04 am, Ben Appleton wrote: >> Hi Jeff, >> >> It seems you've hit your browser's URL length limit. We send the >> (compressed) pat

  1   2   3   4   5   6   >