On Jan 5, 9:50 am, bratliff <[email protected]> wrote: > On Jan 5, 2:02 pm, sandy037 <[email protected]> wrote: > > > any suggestions?? > > I am not sure I understand what your application is trying to do. > Building a custom map means you must host a tile server. Generally, > custom maps are not clickable without a lot of interaction with your > tile server. Rebuilding tiles every hour or every day is > impractical. Google's traffic service does it but it has the > resources to do it. >
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. > Your requirements exceed the limits of Google's KML service. You > really have to find a way to break your several thousand polys into > groups of a few hundred polys from which your users can select. > Without additional information, only you know the right way to subset > your polys. If you do decide to break your polys into manageable > subsets, I can help you with displaying a few hundred simultaneously. > The API will run out of gas with a few dozen. I am finding a way to subset my polys. Could you help me with displaying the few hundreds possible? Thank you -- 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.
