On Jan 4, 7:41 pm, sandy037 <[email protected]> wrote: > @ bratliff > > do you want me to prioritize polylines based on zoom level? If so, may > be I can do it based on length of each user's selection. But does this > mean I have get polyline data in different files depending on the > length? Could you throw me some light on how to do this and make it > look as clustering of markers or some other way in which to reduce the > load time. Could you provide me some example code of how polycluster > works with point reduction based on zoom level?
If you are able fit your many short polys into a file of approximately 100K, you are OK. A file of a million bytes is too large to keep your users happy. Something in between will have to be your call. I use "highway category" to segregate the "US Highway" polys. I also segregate by state. All Interstate highways for California are in the same file. All US highways are in another file by state. All State highways are in another file by state. The last two sets of files are quite large. Separation by county might be beneficial. I will have to rebuild all of the files once the 2010 Census Department shapefiles are available. About half of the shapefiles are already available. Your application may be completely different. I do not know what criteria you use to select polys. Try to group your polys according to expected usage patterns. I believe you can assume no one person is interested in looking 20,000 polys at the same time. -- 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.
