Comment 17 for bug 624981

Is this bug because the sensor parameter is now mandatory? If so it isn't going to be fixed at the Google end, it needs to be fixed in Launchpad. I think when including the google api javascript there should be a sensor parameter after the key, so instead of:

http://maps.google.com/maps?oe=utf-8&client=gme-canonical&file=api&v=2&key=ABQIAAAACeZ5XCmHJlEwBYdSuT5n8xSpSJz2e5W2U1FEKkpRR5DvAoRnExQHcQr64ybfyPfb3_vaIFpvET1ZJg

it should be:

http://maps.google.com/maps?oe=utf-8&client=gme-canonical&file=api&v=2&key=ABQIAAAACeZ5XCmHJlEwBYdSuT5n8xSpSJz2e5W2U1FEKkpRR5DvAoRnExQHcQr64ybfyPfb3_vaIFpvET1ZJg&sensor=false

There are several points in the google maps javascript where the parameters including the sensor parameter get passed to different bits of the google maps back end and it seems that the sensor parameter is required, but up to recently has not been enforced.

I started down this line of thinking after reading this:
http://help.hackshackers.com/questions/648/the-google-maps-api-server-rejected-your-request-the-client-parameter-specifie