Yeah, I was kind of hoping to not have to do a setrows for various zoom levels, but like you said easy enough to do :-)
Sent from my iPhone On Oct 3, 2012, at 1:58 AM, asgallant <[email protected]> wrote: You can code things on your end to filter out non-states in a zoomed in view. Entering states/provinces using the notation: "<country code>-<state/province code>" (ie, "US-GA" for Georgia, USA) makes it easy to programmatically distinguish between states/provinces and countries. On Tuesday, October 2, 2012 8:57:38 PM UTC-4, Sean Power wrote: > > Sweet! One other quick question. The regions can either be ISO codes or > text. I am running into a problem with Georgia the country being confused > with Georgia the state at times (depends on resolution the user selects). > So if I have a map with countries that includes Georgia the country, and > the user zooms to US, Province resolution, they get Georgia the state. > Oops. > > I can't use 2-digit ISO codes either, as then Indonesia gets dropped into > Idaho, etc... Any thought to including the entire 3 segment notation as an > option, its what we use internally. So 142.145.GE is georgia the > country, 019.021.US.GA is georgia the state...impossible to get em mixed > up. > > The only other way I can figure doing this is to NOT allow user to zoom to > US province level when there is no data using UI logic, but what if we have > state level data for US and want to show it? Anyways, thanks for taking > care of below and considering above. > > Sean > > On Tuesday, October 2, 2012 4:02:31 PM UTC-4, Sergey wrote: >> >> Hi, thank you for finding this bug! I'm happy to announce that if you >> switch to 1.1, this issue is now fixed! We hope to have it fixed in 1.0 in >> a day or two. >> >> On Saturday, September 29, 2012 10:10:05 AM UTC-4, Sean Power wrote: >>> >>> backgroundColor.fill: 'none' - *works still.* >>> >>> And I can not get the >>> datalessRegionColor: null - to work (I want a transparent >>> datalessRegionColor). >>> >>> Agree 100% that whatever means transparent ('none', 'transparent') >>> should be consistently applied. >>> >>> Agree 1000% that controlling the region borders (country, province, >>> continent, subcontinent borders) would be a great stylistic improvement. >>> >>> See ya iFrame (cept for the automagic IE8 and earlier detection you guys >>> are doing which is very cool, and retro). >>> >>> S >>> >>> On Tuesday, September 25, 2012 6:37:11 AM UTC-4, visigoth wrote: >>>> >>>> If it works for the background.fill, it would make sense to work for >>>>> the datalessregioncolor no? >>>>> >>>> IMO, you're right. It makes perfect sense to be consistent. I'll refer >>>> this to our GeoChart guy to look into when he's back. >>>> >>>> Glad you found a workaround for now. >>>> >>>> On Tue, Sep 25, 2012 at 12:16 PM, Carlos Moreira >>>> <[email protected]>wrote: >>>> >>>>> Thanks for the quick answer visigoth! >>>>> >>>>> Further testing, and I have some conclusions: >>>>> >>>>> datalessRegionColor: null - *works*; >>>>> datalessRegionColor: 'transparent' - doesn't work, it did in the past >>>>> - error message: 'none' is not a valid hex color >>>>> datalessRegionColor: 'none' - doesn't work, it did in the past, and - >>>>> error message: 'none' is not a valid hex color >>>>> backgroundColor: {fill:'transparent'} - *works* >>>>> >>>>> So, i found out there's a workaround, but I have to change some maps >>>>> that I did in the past and a tool I developed to generate them. >>>>> If it works for the background.fill, it would make sense to work for >>>>> the datalessregioncolor no? >>>>> >>>> >>>>> I'll wait until the end of the week to get some feedback for the >>>>> borders question, no problem, thanks! >>>>> >>>>> Terça-feira, 25 de Setembro de 2012 11:34:29 UTC+2, Carlos Moreira >>>>> escreveu: >>>>> >>>>>> Hello everyone! >>>>>> >>>>>> Nice to see the new release is out and working! >>>>>> To bad HTML tooltips are not available for geochart... Still waiting >>>>>> on that one :) >>>>>> >>>>>> Bye bye Iframes, that's good! >>>>>> The tooltip.trigger will also be usefull. >>>>>> >>>>>> *I had one problem with this update tough*: I was using the color >>>>>> setting: 'transparent' for maps, for the background and inactive regions, >>>>>> and it gave a really cool look in some designs. >>>>>> Apparently now 'transparent' is not accepted, it throws and error. >>>>>> Why is that? It was a nice feature!! Should I report this as an issue in >>>>>> the visualization-api-issues project? >>>>>> >>>>>> Also, what does it mean 'Improved border colors'? The borders of the >>>>>> map container, or the country borders? Would be awesome for us to be able >>>>>> to control country borders colors also :) >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Google Visualization API" group. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msg/google-visualization-api/-/1OXXAZJnjNIJ >>>>> . >>>>> >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/google-visualization-api?hl=en. >>>>> >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/rD62AgIRd-oJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
