Google Charts 'upcoming' release of v48

181 views
Skip to first unread message

Daniel LaLiberte

unread,
Apr 27, 2020, 11:46:51 AM4/27/20
to Google Visualization API
You can now load Google Charts version '48'.  You should soon also be able to use this version by loading 'upcoming', but it is possible that might be unstable for a couple days since we are testing some new features of the loader.  

Please test version '48' and let us know if you experience any new problems.   At this time, 'current' is still '47' but you can continue to load version '47' by specifying that version.

Anticipated production release date: May 4
On this date, loading 'current' or 'upcoming' will load '48'. 

In addition to more internal refactoring, mostly migration to ES6 and TypeScript, there are a couple bug fixes and a major new feature.

* Fix a bug with boxStyle for annotations when there are multiple series.
* Fix AnnotationChart zoom buttons.
* Avoid use of array.entries() and Object.entries().  This is to avoid requiring polyfills for IE11 which may conflict.
* GeoChart now loads data using xhr, which means the setMapsSource method will work again, with two conditions: (1)The data portion of the content must have no comments (i.e. strict JSON format) and (2) the server must allow cross-origin requests for the data.  We will also finally be updating the maps data very soon, so look for news on that.
* VegaChart - this is a significant new feature which we are very excited to announce.  You can find documentation for the VegaChart here:   https://developers.google.com/chart/interactive/docs/gallery/vegachart

Sam S

unread,
Apr 27, 2020, 3:50:23 PM4/27/20
to Google Visualization API
When you say "updating the maps data" does this include updated ISO 3166-2 codes used by GeoChart which are currently very dated?

Thanks,

-Sam

Sam S

unread,
Apr 27, 2020, 4:10:26 PM4/27/20
to Google Visualization API
Using "upcoming" there is still clearly an issue with the ISO 3166-2 codes. https://jsfiddle.net/vg36r17k/ works with dated IOS 3166-2 codes and https://jsfiddle.net/jg7hvtuc/ does working with up-to-date ISO 3166-2 codes. It would be great to get a fix to these issues or at least the lookup table used to render GeoCharts.

Daniel LaLiberte

unread,
Apr 27, 2020, 4:23:52 PM4/27/20
to Google Visualization API
Hi Sam,

Yes, the updated GeoChart data will include updating the ISO 3166-2 codes as well.  We are not quite ready to release this updated data, however, but hopefully within a week.  To use the update, you will have to add a couple options to your charts.

By the way, the update of the loader, so that 'upcoming' is the same as '48', appears to be stable. 

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/5c001eff-8bb2-4413-9e3d-3c569a49cf4a%40googlegroups.com.

Sam S

unread,
Apr 27, 2020, 4:54:04 PM4/27/20
to Google Visualization API
This is great news! Looking forward to the update. Thanks.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

Daniel LaLiberte

unread,
May 11, 2020, 3:58:19 PM5/11/20
to Google Visualization API
The 'current' release is now version '48'.

Unfortunately, we had to disable the new VegaChart, until we can ensure it is more secure.  We have a plan for making it so, which will hopefully be ready for the next release.

We are also not quite ready to announce how to use the updated GeoChart data, but if you are interested, contact me and I can let you know.

Sam S

unread,
May 12, 2020, 11:06:06 AM5/12/20
to Google Visualization API
I'm very interested in testing out the new GeoChart data. Please let me know the next steps.

Thanks!

Amy Finkbiner

unread,
May 13, 2020, 10:31:22 PM5/13/20
to Google Visualization API
The issue I posted as "google.visualization.Query times out in Microsoft Edge" appears to be tied to v48.  When I explicitly load '47' instead of 'current', my pages work fine in MS Edge.  I checked the release notes and don't see anything that looks relevant.

Thanks,
Amy

On Monday, April 27, 2020 at 11:46:51 AM UTC-4, Daniel LaLiberte wrote:

Claudio

unread,
May 20, 2020, 9:43:02 AM5/20/20
to Google Visualization API
Reply all
Reply to author
Forward
0 new messages