I've encountered a strange bug with Mapquest and I was curious if anyone else has had this experience. I use Mapquest to pinpoint locations using lat-long coordinates, both before and after trips. What I've found is that every so often a particular latitude or longitude entry causes Mapquest to freeze up; but if you change your coordinates by one second, it works fine. For instance, my collection coordinates for Choccolocco Creek in Calhoun County, Alabama, this past Saturday were N 33 42 35, W 85 41 08. Mapquest won't display this. But changing the W coordinates to W 85 41 07 works fine.

Does anyone have any insight on this, or similar experiences? Thanks.

I no longer use mapquest, but I entered the coordinates in http://maps.google.com and it seems to work.

It works if you enter some other coordinates first....

I use Terraserver quite a bit if I want to see USGS topo's or black and white aerial. Some parts now have color. You can also download the small portions that are you viewing with geocorrected files to throw them into ArcGIS. I've entered points in Dec Degrees and gotten pretty accurate/precise locations, down to the 0.00001 which is great, often better than my crappy hand held GPS unit.

I've become stuck on using Mapquest because I've found that their road mapping system made the most sense to me, useful for finding sites I've never visited before. But maps.google.com has better aerial images of a landscape that will go to higher resolution levels. The google images of the Choccolocco Creek site lead me to realize that driving in to the Mayden flame chub collecting site might not be as awkward as I'd thought, and I also realized that our collection group had gotten closer to that site than I'd realized. So as usual, it depends on exactly what you're looking for. And I still can't get Mapquest to show me the precise GPS coordinates that I recorded in the field; my best explanation to date is that the fairies don't want me to do it...