Hi there. Its come to the point in my project where i finally have some real world data to display. Even now its only a small subset.
In some cases we may end up rendering > 500 points on a map. However even now this small subset (100-500) i notice alot of slowdown, when panning/zooming e.t.c on the map. I realise this is probably a bingmaps limitation but im looking for ways to improve any bottlenecks.
Here is what i have done
1) Use a Dynamic layer to draw all my sites
2)Setup the dynamic layer zoomlist
3) Added display toggles to turn on/off various objects (most of with a rendered on different information layers). Things like kml/shapefiles e.t.c
4) limited what i render to only very small [image] objects
Do you have any other suggestions ? Ive also noticed it can be quite slow when rendering some kml files but that is less important for performance.
Any other suggestions ?
In some cases we may end up rendering > 500 points on a map. However even now this small subset (100-500) i notice alot of slowdown, when panning/zooming e.t.c on the map. I realise this is probably a bingmaps limitation but im looking for ways to improve any bottlenecks.
Here is what i have done
1) Use a Dynamic layer to draw all my sites
2)Setup the dynamic layer zoomlist
const int viewportWidth = 256;
const int viewportHeight = 256;
for (int zoomLayerIndex = 1; zoomLayerIndex <= 20; zoomLayerIndex += 1)
{
this.Dynamiclayer.ZoomGridList.Add(new ZoomGrid((int)(Math.Pow(2, zoomLayerIndex + 8) / viewportWidth),
(int)(Math.Pow(2, zoomLayerIndex + 8) / viewportHeight), zoomLayerIndex));
}
3) Added display toggles to turn on/off various objects (most of with a rendered on different information layers). Things like kml/shapefiles e.t.c
4) limited what i render to only very small [image] objects
Do you have any other suggestions ? Ive also noticed it can be quite slow when rendering some kml files but that is less important for performance.
Any other suggestions ?