13 Comments
- bitterbug, on 12/26/2008, -0/+9Is that from a programming or non-programming perspective?
- keegangrayson, on 12/26/2008, -1/+6Yeah, I'd rather ***** a Bonobo
- JYoungest1, on 12/27/2008, -1/+5I like how their are no comments, either no one understands, or no one cares.
- CDWMobile, on 12/26/2008, -0/+3Dugg for GIS and the GeoWeb
- tuxisawesome, on 12/27/2008, -0/+3lol
- bobbonew, on 12/26/2008, -3/+6Google API = hard to use
- inactive, on 12/28/2008, -0/+1Or programmers are mostly quiet.
- inactive, on 12/28/2008, -0/+1So would I, but the APIs are easy for me...
- Scaryclouds, on 12/27/2008, -0/+1I have used the Google Map API to make a fairly advanced realty map. I would say most of the difficulties result from working with an AJAX application over actual difficulties of utilizing Google's API, though I did have some difficulties getting the map to work as advertised.
- gdonald, on 12/28/2008, -0/+1I use OpenLayers. The main advantages are:
1) No registering your domain with Google to use their API is required.
2) Your map won't have Google logos on it.
3) The OpenLayers.js lives on your server so you can make local intranet maps that work offline, very handy for closed research environments.
4) OpenLayers is more generic than Google's API, look at the OpenLayers examples page for interesting edge case usage. - jsqurred, on 12/28/2008, -1/+1answer - google webtoolkit
- ryanrk, on 12/26/2008, -0/+0ditto
- PopovIsovSerov, on 12/27/2008, -5/+0you made first page with only 7 comments?


What is Digg?
Digg is coming to a city (and computer) near you! Check out all the details on our