title: How to handle large numbers of pushpins in Bing Maps
body: <p>I am using Bing Maps with Ajax and I have about 80,000 locations to drop pushpins into. The purpose of the feature is to allow a user to search for restaurants in Louisiana and click the pushpin to see the health inspection information.</p>
  
  <p>Obviously it doesn't do much good to have 80,000 pins on the map at one time, but I am struggling to find the best solution to this problem. Another problem is that the distance between these locations is very small (All 80,000 are in Louisiana).  I know I could use clustering to keep from cluttering the map, but it seems like that would still cause performance problems.</p>
  
  <p>What I am currently trying to do is to simply not show any pins until a certain zoom level and then only show the pins within the current view.  The way I am currently attempting to do that is by using the viewchangeend event to find the zoom level and the boundaries of the map and then querying the database (through a web service) for any points in that range.  </p>
  
  <p>It feels like I am going about this the wrong way.  Is there a better way to manage this large amount of data?  Would it be better to try to load all points initially and then have the data on hand without having to hit my web service every time the map moves.  If so, how would I go about it?  </p>
  
  <p>I haven't been able to find answers to my questions, which usually means that I am asking the wrong questions. If anyone could help me figure out the right question it would be greatly appreciated.</p>