Maps are easy, right? Right. Except... when they aren't.
What about when you need to mix different data types on your maps?
What about when the simple solutions (paging) to complex problems (too much data) don't cut it with your users?
What about when your scaling problems exceed the bounds of all the available solutions?
When building any kind of GIS on the web, whether with Bing Maps or Google Maps or something else, one of the things you need to realize is that the web is a far different environment from the desktop. Massive datasets have serious performance problems on the web. Although there are some built-in and add-on scaling solutions (clustering, polyline encoding), you can quickly run into issues like "unresponsive script" or just plain old horrible laggy performance on your map, when you attempt to zoom or pan with too many markers or polylines on the map.
In this talk, I'll walk through several such problems we encountered in the development of our Oil & Gas data browsing app, eTriever, and our initial, simplistic solutions, followed by our total re-write to provide a more robust and high-performance web map.