How can I use Google's Geocoding to normalize addresses without violating the terms of service?

I'm working on a API that will accept addresses in searc开发者_高级运维hes. We would like to use Google's geocoding service to normalize the addresses before submitting the search criteria to our search engine.

This caught my attention: http://code.google.com/apis/maps/documentation/geocoding/index.html#Limits

"Note: the Geocoding API may only be used in conjunction with a Google map; geocoding results without displaying them on a map is prohibited. For complete details on allowed usage, consult the Maps API Terms of Service License Restrictions."

Does this mean we can't use the Geocoding service for this purpose? Having used libraries that access Google's geocoding service before, I know it's technically possible to do this but it sounds like a violation of the terms of service.

Are there other options for what we're trying to do?

Edit:

It turns out our company does have a license with Google to use the addresses that come back, and they will eventually be displayed on a Google Map to the end user, satisfying the terms of our agreement.

Short answer: You can't. The terms of service seem pretty clear-cut that geocoding using their API is not in line with their terms, unless you display them on a Google Map.

If you need this for other purposes, you should consider licensing a Geocoding library and dataset(s) for your regions of interest. There are quite a few companies which sell these for commercial purposes.

Update on this really old post:

@Cerin pointed out something important on this answer.

USPS Web Tools API are only free if you're using them to ship via USPS

So be legal.

You are correct: you can't use the Google Geocoder for address cleaning.

You can use this wrapper to access USPS's Web Tools.

Another inexpensive solution is Semaphore, but you'll have to write your own wrapper class to call the DLLs.

The USPS has a free service to validate addresses. It's in a fairly easy-to-use API that you can curl information to and receive a valid response back. The only rub is that they're a little slow when it comes to registering, and they require you to run several tests before they'll open it up. Regardless, once you've jumped through the hoops, it does a great job. It's been keeping addresses in my app clean for quite a while now without any hiccups.