Slashdot Mirror


Do You Recommend Google Maps API or Microsoft Live Maps?

KSobby writes "The organization that I work for is going to be redoing our website in .Net/AJAX. On the site, our members will have profile pages listing where their organizations are located (our members are scattered throughout the world) as well as other pertinent information for the general public. It is a non-profit organization, so funds are tight. My question to you: If we include maps, which API do we go with: Google or Microsoft? We're in a Microsoft environment (we're non-profit and Microsoft basically gives us everything for free) but the ubiquity of Google may be enough to sway us. Has anyone used either extensively? Used them in conjunction with .Net?"

3 of 252 comments (clear)

  1. Go with Microsoft, get MapCruncher by Anonymous Coward · · Score: 5, Informative

    I recently discovered MapCruncher which is a super cool add-on for the Microsoft Virtual Earth API. Basically, if you have any of your own high resolution maps (like PDF of a floorplan or bicycle route or whatever) you can align it to Virtual Earth and MapCruncher writes the thousands of tiny image tiles needed to make your map easily browsable right on top of Virtual Earth. Google doesn't have anything like this. (Even though Google Earth has an "image overlay" feature, they have nothing that runs in the browser, plus it forces the user to download the entire overlay image instead of just the tiny pieces they're trying to view.)

    MapCruncher rocks!

  2. Checkout refin.com's comparison by sp00 · · Score: 5, Informative

    Redfin did a decent writeup at the beginning of the year when they were deciding what technology to use. It was helpful to read when I was making the decision for the company I work for. Some of the things they point out have changed/been fixed, but it's still a good overview.

  3. OpenLayers.org API ! by Lord+Satri · · Score: 5, Informative

    Really. Don't want to get stucked by one of the numerous webmap providers? Use OpenLayers.org. OpenLayers, open source, will legally allow you to connect to Google, Microsoft, Yahoo! and other providers' data and switch between any without ever changin your code. No jokes, this is the best choice. Of course, it allows you to do *much* more. Want to learn more? Also, OpenLayers works perfectly with other widely used webmapping software, such as GeoServer.org and many others. See also the webmapping section over Slashgeo.org. (Yes I'm one of the founders, but it's really on-topic! :-) Why not read this entry on the webmapping APIs and data access.