Ananya,
Can you read my embedded comments, which are:
You can change the color of all the data points by using the 'colors'
option, with one color. e.g. colors: ['red']
The best way to make overlapping points distinguishable might be to use the
dataOpacity option. This seemed to work well:
I believe you are asking if you can make each point in the scatter chart
have a different size. If so, then no, the scatter chart assumes they are
all the same size. However, the bubble chart is almost the same kind of
chart, but it allows you to set the color and size of each point from data.
We have no feature for altering the label text of the annotations in the
chart. If you have a specific suggestion for what you would like to see,
we will consider it for a future enhancement. It might be best to post a
suggestion to the issues list so others could contribute as well:
Hi lagvendra
The AnnotationChart legend is very different from other chart legends,
partly because it is showing the values that you hover over.
Unfortunately, there is no way currently to display the legend until you
hover over a value, not even by programmatically selecting a value (with
Glad to hear you got it working, though I am still puzzled about how the
URL will be constructed properly.
On Mon, Aug 25, 2014 at 6:23 PM, gulb...@gmail.com wrote:
Hi,
I just wanted to let you know the following fixes the issue:
change
google.load(visualization, 1, { packages:
Hi Angelica,
There is no after-page event, but I can imagine reasons why you would want
it. Can you tell us how you would use it? Maybe we can offer some
workaround.
If the table chart triggered a 'ready' event after the internal redraw for
paging and sorting, would that be enough to handle
Getting data from a local file would be a security risk for the user who
finds your page on the web. If your page is also local, not accessed via
an http url, then fetching local static files could work. The next
question is what format? The only kind of text file that can be loaded is
either
Hi Rob,
You have a couple different choices.
First, on
https://developers.google.com/chart/interactive/docs/spreadsheets#queryurlformat
it talks about adding a range parameter to your spreadsheet url, like
*range=A1:C4*
But since your data values are arranged across columns (D2, E2, and F2),
Could you create a separate sheet with the transposed data in it using the
Transpose formula? That way, when the data is updated, the formula would
automatically create the updated transposed version of it.
To do this in JavaScript, here is an outline of the tasks:
1. Fetch the data
The transpose formula should do this, if you use it with the appropriate
parameters. You can leave off the letter or number in a part of the range
to indicate all rows or columns. So in your case, to get rows 1 and 2 of
all columns after column D, try =TRANSPOSE(D1:2)
On Wed, Oct 22, 2014 at
Maybe you should look again at your earlier solution, to extract the data
in the client side code using the 'query' option for the chart wrapper.
'query':'SELECT C,D,E,F WHERE C = r...@domain.com ',
I missed the fact that you could select the row of data you want that way.
But then you still
Rob,
You may not need this anymore, but in case anyone else is interested, I
learned from one of the Spreadsheet developers how you can do a transpose
of a row of data that you search for by a string.
Basically, do the search with MATCH, and specify the range of cells to be
transposed with
Since you say you are using tabs, and the sizing is wrong, this is most
likely due to Google Charts not being able to draw the chart correctly if
it is not visible when you do the draw. If that is the case, there are a
few solutions which all amount to drawing the chart only when it becomes
Steven,
What you are trying to do seems like a long-shot, with several obstacles
beyond just getting the SVG string.
But it turns out there is an undocumented 'dump' method on CoreCharts that
might work to give you this SVG string, although I believe it depends on
first having generated the SVG
The general problem is that the whole chart, including the legend, is
erased and redrawn at each step of the animation. So if any part of the
display is to not flash, it must be redrawn correctly at each stage of the
animation. Animating the legend changes seemed fairly pointless relative
to
Tim,
Your thinking about this is just fine. The explorer mode changes the
viewWindow of the chart's axes, but these changes are not reflected in any
internal state of the chart. Consequently, when you draw the chart again,
the viewWindow changes are lost, and reset to the default, or whatever
Hi Neo,
First, you will happy to know that the next release (coming out real soon
now) will have some significant performance improvements as well as an
option to draw asynchronously, which will greatly improve the interactivity
of the ChartRangeFilter with a large amount of data.
Constructing
Hi Stephen,
Your assumption that the chart should show all your data is correct.
Currently, the chart will silently hide data that can't be show with enough
resolution. It is not clear whether 2 pixels are required as a minimum,
but it seems 1 pixel should be sufficient. But note that you
Hi Samuel,
What you want to use is the explicit 'ticks' option for the vertical axis
to specify the values where you want those horizontal gridlines to show
up. If you also want the labels to be like in your example, 'y1', ...
'y5', then you'll want to specify each tick with its formatted value
I see one potential problem, which would explain why some types of browsers
have problems. You have some extra commas in your option object literals.
Look for any commas preceding a '}'. Use this instead:
var options={
width:800,
height:600,
interpolateNulls:true,
hAxis:{
Hi Vijay,
You are probably drawing the piechart when it is not visible on the page.
This causes the text measurer to not know how wide the text is, so it puts
it in the wrong place. If you can arrange to wait until the container is
visible before drawing the chart, this should fix the problem.
Yesterday, Feb 18, Google Charts V41, was released to production.
However, several problems were found, and we attempted to rollback the
release today. But the rollback is also failing, so we are stuck between a
rock and a hard place, as the saying goes.
Since we already have fixes for most of
James,
I'm seeing two types of errors in the developer tools on your page now:
Uncaught TypeError: Cannot set property 'onfocus' of undefined
Uncaught Error: Invalid row index 5122. Should be in the range [0-70].
The second error, we have a fix for.
The 'onfocus' error seems to be due to this
Lewis, the table elements have changed, so if you have css code that
depends on internal use of css, then you will have to update accordingly,
or better, use the cssClassNames option so your own class names will be
used.
The width of the table content being set to 0 is most likely due to drawing
James, the fixes did go out, one of which addressed the indexing of
selections in Dashboards.
We have been updating the documentation, but there is always more to do.
We are glad you are getting value from Google Charts. Sorry for the
inconveniences this release has caused. Hopefully they will
The new fixes did get applied, but you will only see them if you load
1.0.
The fixes did not include changes for the Table chart sizing, because we
didn't have enough to go on to determine what should be changed. Please
provide a link to a page showing the incorrect behavior you are seeing so
we
The rollback is now in progress, and will hopefully finish in about 4
hours, judging from previous experience.
On Thu, Feb 19, 2015 at 12:26 PM, SJA steven.ain...@gmail.com wrote:
Daniel
Our experience today has been charts not rendering when previously
(yesterday) they did or in the case of
Hi Joel,
You can use Google Charts for free, (see
https://developers.google.com/chart/terms) but you can't include the code
itself in your product. Nor is the source code available. The Google
Charts library is loaded into browsers in compiled and obfuscated form;
though it is JavaScript
We have pushed a new Google Charts Release Candidate (RC) - V41
Candidate release date: January 13, 2015
Anticipated production release date: January 27, 2015
New features / bugs fixed:
-
Calendar chart - support 0 values.
-
Histogram - automatically constrain number of
When you have a lot of columns in the available width, it will try to drop
some of the category labels, or slant them, in order to fit as many as can
comfortably fit. The 'chartArea' option is for specifying the area inside
the axes, relative to the overall chart width and height. So if your
Sorry, we don't have any configuration options for the color of the
prev/next links in the legend. It should inherit from the top-level option
for the text color, so this is a bug.
On Thu, Mar 26, 2015 at 8:04 PM, f...@txn.com wrote:
Hello there!
We've noticed that the prev/next links
Sorry Dimitry, we were unable to rollback the release this time around.
And there is no way to point to the old code now.
If you can point us a page that shows your broken tables and line charts,
we will be happy to look into it. Or you might prefer to email me directly
(dlalibe...@google.com).
There was an announcement of a new candidate release last Thursday. This
should only affect those who are loading 1.1.
David, I can tell by looking at your code that you are calling the
chartwrapper draw() method with a datatable, which is not correct, and the
source of the problem. It used to
Patrike,
We would like to provide more features like what you are requesting, more
general across all the charts, but this is difficult to do with the current
code base. As we redevelop charts, we will keep this goal in mind.
On Wed, Apr 22, 2015 at 9:12 PM, Khrys khrysl...@gmail.com wrote:
I
I see the problem now, even in Chrome on Linux. Thanks. Just needed to
know what I was looking for.
On Mon, Apr 20, 2015 at 12:26 PM, Jean-Rémi Delteil
jeanremi.delt...@gmail.com wrote:
Hi Daniel,
I'm using Firefox Chrome on Window 8, last version both.
Follow a capture of the problem.
Hi Jean-Rémi,
Which browser are you using? I am not seeing any problem with the tooltips
in Chrome on Linux.
On Mon, Apr 20, 2015 at 11:11 AM, Jean-Rémi Delteil
jeanremi.delt...@gmail.com wrote:
I had to report a detail on the Timeline chart,
It was also here on the previous version V41
We have pushed an update of the new Google Charts Release Candidate (RC) -
V42. This should start to be available within a couple hours.
This update fixes a couple bugs and adds a couple small features:
- The 100% stacking feature for AreaChart shows correct values in
tooltips.
-
This is a bug we are aware of that will be fixed in the next release.
Until then, you can add viewWindow min and max options to specify the range
you want: https://jsfiddle.net/jj2rej9L/5/
On Sat, May 2, 2015 at 9:34 AM, M S Dasaradh thasarat...@gmail.com wrote:
Your code looks fine. The problem might be in your data. You could try to
just display a table chart, not even a dashboard, just to see what data is
being fetched.
Looking in your spreadsheet, I see that column E, after row 3111, is all 0s
for 53000 more rows. That could be cause the chart to
Sorry Fernando, the chart layout is limited to showing either a right-side
axis or a legend on the right, but not both.
On Thu, May 7, 2015 at 4:00 PM, Fernando Iwamoto fernando.iwam...@gmail.com
wrote:
When comment the series and vAxes to make my right y-axis appear, the
legend on the right
We have pushed a new Google Charts Release Candidate (RC) - V42. This
should start to be available within a couple hours.
*Candidate release date: April 16, 2015Anticipated production release date:
as soon as May 4, but not before a frozen V41 is available.Please test this
candidate release
Sounds like what you want is the hAxis.slantedText and .slantedTextAngle
options to specify that the tick labels for the hAxis should be slanted.
You can override the heuristics that decide whether to use slantedText, and
then override the default angle with those two options. Try this:
var
Good to hear V42 is working for a few people. It would be reassuring to
have more people test their pages with V42 by loading 1.1.
I am particularly concerned that the Table chart is behaving as expected,
given the surprises of V41, and since I made a lot more changes under the
covers for V42.
If you only have a single data point, you will get some odd results by
default. You can constrain the automatic computation of how the chart is
laid out by using the viewWindow min and max options. So you would want to
add something like:
hAxis: { viewWindow: { min: new Date(2015, 0, 1) } }
Hi Luke,
The problem is just that the values for your SalesVal column are actually
strings rather than numbers. The PieChart apparently doesn't complain
about the data when it is provided in this format, and instead, it fails
silently. There should at least be an error message about being
Assuming you are trying to draw one of the corecharts or GeoChart, you'll
probably want to generate an image for the chart and send that in the
email. See https://developers.google.com/chart/interactive/docs/printing
But how you get that image into an email will require additional work on
your
Shahid,
The ColumnChart does not have a 'chart' option. That's for the material
charts only, at this point. For the column chart, just use the 'title'
option.
On Sun, May 24, 2015 at 5:57 AM, Shahid Majeed shahid.maj...@gmail.com
wrote:
Hi,
I am using google column chart in my website and i
Allessandro, it sounds like you are setting the height to 100%. If you
don't want the height to expand, then leave the height as unspecified. If
it is another problem, post enough code that we can reproduce it, or
better, link us to your page, or create an example on jsfiddle.
On Mon, Aug 24,
Loading '1.0' will only fix problems caused by the new candidate release
until it becomes the production release, which will be the coming Monday.
So instead, you should either address the cause of the problem or switch to
using the frozen loader for version 41.
I haven't seen anything like error
After an extended delay while we finished preparing Frozen Google Charts
for version 41 (see
https://developers.google.com/chart/interactive/docs/library_loading_enhancements#frozen-versions),
we are now starting a new phase in the release of version 42, which we are
calling the pre-production
Hi Paul,
You should be able to freeze the header row with heights other than 100%.
And you can also specify a height on the container.
If you are still having trouble figuring out how to make it work, can you
point me at your page, or set up an example on jsfiddle? Thanks.
On Mon, Aug 24,
Vamshik,
We were never successful in deploying v43 by the usual process, such that
loading with google.load('visualization', 1, ...) would work. But loading
v43 via the frozen version loader is working. (see
Henrik,
Thanks for your report. Your two jsfiddle links appear to have identical
scripts, and I don't see a problem when loading both controls and table.
It has been the case that the Table chart is available if you load almost
anything, but the styles won't necessarily be correct unless you
Kevin,
I'm not sure how that could be happening unless the deployment is partially
successful, and then rolls back when it doesn't complete.
But you can switch to loading the frozen version 43 and it should reliably
stay the same from now on, except for a few updates will will make to fix
Hi Matthew,
Since the release candidate for version 43 was never successfully pushed
out, you are actually still running version 42.
The problem you and others are experiencing with multiple 'material' charts
(any type) is avoided if you use version 43 with the frozen version
loader. See
I notice that your examples use window onload to determine when to draw the
charts. This is not good enough since the libraries are loaded
asynchronously, and may not finish until sometime later. So you should use
setOnLoadCallback().
I changed your example to use the frozen loader with version
The v43 release candidate (which would only affect you if you load 1.1) is
not quite out, due to deployment problems, so that couldn't be a cause of
the problem. I'm not sure when this deployment will be finished, but
perhaps as early as this afternoon.
The font-related problems people are
Robert,
If you are not calling google.load() until after the document has finished
loading, then the google.setOnLoadCallback function will not be called.
You'll need to add a 'callback' property to your google.load() call
instead. For the details, see
The production release of v42 is now rolling out. The production release
means that if you use google.load() to load Google Charts for version 1,
or 1.0, or 1.1, you will get the same thing, which is v42. Because of
the pre-production release last week, you will only see a difference once
the
We are about to push a new Google Charts Release Candidate (RC) - V43. This
the push is uneventful, it should be finished by the evening of Monday, Oct
5.
In the meantime, you can try it now via the Frozen Google Charts loader by
loading '43'. See instructions at
My mistake. For the anticipated production release date, I meant to say
Monday, Oct 26.
On Fri, Oct 2, 2015 at 2:28 PM, Daniel LaLiberte
wrote:
> We are about to push a new Google Charts Release Candidate (RC) - V43.
> This the push is uneventful, it should be finished
V45 is now available on the gstatic server by loading either "upcoming" or
"45" with google.charts.load(). If you are using the old jsapi loader,
you should try using the new loader by switching your code to the following:
https://www.gstatic.com/charts/loader.js">
There is no option to just color negative areas differently, although that
would be a good idea.
But you can get a similar effect by filling the negative area with another
area chart. Here is a modification of the previously posted example that
does that: http://jsfiddle.net/bnugqpjx/6/
On
Hi Patrick,
V45 was actually rolled out, which I mentioned in my May 9 comment. This
was only a release on the old jsapi server.You are correct that we
neglected to add to the release notes, but I was waiting until I could
finish rolling out to the new gstatic server. But now that has been
This is mostly a security related fix, and as such, you shouldn't see any
changes for the most part. The end-of-the-month bug was actually caused by
one of those fixes, but we should have a fix for that bug out before the
end of this month.
As I mentioned in the email, the one visible change is
An update for v45 on the old jsapi server should show up in an hour or two,
hopefully. This is a candidate release for a couple days, and then it will
go to production on Wednesday or Thursday.
This update only affects the code loaded via the jsapi loader, not the
gstatic loader. If you
We are not changing anything, not since I threw the switch last Thursday so
that 'current' now redirects to '44' instead of '43'. The errors seem to
be due to caches not behaving as we expected. I would like to hear from
someone that clearing their browser cache helped, but perhaps there are
We are not seeing any problems here, but if you change 'current' to '44',
it should work better.
On Mon, Feb 29, 2016 at 4:13 AM, John Ellwood
wrote:
> Hi
>
> The word trees chart examples no longer work at
>
>
It appears that when we push out a new version, there are some hiccups in
the system until the changes fully propagate. We will be working to fix
this in the future, but for now, if you get these kinds of errors, I
suggest you refresh the page, flushing your cache if necessary.
You can also
In your google.charts.load() call, you can replace 'current' with '43' or
'44' to avoid the redirections, which seems to be the cause of the problems
people are seeing.
On Fri, Feb 26, 2016 at 3:38 PM, Dwayne Etchison
wrote:
> Hello,
>
> I use google charts in one of
We have pushed Google Charts v44.
Summary of changes for v44:
- Corecharts:
- Timeofday values now use UTC internally, which fixes problems with
truncated timeofday axes.
- Added options to specify bar.width, bar.gap, bar.group.width (was
bar.groupWidth)
We have pushed a new Google Charts Release Candidate (RC) - *V44*.
Candidate release date: Feb 16, 2016
Anticipated production release date: Feb 23, 2016
New features / bugs fixed:
Summary of changes for v44:
-
All:
-
Changed timeofday values to use UTC internally. This
Sorry Kevin. We haven't done any work on reenabling the legend animation.
Not sure when we will be able to get to it.
On Fri, Feb 19, 2016 at 7:43 PM, Kevin Hofmaenner <
kevin.hofmaen...@gmail.com> wrote:
> Hi Daniel,
>
> Thanks for responding. Do you know if anything pertaining to the legend
>
It works if you refresh your browser cache. I made a change that should
help update these caching problems soon, if it works.
On Tue, Mar 1, 2016 at 3:28 PM, David Canady wrote:
> Gauge charts no longer work, as of yesterday. Even the example on the
> Google Charts
Unfortunately, the formatter only knows how to treat date units in the
typical way, so hours are limited to 24 hours in a day. Since we use the
formatting utilities provided by Google Closure, I'm not sure when we will
be able to generalize this.
On Tue, Apr 5, 2016 at 9:33 AM, Leandro Godek
Hi Per,
Can you point us to a page demonstrating what you are seeing?Thanks.
On Thu, Mar 17, 2016 at 4:04 AM, Per rock wrote:
> Hello,
>>
>
> I don't know if this is in relation with the new version, but since 4
> days, all informations on my different chart
Sorry, but there is no support for tooltips on the table chart.
On Tue, Mar 22, 2016 at 5:10 AM, Prakash A wrote:
> I am creating a *Table* using Google Charts Table.
>
> I wish to add *tool-tip* for the *header* row. May I know how it could be
> done.
>
> PS: I am NOT
Hi Jafar,
We are not doing any development on the deprecated google image charts, so
if you want point shapes, you'll have to switch to using the Google Charts.
On Wed, Mar 23, 2016 at 11:30 AM, Jafar S wrote:
> Hi
>
> I have a requirement to build a chart (assume google
All the loading problems should be resolved now. We found the cause of the
problem, which was caching of redirects that were not updating as expected.
We changed the loader so it uses a different way of mapping 'current' to
'44' that avoids the redirects. So everything that was failing for
We are about to push a new Google Charts Production Release - *V45*.
Previously we announced the Release Candidate on April 7 here:
https://groups.google.com/forum/#!topic/google-chart-api/eMOR1jsS6No
The production release was delayed until now because we were trying to work
around a problem,
There was another question about this recently:
https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/google-visualization-api/X6Mad7NCCPU/GKD-kQ3LGAAJ
I made this example to show how it can be done:
http://jsfiddle.net/dlaliberte/f7r3odo7/
On Thu, Apr 14, 2016 at 12:14 PM, Robert
You have to save your code with jsfiddle, otherwise you get a 'pure' empty
page.
You can disable interactivity by setting the enableInteractivity option to
false.
On Tue, Apr 19, 2016 at 3:47 PM, Erik F wrote:
> Hi all!
>
> When clicking on a line on a line chart
Erik, you should check out the tooltip.trigger option.
On Wed, Apr 20, 2016 at 9:44 AM, Erik F wrote:
> Hi,
>
> Sorry, thought it got saved since i borrowed it from Google Chart API
> pages.
>
> Thanks for the suggestion regarding the enableInteractivity option. I do
Google Charts depends on running in a browser, or at least a browser-like
environment. It is possible to use webkit in a server to simulate the
browser-like environment, but we don't have any docs on how you might set
that up.
On Wed, Jul 27, 2016 at 12:58 PM, carinlynchin
The message about calculated columns needing a 'type' property is true
regardless. We fixed a bug in v44 that allowed the 'type' property to be
missing, and now things that depended on the bug are still being exposed.
The startup animation feature is one of those things. A coupld of these
Hi Karim,
Sorry about messing up the v45 release on the gstatic server.
Unfortunately, I did an update (and check-in) late last week that turned
out to be very flawed, but even more unfortunately, it is also impossible
to undo since I don't have the previous version that was also broken, but
in a
Version 45 on the gstatic server should now be working reliably with
multiple google.charts.load() calls. This includes support for
ChartWrapper calls that dynamically load the appropriate package for your
type of chart.
Please test this new version, by loading '45' or 'upcoming' and let us know
With the interpolateNulls option set to true, this should be enough to
cause interpolation. Does it work correctly without the curveType:
'function' option? If so, then that is a bug.
Otherwise, it is difficult to tell what is happening without seeing your
data. Could you inline a sufficient
The most straightforward way to implement your two-line chart is to put
each year of data in a separate column. Just use the month name (or
number) for the domain values rather than the full dates, and label the
columns according to the year.
On Thu, Sep 1, 2016 at 5:37 AM,
After many delays, and further work on security issues, I have finally
deployed v45 on the gstatic server. This means that when you call
google.charts.load('*current*', ...) you will get v45. If you want to
continue using the previous version, you can change '*current*' to '*44*'.
There
Jack,
IE9 has become much more difficult to do any tests on, and so we have given
it much less attention since Microsoft also stopped supporting it. We
certainly haven't tried to break support for it, and if something stops
working, we'd at least like to know why, and maybe we can fix it if it
There should be no link to
https://www.gstatic.com/charts/current/css/util/util.css created by loading
Google Charts. I would guess you are using this URL by some independent
means, rather than what the loader at
http://www.gstatic.com/charts/loader.js does for you. If this is not
true, I would
If the problem is how to combine the top 10 and the logged-in physician in
the same datatable, you'll probably need to construct a DataTable or
DataView from the two sets of data in the browser, unless you can do it
with a query to your database.
In addition, you might want to put the values for
Hi Cindy,
We added a heuristic a couple years ago that tries to include 0 (or
whatever your baseline value is) in the chart if it is 'close enough' to
your data. This was particularly important for bar and column charts,
where the length of a bar should be determined visually from the baseline.
You can get the range of values for a column (with
datatable.getColumnRange(columnIndex) ) and use the min value for
viewWindow.min. That is probably better than setting the baseline.
On Wed, Apr 5, 2017 at 12:02 PM, Cindy wrote:
> Is there a way to have the baseline always
Your container element, the "chart_div", appears to be what you should be
using, but it appears your drawChart() function ends before you define the
chart and draw it.
};
var chart = new
google.charts.Line(document.getElementById('chart_div'));
chart.draw(data,
You can create the chart one time (with new
google.visualization.PieChart()) and draw it multiple times with different
data and options each time.
On Thu, May 25, 2017 at 9:33 AM, Andrew Barker
wrote:
> Hi I am using google charts API, im calling a pie chart here is
Hi Michelle,
Is there any error reported in your browser's debugger?
You left out the HTML, but I assume you have two divs with ids "chart_div"
and "chart_div2".
The data could make a difference. Just to check that you are getting the
data you expect, you could change the chart from
There is a new bug that your code exposes, which happens when there is only
a single date value for the domain axis. This is a problem because it
can't tell what the range of the axis should be with only one point, but
you can work around it by adding a minValue or maxValue to define the range
Hi Yves,
Have you found the StringFilter at
https://developers.google.com/chart/interactive/docs/gallery/controls#stringfilter_1
Sounds like what you want.
On Wed, Nov 27, 2019 at 1:17 AM Yves De Jesus wrote:
> i have a lot of building data that I want my users to filter using a
> search bar.
1 - 100 of 105 matches
Mail list logo