This is great news! Looking forward to the update. Thanks. On Monday, April 27, 2020 at 4:23:52 PM UTC-4, Daniel LaLiberte wrote: > > 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. > > On Mon, Apr 27, 2020 at 4:10 PM Sam S <[email protected] <javascript:>> > wrote: > >> 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. >> >> On Monday, April 27, 2020 at 3:50:23 PM UTC-4, Sam S wrote: >>> >>> 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 >>> >>> On Monday, April 27, 2020 at 11:46:51 AM UTC-4, Daniel LaLiberte wrote: >>>> >>>> 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 >>>> >>>> -- >>>> Daniel LaLiberte >>>> <https://plus.google.com/100631381223468223275?prsrc=2> >>>> [email protected] Cambridge MA >>>> >>>> -- >> 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 [email protected] >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-visualization-api/5c001eff-8bb2-4413-9e3d-3c569a49cf4a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-visualization-api/5c001eff-8bb2-4413-9e3d-3c569a49cf4a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> > [email protected] <javascript:> Cambridge MA > >
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/b65c4260-7120-48b3-84ed-c371e624939c%40googlegroups.com.
