2011/4/14 - New Release

[Chris Broadfoot (Google Employee)]

Hi all,

We recently pushed a new version of the Maps API. The major change in this release is Polylines and Polygons are now rendered in Canvas. This provides a significant speedup when adding many polys to a map. One known issue is that polygons are hidden when strokeOpacity is zero. As a workaround, set your strokeOpacity to something non-zero (say, 1e-32).

Polyline/Polygon stroke/fill colors now need to be specified in full hex notation (i.e. '#FF0000', rather than 'red' or '#F00'). This has long been the documented way of providing a color, but previously any CSS color worked.

We also recently made changes to our terms of service. Please read this blog post for a summary of the changes:

http://googlegeodevelopers.blogspot.com/2011/04/updates-to-google-maps-apigoogle-earth.html

The changelog for this release is copied below. See the full changelog here:

http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIv3Changelog

---

Resolved issues:

  * Fixed regression: Marker icon and shadow no longer transparent on IE6

  * Fixed: Markers no longer flicker on zoom

  * Fixed: Rendering of polygons across tile boundaries near the north/south poles

Noticeable changes:

  * Polylines and Polygons now rendered in Canvas where possible.

  * LatLngs for events on polylines and polygon borders now snap to the nearest point on the line.

---

Thanks,

Chris

--
http://twitter.com/broady

[Remi Grumeau]

After reading this blogpost, I would love to get a "diff" of Terms, to see all minor changes.

[Alessandro Giannini]

Hi !

with last version, using Chrome or FF , the sample 'http://code.google.com/intl/it-IT/apis/maps/articles/mvcfun/twittersearch.html' don't work !!!! I'm not able to view circle to define area. Any idea ? 

Thanks

@le><

[Chris Broadfoot]

The awesome wayback machine can help here :)

http://replay.waybackmachine.org/20101014235139/http://code.google.com/apis/maps/terms.html

--
http://twitter.com/broady

[Jason Sanford]

I've also got an application that uses the Distance Widget found in the "Fun with MVC Objects" example that is no longer working. I know this isn't a supported library, but I'm essentially just drawing a circle here. Website below:

http://open-data-day.geojason.info/

--
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-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Joseph Elfelt]

Thanks for the info Chris.

Can you (or someone) please clarify if the following FAQ statement is
still true under the revised TOS?

http://code.google.com/apis/maps/faq.html#tos_commercial
"If you charge people to place information on your map (e.g. to list
their homes for sale), but you display this information using the
Google Maps API on a free part of your site, you'll also meet the
Google Maps API Terms of Service."

[Stephan Bardubitzki]

The interesting thing in the change of the TOS is that the Static Maps API can be used outside a browser, but this still requires an Internet connection.

There are regions on our planet where there is no Internet service of any kind - and properly will never be - due to the vast distance between communities and the sparse population. One of this regions is Alaska - Northern Canada where I live. There are coming about 4 - 5 million travelers to this region each year, but no way to guide them on their handsets while on the roads or on water.  

For these regions it would make sense to allow offline usage of Google Maps to create meaningful services for travelers.

Stephan

   

[Todd Taylor]

With the use of Canvas now for polylines, does this open up the
possibility of dashed or dotted line rendering? Baked-in support in
the API or a utility library add-on would be great. Here's an open
feature request for this, which folks can star if interested:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=1800

One other feature request, which perhaps Canvas could be employed for,
is the ability to add text labels along polylines:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=3163

[Chris Broadfoot]

Thanks, this has been fixed. The problem was using shorthand color notation (i.e. #369 as opposed to #336699)

--
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-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

--
http://twitter.com/broady

[Lawrence]

Hi Chris,

Please note that the Polyline/Polygon rendering in Canvas has also
brought in an issue with the way the strokeOpacity or fillOpacity is
valued.

Canvas warnings get thrown in Firebug if zero (0.0) is used for the
strokeOpacity/fillOpacity. The documentation does still indicate that
the strokeOpacity and fillOpacity is a value of number type between
0.0 and 1.0. You'll see that the workaround has been to use a string
"0.0" or else use a value of at least 0.01. But again the
documentation does not reflect this.

So I'm unsure if this is a case of the documentation needing an update
or else this API update introducing an issue.

Please refer to this thread:
http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/bef7d861a9d25d9

Thanks!

On Apr 15, 6:28 pm, Chris Broadfoot <c...@google.com> wrote:
> Thanks, this has been fixed. The problem was using shorthand color notation
> (i.e. #369 as opposed to #336699)
>
> On Fri, Apr 15, 2011 at 5:15 PM, Alessandro Giannini <
>
>
>
>
>
>
>
>
>
> infinity.so...@gmail.com> wrote:
> > Hi !
>
> > with last version, using Chrome or FF , the sample '

> >http://code.google.com/intl/it-IT/apis/maps/articles/mvcfun/twitterse...

[Chris Broadfoot]

On Tue, Apr 26, 2011 at 10:41 AM, Lawrence <law...@gmail.com> wrote:

Canvas warnings get thrown in Firebug if zero (0.0) is used for the
strokeOpacity/fillOpacity. The documentation does still indicate that
the strokeOpacity and fillOpacity is a value of number type between
0.0 and 1.0. You'll see that the workaround has been to use a string
"0.0" or else use a value of at least 0.01. But again the
documentation does not reflect this.

It's a bug. It should be fixed in the next release: 
http://code.google.com/p/gmaps-api-issues/issues/detail?id=3241

http://code.google.com/p/gmaps-api-issues/issues/detail?id=3246

Chris

--
http://twitter.com/broady