On Jan 6, 2:44 pm, bratliff <[email protected]> wrote: > On Jan 6, 5:02 pm, Rossko <[email protected]> wrote: > > > > I guess thats true. It will be difficult to build tiles whenever a > > > user comes and modifies the something on the map say a new selection. > > > But not too difficult. Any given update will only affect some tiles > > (at various zoom levels), so you can have a large cache of pre-made > > tiles and only update a handful for each update. > > Perhaps he could augment yesterday's tiles with today's polys. I > suspect he will have to provide tiles for several different zoom > levels.
If its the case, I will have to provide all tiles for different zoom levels. And the caching takes large amounts of space further. I am thinking of grouping sets of polylines with different IDs based on distance from a fixed point in a city (sets are based upon concentric circles or concentric rectangles) and load those polyline sets as needed (as the user starts dragging). Each set might have say some hundreds of polylines. So, is there any problem with the google API to render some hundreds of polylines at a time? Also, I plan to lay more polylines as the user starts dragging the map. If the user starts dragging fast, it means I have to load more and more polylines at a time. Do you guys think if its feasible to do this way? -- 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 [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-maps-js-api-v3?hl=en.
