On Sep 23, 2:40 pm, MapSavage <[EMAIL PROTECTED]> wrote: > > Encoded polys may help a little but 3110 polys displayed > > simultaneously is too many. > > > That's what I was afraid of. > > > Which web service ? I am curious how it is done. > > Esri's ArcWeb Services. It is a pay as go service, each visit costs a > credit and is deducted from your account. ESRI builds a map image, > stores it for a period of time on their servers, and sends back the > link. It is OK, but I like the google maps look and feel, as well as > their pan and zoom capability. The client doesn't mind paying, it is > a gov't agency it is a low cost way for them to make maps available to > the public. > > I'm not quite sure how the tiling works. If the user is only > interested in a few counties, is it possible to just display them from > the tile? I thought tiles were an all or nothing proposition.
Tiles are fixed unless you have a clever back-end to generate tiles "on-the-fly". Individual poly "hide" / "show" is still impractical. Tiles are fast but static. Polys are dynamic but slow. For fewer than one hundred polys, the API mechanism works pretty well. For more than one hundred polys, the API mechanism runs out of gas. The best of both is a collection of previously rendered transparent PNG shapes which can be selectively positioned over the map. Unlike maps with a lot of detail, uniformly colored shapes stretch & squeeze well which means some intermediate zoom levels can be interpolated. Anti-aliasing will help. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
