Hi >From reading the relevant constraint ie Queries with spatial predicates only return data from within this first 100,000 rows. Therefore, if you apply a filter to a very large table and the filter matches data in rows after the first 100K, these rows are not displayed. The maximum size of table you can filter(Query) is 100K.
Regards Davie On Monday, March 5, 2012 3:09:49 PM UTC, Henri wrote: > > From what I read about fusion tables, up to 100k rows can be marked on the > map. However, if your fusion table has say 1m rows, you are able to query > the relevant rows required to be mapped using the fusion api and then plot > from the views table. > > So, if there were 1m rows for data points across the whole of the UK, but > only 50k in Cardiff then you would be able to select from the 1m rows to > create a view table with 50k rows then you would be able to display these > on > the map. > > > https://groups.google.com/forum/?fromgroups#!topic/fusion-tables-users-group/385ig9FG3UM > > Is that what Rebecca from this thread is suggesting or have I misread? > Because I've tried uploading 1.3 million rows to the fusion tables and its > well within the 100mb limit. > > Thanks > > -----Original Message----- > From: Barry Hunter > Sent: Monday, March 05, 2012 2:41 PM > To: google-maps-js-api-v3@googlegroups.com > Subject: Re: [Google Maps API v3] Re: Performance scaling google maps > application > > There is a limit of 100,000 geocoded rows in a single table. > > So that is a fundermental limitation. It will also only render a > limited amount of data in a single tile (500 features?) - so in heavy > populated areas, features wont show. > > (also 100Mb of data per table, and 250Mb per account. Which makes > working with large datasets hard.) > > > Also there isn't 'clustering' as such. It just tries to plot all > features. Although you do have the heatmap option, which is a sort of > clustering - but does end up obscuring the map with large datasets. > > - I would say Fusion tables, is for small or medium datasets - not > large ones - currently. > > (I use geocubes - with a dataset of 2.1M features, so that does scale > to large datasets! Note I am only a user, not an affiliate!) > > And KML definitly wont cope with this - at least on Google Maps (1000 > features is a practical limit - but can do slightly more). KML can > however be used for Google Earth - as can use regions to make a > SuperOverlay/SuperLayer. > > > On Mon, Mar 5, 2012 at 2:28 PM, Henri Cammiade <henri.cammi...@gmail.com> > wrote: > > Excellent, thanks for the advise. Probably server side clustering would > be > > more suitable as all the results need to "be" there. However, what about > > KML > > overlays or Fusion tables? Has anybody had much experience with either of > > these and can comment on the performance? > > > > Thanks, > > Henri > > > > -----Original Message----- From: Barry Hunter > > Sent: Monday, March 05, 2012 2:22 PM > > To: google-maps-js-api-v3@googlegroups.com > > Subject: Re: [Google Maps API v3] Re: Performance scaling google maps > > application > > > > > > btw, that is only one approach. > > > > Doing server side 'clustering' might be better suited (rather than > > just picking a sample). There are various ways to do that. > > https://www.google.com/search?q=server+side+clustering+google+maps > > > > Or you can just outsource it > > http://geocubes.com/ > > one of a few sites offering it :) > > > > > > On Mon, Mar 5, 2012 at 2:17 PM, Barry Hunter <barrybhun...@gmail.com> > > wrote: > >> > >> Here is a map that does that > >> http://wales.portal.geographs.org/map.php?view=thumbs > >> > >> Ok, that particular map is not using millions of markers, but the same > >> technique works for bigger datasets. (I just dont have any big > >> datasets using v3 of the maps api) > >> > >> The biggest issue is deciding which features to show as the 'sample'. > >> Picking random works reasonably well. But there are more elaborate > >> ways of doing it. You could perhaps pick the top rated (if your > >> dataset has that) > >> > >> On Mon, Mar 5, 2012 at 1:58 PM, Henri Cammiade < > henri.cammi...@gmail.com> > >> wrote: > >>> > >>> Yes. Obviously it is pointless displaying markers in areas half way > >>> around > >>> the world to the view port. The DB has millions of locations - what is > >>> the > >>> best way to build the gmap for high performance of loading initial > >>> markers > >>> and for loading additional markers on pan/zoom. > >>> > >>> Thanks > >>> > >>> On Mar 5, 2012 3:16 AM, "Rossko" <ros...@culzean.clara.co.uk> wrote: > >>>> > >>>> > >>>> > I'd like to know what are the best strategies and practises to use > >>>> > when building a google map that has millions of markers. > >>>> > >>>> Go back a step and re-examine your needs. A viewer isn't goimg to get > >>>> much value out of a map with millions of markers on it, so you could > >>>> perhaps think about what you want to actually show at any given time > >>>> (perhaps from an available pool of millions of markers) > >>>> > >>>> -- > >>>> 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. > >>>> > >>> -- > >>> 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. > > > > > > -- > > 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. > > > > -- > > 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. > > > > -- > 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. > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/V7cxfZ6GVQgJ. 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.
