iam not familiar with fusiontables but it looks interessting...so basicly you use spreadsheeds to display your data, or iam wrong on that ?
and you just create all the time a new infowindow and set height and with manualy ? On 31 Jan., 17:13, 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. > > @en4ce- thanks for your feedback. Actually we don't use different > icons for different zoom levels. When you zoom out what you see is a > Heatmap which shows different colors based on marker density, rather > than individual markers. We use the experimental FusionTablesLayer to > present a large number of markers on a single map, and this approach > has some advantages, but it also has drawbacks - we can't cluster the > markers and can't present different icon types based on category. We > hope these features will be supported by FusionTablesLayer in the near > future. > You can read more about Google Maps + Fusion Tables > here:http://code.google.com/apis/maps/documentation/javascript/overlays.ht... > > I didn't understand the question re InfoWindows - we configure the > info window using FusionTables - essentially each info window is a > little snippet of HTML that we can define the way we want. > > Thanks, > Michael Weinberg > > On Jan 31, 5:16 am, en4ce <djen...@googlemail.com> wrote: > > > > > > > > > its nice that you use different marker icons for different zoom > > levels, but still i would suggest to use clusters > > > 1 question, how you realized the resizing of the infowindows? > > > On 31 Jan., 07:19, Chris Broadfoot <c...@google.com> wrote: > > > > Cool. > > > > Although, just from panning around a little bit, I got an alert: > > > > Geocoder failed due to: OVER_QUERY_LIMIT > > > > Chris > > > > On Mon, Jan 31, 2011 at 1:23 PM, Mike <weinbe...@gmail.com> wrote: > > > > Wanted to share our project called CitySale.ca which is built entirely > > > > on the Google stack: > > > > > Google APIs - App Engine, GWT, Maps, Fusion Tables, Geocoding, Places, > > > > Search, ... > > > > Google Tools - Analytics, DoubleClick, Webmaster > > > > > The GWT Client and the App Engine based server are also deeply > > > > integrated with Facebook APIs. > > > > > It is a bit scary to completely rely on a single company (Google) for > > > > all your technology/infrastructure needs, but at this point the > > > > benefits outweigh this concern. > > > > > Would be great to get some feedback and I would be happy to answer any > > > > questions about how the service was built. > > > > > p.s. if you are from Canada, we hope you would actually sign up and > > > > use the service too :) > > > > > the url is http://www.citysale.ca > > > > > Thanks, > > > > Michael Weinberg > > > > > -- > > > > 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<google-maps-js-api-v3%2B > > > > unsubscr...@googlegroups.com> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > > --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.
