Alle - We don't recommend relying on just one geo-coding source...using Omniscope, you can start with coordinates from a merge file (free or commercial), then add corroboration/cross-referencing via Omniscope geo-coding formulae referencing one or even BOTH of the current geo-coding servers (yahoo & Cloudmade) giving you up to 3 sets of coodinates you can compare formulaically (with variable slider difference threshold tolerances) before deciding which source(s) are best for your file. You can even using search/replace blocks in DataManager to correct known errors not yet to be corrected in the geo-coding servers. We offer links to free services to which you can submit corrections (ideally as Omniscope IOK map view error files). We have seen errors in ALL services (the providers of these free services don't yet use Omniscope to scrub their data). Google had a city in Iraq in Afganistan, Yahoo has a US post code used for the Puerto Rican territory located in France...Cloudmade had a few postcodes at sea when verifying our new full-length UK post code merge file available as Lookup data in the Desktop Edition. Different geo-coding servers give different results depending not only on the country/location being geo-coded, but also how the exact search argument is presented. Yahoo, for example, does very well with just 5-digit US zip codes submitted, but not so well if UK postcodes are submitted. For this and other reasons, do not rely on a single source, especially since Omniscope makes it so easy to consult and compare many different sources. Adding Google geo-coding would not change this recommendation, and in any event is not currently possible (see below)

Note that Google's geocoding API specifically prohibits use of the API not in conjunction with a Google map. This is why we don't provide it.