@Andrew - I agree, this is probably what has happened @Chris - I currently geocode on 'dragend' - do you recommend changing this?
@en4ce - with Google Fusion Tables you basically use the standard Google Maps API, but instead of creating the markers on the map, you load your geo data into a Fusion Table and present the data as a layer on the map. You can upload to Fusion Table manually (e.g. bulk upload) or using an API. In my case, when I have a new "geo-point" I use Fusion Table API to add to the table and also store it in my backend (App Engine) for presenting it out of the map. Once I add it to the table, a new layer is automatically generated and the new marker appears. As to info-window, you define a HTML "template" for you InfoWindow inside FusionTable and the InfoWindow can reference certain fields from the Table. In my case it is an image, title and address. Michael Weinberg On Feb 1, 1:28 am, Chris Broadfoot <c...@google.com> wrote: > On Tue, Feb 1, 2011 at 3:13 AM, Mike <weinbe...@gmail.com> wrote: > > @Chris- thanks for the feedback. It's weird that you get > > OVER_QUERY_LIMIT, it means that Google thought too many Geocoding > > requests were made from your IP. When you move the map (or search for > > location and move there) the geocoding is done from the client side, > > meaning that Javascript Maps API hits a query limit. API docs say that > > for most users and usages this shouldn't happen, but since it does I > > will look into this issue again. > > As Andrew said, maybe it's because I'm behind our corp proxy. I'll try it > from home tonight. Are you geocoding on the idle event? > > Chris > > --http://twitter.com/broady -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
