you could preload your application with a small set of gauges and switch between them, or use a lower resolution for your gauge data to let caching infrastructure keep them instead of constantly doing a full round-trip to draw the next gauge. Quick recommendation based on guess of underlying root problem: lose the additional, unused precision in the requests.
Of course, what you're asking for is a implementation that works more like a physical gauge, with a background image and a moving needle layer -- that's more trouble than its worth at this time. -- You received this message because you are subscribed to the Google Groups "Google Chart 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-chart-api?hl=en.
