The new google maps api needs to have the sensor parameter on the end of the query string. You can check it out in the docs here:

http://code.google.com/apis/maps/documentation/geocoding/#GeocodingRequests

Otherwise it'll throw this confusing error. So to geocode an address you need to do:

http://maps.google.com/maps/api/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&sensor=false

where that last bit (&sensor=false) is the important bit. It's a new thing and that query parameter specifies whether you're on a location aware device (such as an iphone).

Jeff Larson

209

You'll likely find better help over at the Google Maps API Google group.

John Heasly

472

Apologies if this is repetitive (I actually haven't had a chance to read through this thread yet). This was part of my answer to the "What should a Hacks/Hackers glossary aimed at programmers contain?" thread and Phillip asked me to post it here:

...Introduce programmers to how newsrooms operate, because programmers who join newsrooms are likely there to work on projects that compliment reporting. Introduce programmers to the basic editorial structure: how newsrooms are organized; how newsrooms operate day-to-day; how stories go from concept, to reporting, to editing, to publish; who and how many people a programmer is likely to be working with on a project (in our case: reporters, several editors, designers, the copy desk, the web producers, in some cases, IT), etc.

It would be great to see case studies of how projects came to be. The WaPo's recent "Top Secret America" would be a good one. Derek Willis gave a really interesting talk at an ONA meetup on producing NYT's Toxic Waters . The video is somewhere online, but I can't find it. Greg Linch probably has the link, so hopefully he'll see this.

devinvarsalona

60