[mapguide-users] MapGuide versus Google Maps Number of Features

2013-02-13 Thread Jim O'Leary
I am doing some research on the benefits of MapGuide versus Google Maps. Can someone explain why MapGuide can render seemingly unlimited features on the map while Google Maps can only render a few hundred before the browser chokes? Thanks -- View this message in context:

Re: [mapguide-users] MapGuide versus Google Maps Number of Features

2013-02-13 Thread Zac Spitzer
Mapguide works server side outputting images Google Maps is client side using vectors Most modern browsers can render thousands of vector points, it's just mainly older crust versions of IE which can't handle it. On Thu, Feb 14, 2013 at 3:13 PM, Jim O'Leary joleary.pub...@gmail.comwrote: I

Re: [mapguide-users] MapGuide versus Google Maps Number of Features

2013-02-13 Thread Hans Milling
As a side node. If you add a KML layer to your Google map, the layer will be rendered by the Google server. Then you can put thousands of features on the map with no problem. Only problem I had is to properly control the order of the layers. Also Google’s server caches the images (tiles) generated