[OSGeo-Discuss] Batch geocoding
Wladimir Szczerban
bolosig at gmail.com
Mon Feb 7 00:34:11 PST 2011
Hi JP,
I work in the IDEC (Spatial Data Infrastructure of Catalonia).
You can contact the ICC (www.icc.cat) and explain that you need to codify
some directions for a thesis. Maybe give you some access to their
geocoder, though
they are quite closed to that topic.
In the list of geoinquiets was treated this subject in a post titled "la
importancia de les dades obertes" of January 21, 2011. See the thread that you
might get something that works for you.
Cheers,
2011/2/6 JP Glutting <jpglutting at gmail.com>
> FYI: Fusion Tables does not provide access to unlimited geocoding. There is
> a daily limit (not sure what it is, but I assume it is the same as the API)
>
>
> http://www.google.com/support/fusiontables/bin/answer.py?hl=en&answer=1012281
>
> The interface is nice for geocoding, though, because it has some nice
> features for adjusting the geocoding location on the fly. I have about 100
> pages of addresses to check, but I am really only checking one or two per
> street name, since not finding a street seems to be the biggest problem for
> Google.
>
> When geocoding fails, it tends to assign a location to the centroid of the
> postal code in the address. It would be nice to be able to see these cases
> and fix them, but I can't figure out how to do this through the interface
> (if anyone knows, please let me know). i am going to look into the API.
>
> The only way I can think to do it would be to export the KML file (Postgis,
> etc), search for addresses that start with a postal code, and create a new
> file of bad addresses to upload back to Fusion to fix them by hand.
>
> Cheers,
> JP
>
>
> On Sun, Feb 6, 2011 at 12:35 AM, JP Glutting <jpglutting at gmail.com> wrote:
>
>> HJ,
>>
>> Is it the "partial_match" field in the results? If so, I am not sure if
>> that helps much. for example, these two addresses return
>> "partial_match":True
>>
>> CARRERO DE LES CAROLINES, 25, 08012, Spain
>> which returns the formatted address
>> Carreró de les Carolines, 25, 08012 Barcelona, Spain
>>
>> and
>>
>> TURO DE LA PEIRA, 31, 08031 Barcelona, Spain
>> returns
>> Turó de la Peira, Passeig de Fabra i Puig, 396, 08031 Barcelona, Spain
>>
>> While the former is probably fine, the latter is probably not.
>>
>> Oh well, I'm just going to keep working on cleaning the addresses and
>> formatting the fields better. Running queries from the python prompt make it
>> clear that little things make a huge difference. A few stray letters at the
>> start of an address can send google off into a whole different city.
>>
>> Cheers,
>> JP
>>
>>
>>
>> On Sat, Feb 5, 2011 at 10:53 PM, JP Glutting <jpglutting at gmail.com>wrote:
>>
>>> Hi HJ,
>>>
>>> That is the part I missed when I read the Google geocoding API. I don't
>>> see it on the geocoding API page [
>>> http://code.google.com/apis/maps/documentation/geocoding/]. Am I looking
>>> in the wrong place?
>>>
>>> Actually, now that I re-read it, it says that you can only use Google
>>> Geocoding with a Google map:
>>>
>>> Usage Limits
>>>
>>> Use of the Google Geocoding API is subject to a query limit of 2,500
>>> geolocation requests per day. (User of Google Maps API Premier may perform
>>> up to 100,000 requests per day.) This limit is enforced to prevent abuse
>>> and/or repurposing of the Geocoding API, and this limit may be changed in
>>> the future without notice. Additionally, we enforce a request rate limit to
>>> prevent abuse of the service. If you exceed the 24-hour limit or otherwise
>>> abuse the service, the Geocoding API may stop working for you temporarily.
>>> If you continue to exceed this limit, your access to the Geocoding API may
>>> be blocked.
>>>
>>> *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<http://code.google.com/apis/maps/terms.html#section_10_12>
>>> .*
>>>
>>>
>>> Whoops!
>>>
>>> Would you mind sending me the code you are using? I was using geopy to
>>> avoid having to spend time writing or learning about a JSON parser, but the
>>> example on the google page works for me. Is the geocoding quality part of
>>> the JSON results object? I don't see it.
>>>
>>> Cheers,
>>> JP
>>>
>>>
>>> On Sat, Feb 5, 2011 at 9:11 PM, Stark Hans-Jörg <hansjoerg.stark at fhnw.ch
>>> > wrote:
>>>
>>>> the mapping APIs provide indormation on the geocoding quality - this
>>>> will help you use only addresses with good geocoding quality.
>>>>
>>>> --hj
>>>>
>>>> Am 05.02.2011 um 20:26 schrieb "JP Glutting" <jpglutting at gmail.com>:
>>>>
>>>> Hi Hans-Jörg,
>>>>
>>>> That is a good point about the dataset. I am not sure how good it is in
>>>> Spain. I might try comparing Yahoo and Google (or at least it should be
>>>> possible to use my data for that), but I don't really have a "gold standard"
>>>> to compare them too.
>>>>
>>>> For my project, the accuracy of the locations are not as important for
>>>> interpolation (which would be based on 2-3 weather stations around
>>>> Barcelona, at best), but I also want to use satellite thermal IR images to
>>>> take a look at the temperature as well. Landsat 7 has a 60m resolution, but
>>>> there are methods for getting that down to 10m, and it could be very
>>>> important. My thesis advisor hasn't approved the TIR part of the project (he
>>>> might think it is too much), but I think I can do it. There are several
>>>> similar studies published, so the methods are not a mystery.
>>>>
>>>> I have enough addresses that I would be happy discarding the ones that
>>>> are erroneous and not trying to fix them all, but I am not sure how to
>>>> figure out which ones are poorly geolocated. Right now I know there are a
>>>> number that are bad, because the Fusion map shows them all over Spain, not
>>>> in Barcelona itself, but the accuracy of the points within the city itself
>>>> is a mystery. I might try to check on a sample, but I am afraid of what I
>>>> might find.
>>>>
>>>> Cheers,
>>>> JP
>>>>
>>>> Public Health - GIS - Bioinformatics
>>>> <http://www.bmeisis.com/>http://www.bmeisis.com
>>>> <http://www.bmeisis.com/> <http://www.jpglutting.com>
>>>> http://www.jpglutting.com
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Feb 5, 2011 at 8:00 PM, Stark Hans-Jörg <<hansjoerg.stark at fhnw.ch>
>>>> hansjoerg.stark at fhnw.ch> wrote:
>>>>
>>>>> mind you: Google licensed a high-quality dataset in Switzerland - in
>>>>> other words: I doubt that GM provides as good spatial accuracy in other
>>>>> countries per se.
>>>>>
>>>>> I'll checkmout the mentioned table (have currently no access). Your
>>>>> task sounds interesting - I would like to read your thesis / follow your
>>>>> work. But we could also continue on this via personal mail and not this
>>>>> list.
>>>>>
>>>>> cheers, hj
>>>>>
>>>>> Am 05.02.2011 um 18:28 schrieb "JP Glutting" < <jpglutting at gmail.com>
>>>>> jpglutting at gmail.com>:
>>>>>
>>>>> Brilliant! I will take a closer look at the PDF after I finish some
>>>>> things I need to take care of. The python code would be nice, but the truth
>>>>> is that this geocoding is a small part of the project (it is my UNIGIS
>>>>> Master's thesis as well :-), and if I can get decent geocoding through
>>>>> Google, then I would prefer not to get too caught up in that. I am looking
>>>>> at heat and mortality in Barcelona, and I need to generate a lot of
>>>>> interpolated temperature maps, so I would like to spend more time on that.
>>>>>
>>>>> From the images in the paper (figure 35) it looks like Google is better
>>>>> at locating the position of the address, but then in Table 12 it shows that
>>>>> Google's positional accuracy was slightly worse than Bing's. Do you know why
>>>>> that is?
>>>>>
>>>>> I'm geocoding addresses of people who died, so positional accuracy is
>>>>> important with regard to heat exposure. Which would you recommend?
>>>>>
>>>>> Actually, after reading some of that, maybe I should take a look at
>>>>> your code. It looks like I am going to need to do more to make sure these
>>>>> are correct. The difficult thing is that the addresses I have are
>>>>> abbreviated (like "CL/ LLEO, 12" which is really "Carrer del Lleó 12"), so
>>>>> it will be hard to check accuracy automatically.
>>>>>
>>>>> i am definitely citing your paper.
>>>>>
>>>>> Cheers,
>>>>> JP
>>>>>
>>>>> On Sat, Feb 5, 2011 at 5:53 PM, Stark Hans-Jörg <<hansjoerg.stark at fhnw.ch><hansjoerg.stark at fhnw.ch>
>>>>> hansjoerg.stark at fhnw.ch> wrote:
>>>>>
>>>>>> Hi JP
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hope this helps:
>>>>>> http://www.unigis.ac.at/club/bibliothek/pdf/40138.pdf
>>>>>>
>>>>>>
>>>>>>
>>>>>> In OA we are currently running a test-phase where we check all
>>>>>> user-digitised addresses versus open Geocoding engines like Bing, Google and
>>>>>> Yahoo. The comparison results shall then be an indicator of the quality of
>>>>>> the user entered address. Cf.
>>>>>> http://geolin01.cti.ac.at/openaddresses/ (to digitise) and
>>>>>> http://geolin01.cti.ac.at/openaddresses/qa/qareport to get the report
>>>>>> (and http://code.google.com/p/openaddresses/wiki/qa for a
>>>>>> description).
>>>>>>
>>>>>>
>>>>>>
>>>>>> I run the yahoo geocoding in python. If you want to see the code I
>>>>>> could provide it (it is not yet in the wiki) and perhaps you can take parts
>>>>>> of it for your purpose to avoid starting from scratch.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> hj
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Von:* <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org [mailto:<discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org] *Im Auftrag von *JP Glutting
>>>>>> *Gesendet:* Samstag, 5. Februar 2011 17:42
>>>>>>
>>>>>> *An:* OSGeo Discussions
>>>>>> *Betreff:* Re: [OSGeo-Discuss] Batch geocoding
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi HJ,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Yes, thanks, it is relevant. I was going to go looking for a reference
>>>>>> just like that. It looks excellent. Is there a PDF available? From the
>>>>>> image, it looks like Google is much better, but I can't read the table
>>>>>> online (and I don't seem to get GeoInformatics in the mail anymore, not sure
>>>>>> why).
>>>>>>
>>>>>>
>>>>>>
>>>>>> At this point, I am not sure I have much choice in the matter. I can
>>>>>> geocode the addresses in Google using fusion tables, but Yahoo seems to
>>>>>> start returning errors after a few thousand lookups per day via geopy.
>>>>>>
>>>>>>
>>>>>>
>>>>>> After spending some time fixing geocoding errors in fusion tables, I
>>>>>> think I am going to go back and edit the addresses in the source table and
>>>>>> re-export them to Fusion. It is putting addresses like "CL/ LLEO, 12,
>>>>>> Barcelona, Spain" in León. Adjusting that to "Carrer del Lleó, 12,
>>>>>> Barcelona, Spain" does a much better job, so I am going to go back and make
>>>>>> abbreviations like "CL/", "PA/", "RBLA", etc. explicit and try the geocoding
>>>>>> again. On the whole, it did a very good job, but there are a lot of
>>>>>> addresses that I need to fix. It would probably work better if I could
>>>>>> specify fields for City and Country (some of the addresses were encoded in
>>>>>> Bermuda, despite all having "Barcelona, Spain" appended to them).
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> JP
>>>>>>
>>>>>> On Sat, Feb 5, 2011 at 4:54 PM, Stark Hans-Jörg <<hansjoerg.stark at fhnw.ch><hansjoerg.stark at fhnw.ch>
>>>>>> hansjoerg.stark at fhnw.ch> wrote:
>>>>>>
>>>>>> BTW: the geocoding engines of Yahoo and Google provide different
>>>>>> spatial accuracy (cf.
>>>>>> http://www.geoinformatics.com/blog/in-the-spotlight/quality-assessment-of-volunteered-geographic-information-vgi)
>>>>>>
>>>>>>
>>>>>> But I do not know whether that is relevant for your task.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> hj
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Von:* <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org [mailto:<discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org] *Im Auftrag von *JP Glutting
>>>>>> *Gesendet:* Samstag, 5. Februar 2011 16:37
>>>>>>
>>>>>>
>>>>>> *An:* OSGeo Discussions
>>>>>> *Betreff:* Re: [OSGeo-Discuss] Batch geocoding
>>>>>>
>>>>>>
>>>>>>
>>>>>> For anyone who is considering using Fusion Tables, it has a very nice
>>>>>> feature that allows you to select a point that has been badly geocoded, and
>>>>>> find the right location searching in a small pop-up map, and then select
>>>>>> from a set of alternate locations. Your choice modifies the coordinates of
>>>>>> the geocoding, but not the address itself. A very nice and quite easy way to
>>>>>> fix problems.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> JP
>>>>>>
>>>>>> On Sat, Feb 5, 2011 at 12:37 AM, JP Glutting < <jpglutting at gmail.com><jpglutting at gmail.com>
>>>>>> jpglutting at gmail.com> wrote:
>>>>>>
>>>>>> It is pretty slick, but I just started using it about an hour ago, so
>>>>>> I haven't thought much about what to do with it. I did see a comment where
>>>>>> someone from Google said that reverse geocoding is not possible yet.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I am going to have to get up to speed with PostGIS, but this is a
>>>>>> pretty simple operation. I didn't number the addresses, but each event has a
>>>>>> real address and a "cleaned" address column in a table. The CSV that I
>>>>>> uploaded to Fusion was just a "select distinct..." of the cleaned addresses,
>>>>>> so it will serve as a lookup table for all the addresses in the original
>>>>>> table. I'm not sure how I am going to reorganize the tables afterward, but I
>>>>>> want to interpolate temperatures for each data point based on other data
>>>>>> that I have, and I think PostGIS only does simpler operations right now, so
>>>>>> I might have to export the points into shapefiles for each day an event
>>>>>> occurs and do splines in another package, then copy the interpolated values
>>>>>> back into the database. I am sure there is a more elegant way to do that, I
>>>>>> really need to think about it some more.
>>>>>>
>>>>>>
>>>>>>
>>>>>> (Oh, hey, I just saw that you can compile R into Postgres. That is
>>>>>> pretty crazy, but potentially totally awesome: <http://postgis.refractions.net/pipermail/postgis-users/2009-March/022894.html><http://postgis.refractions.net/pipermail/postgis-users/2009-March/022894.html>
>>>>>> http://postgis.refractions.net/pipermail/postgis-users/2009-March/022894.html
>>>>>> )
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> JP
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Feb 5, 2011 at 12:17 AM, Dan Putler <<dan.putler at sauder.ubc.ca><dan.putler at sauder.ubc.ca>
>>>>>> dan.putler at sauder.ubc.ca> wrote:
>>>>>>
>>>>>> Glad to be of help, I'm just curious about what the licensing / terms
>>>>>> of use on the KML files that come out of fusion tables. Plus I want to know
>>>>>> if it will reverse geocode. It is very slick, but I can imagine violating
>>>>>> the terms of use almost instantly.
>>>>>>
>>>>>> In terms of your next problem (which seems like one for the PostGIS
>>>>>> user list), did you create a unique address ID? if you did, can't you put it
>>>>>> in the data you created the fusion table from and then just do the
>>>>>> appropriate table join in Postgres/PostGIS?
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 02/04/2011 03:08 PM, JP Glutting wrote:
>>>>>>
>>>>>> That is a nice trick, I will remember that. I really just need the
>>>>>> coordinates, since each coordinate needs to go back into a database in a
>>>>>> register of a location-time that needs more data added later. These are the
>>>>>> "generic" addresses, with the apartment numbers stripped, so each address
>>>>>> will provide coordinates for multiples DB entries on different dates, and I
>>>>>> won't really be using them on the same layer. But I am sure I can figure out
>>>>>> a way to get the data back out with PostGIS (the original data is in
>>>>>> Postgres anyway).
>>>>>>
>>>>>> Cheers,
>>>>>> JP
>>>>>>
>>>>>> On Fri, Feb 4, 2011 at 11:59 PM, Dan Putler <<dan.putler at sauder.ubc.ca><dan.putler at sauder.ubc.ca>
>>>>>> dan.putler at sauder.ubc.ca <mailto: <dan.putler at sauder.ubc.ca><dan.putler at sauder.ubc.ca>
>>>>>> dan.putler at sauder.ubc.ca>> wrote:
>>>>>>
>>>>>> JP,
>>>>>>
>>>>>> If you export the KML, and then feed it into QGIS you can then
>>>>>> save the resulting layer as a shapefile, which is probably what
>>>>>> you are really hoping to have since you can then easily feed it to
>>>>>> R, PostGIS, or a number of other tools to pull the coordinates.
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>> On 02/04/2011 02:20 PM, JP Glutting wrote:
>>>>>>
>>>>>> Hi Bernie,
>>>>>>
>>>>>> You can't actually get the lat-lng back out of a Fusion table.
>>>>>> It will geocode all the addresses, but you can't get the
>>>>>> numbers back, you can just make a map or layer or something.
>>>>>>
>>>>>> <http://groups.google.com/group/fusion-tables-users-group/browse_thread/thread/91c43c73107164eb><http://groups.google.com/group/fusion-tables-users-group/browse_thread/thread/91c43c73107164eb>
>>>>>> http://groups.google.com/group/fusion-tables-users-group/browse_thread/thread/91c43c73107164eb
>>>>>>
>>>>>> Unless I export it to KML and pull it back out of there?
>>>>>>
>>>>>> That seems like a lot of work. But it sure geocodes like
>>>>>> gangbusters.
>>>>>>
>>>>>> Cheers,
>>>>>> JP
>>>>>>
>>>>>> Public Health - GIS - Bioinformatics
>>>>>> <http://www.bmeisis.com> <http://www.bmeisis.com>
>>>>>> http://www.bmeisis.com < <http://www.bmeisis.com/><http://www.bmeisis.com/>
>>>>>> http://www.bmeisis.com/>
>>>>>> <http://www.jpglutting.com> <http://www.jpglutting.com>
>>>>>> http://www.jpglutting.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Feb 4, 2011 at 7:42 PM, Connors, Bernie (SNB)
>>>>>> < <Bernie.Connors at snb.ca> <Bernie.Connors at snb.ca>
>>>>>> Bernie.Connors at snb.ca <mailto: <Bernie.Connors at snb.ca><Bernie.Connors at snb.ca>
>>>>>> Bernie.Connors at snb.ca>
>>>>>>
>>>>>> <mailto: <Bernie.Connors at snb.ca> <Bernie.Connors at snb.ca>
>>>>>> Bernie.Connors at snb.ca <mailto: <Bernie.Connors at snb.ca><Bernie.Connors at snb.ca>
>>>>>> Bernie.Connors at snb.ca>>>
>>>>>>
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>> Try Google Fusion Tables. All you have to do is put all of
>>>>>> the
>>>>>> address components in one field and it should be recognized
>>>>>> and
>>>>>> geocoded.
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Bernie Connors, P.Eng*
>>>>>>
>>>>>> Service New Brunswick
>>>>>>
>>>>>> (506) 444-2077
>>>>>>
>>>>>> 45°56'25.21"N, 66°38'53.65"W
>>>>>>
>>>>>> <http://www.snb.ca/geonb/> <http://www.snb.ca/geonb/>
>>>>>> www.snb.ca/geonb/ < <http://www.snb.ca/geonb/><http://www.snb.ca/geonb/>
>>>>>> http://www.snb.ca/geonb/>
>>>>>> < <http://www.snb.ca/geonb/> <http://www.snb.ca/geonb/>
>>>>>> http://www.snb.ca/geonb/>
>>>>>>
>>>>>>
>>>>>> *From:* <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org
>>>>>> <mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org>
>>>>>> <mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org
>>>>>> <mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org>>
>>>>>>
>>>>>> [mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org
>>>>>>
>>>>>>
>>>>>> <mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org>
>>>>>> <mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org
>>>>>> <mailto: <discuss-bounces at lists.osgeo.org><discuss-bounces at lists.osgeo.org>
>>>>>> discuss-bounces at lists.osgeo.org>>] *On Behalf Of *JP
>>>>>> Glutting
>>>>>> *Sent:* Friday, 2011-02-04 09:34
>>>>>> *To:* <discuss at lists.osgeo.org> <discuss at lists.osgeo.org>
>>>>>> discuss at lists.osgeo.org
>>>>>> <mailto: <discuss at lists.osgeo.org> <discuss at lists.osgeo.org>
>>>>>> discuss at lists.osgeo.org>
>>>>>>
>>>>>> <mailto: <discuss at lists.osgeo.org> <discuss at lists.osgeo.org>
>>>>>> discuss at lists.osgeo.org <mailto: <discuss at lists.osgeo.org><discuss at lists.osgeo.org>
>>>>>> discuss at lists.osgeo.org>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Subject:* [OSGeo-Discuss] Batch geocoding
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have a large set of addresses (around 150k) that I need to
>>>>>> geocode for a study (my Masters thesis on heat-related
>>>>>> mortality).
>>>>>> I am looking into different solutions, but I can't find
>>>>>> anything
>>>>>> that seems like it would work properly.
>>>>>>
>>>>>> I could script a solution using Google's map API, but there
>>>>>> is a
>>>>>> limit of 2,500 addreses per day (I can get around them with
>>>>>> a
>>>>>> little patience).
>>>>>>
>>>>>> Right now the best solution I am looking at geopy for
>>>>>> geocoding
>>>>>> addresses ( <http://code.google.com/p/geopy/><http://code.google.com/p/geopy/>
>>>>>> http://code.google.com/p/geopy/). It seems like
>>>>>> a good
>>>>>> system, I think I can use it to pull addresses out of my
>>>>>> database
>>>>>> and write back coordinates. There is one thing that I am
>>>>>> not sure,
>>>>>> about, though, is whether I am actually allowed to use the
>>>>>> Google
>>>>>> API without my use being liked to a specific web page. The
>>>>>> terms
>>>>>> of service and form for getting a Google API key require a
>>>>>> URL
>>>>>> linked to a Google account. In fact, it looks like the API
>>>>>> can
>>>>>> only be used through a web site:
>>>>>>
>>>>>> "5.2 _Account Key_. After supplying Google with your
>>>>>> account
>>>>>> information and the URL of your Maps API
>>>>>> Implementation, and
>>>>>> accepting the Terms, you will be issued an alphanumeric
>>>>>> key
>>>>>> assigned to you by Google that is uniquely associated
>>>>>> with
>>>>>> your Google Account and the URL of your Maps API
>>>>>> Implementation. Your Maps API Implementation must
>>>>>> import the
>>>>>> Google Maps APIs using this key as described in the
>>>>>> Maps APIs
>>>>>> Documentation
>>>>>> < <http://code.google.com/apis/maps/documentation/><http://code.google.com/apis/maps/documentation/>
>>>>>> http://code.google.com/apis/maps/documentation/>, and Google
>>>>>>
>>>>>> will block requests with an invalid key or invalid URL.
>>>>>> You
>>>>>> may only obtain and use a key in accordance with these
>>>>>> Terms
>>>>>> and the Maps APIs Documentation
>>>>>> < <http://code.google.com/apis/maps/documentation/><http://code.google.com/apis/maps/documentation/>
>>>>>> http://code.google.com/apis/maps/documentation/>."
>>>>>>
>>>>>>
>>>>>> So it looks like I can't even get it to work without a URL.
>>>>>>
>>>>>> I can always write a script that loops through results
>>>>>> extracted
>>>>>> from the database, creates URLs and parses the XML results
>>>>>> one at
>>>>>> a time, but that seems like a fairly inelegant solution.
>>>>>>
>>>>>> Does anyone have any good ideas about how to geocode a few
>>>>>> thousand addresses?
>>>>>>
>>>>>> Many thanks,
>>>>>>
>>>>>> JP
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Discuss mailing list
>>>>>> <Discuss at lists.osgeo.org> <Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org <mailto: <Discuss at lists.osgeo.org><Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org>
>>>>>>
>>>>>> <mailto: <Discuss at lists.osgeo.org> <Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org <mailto: <Discuss at lists.osgeo.org><Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> <http://lists.osgeo.org/mailman/listinfo/discuss><http://lists.osgeo.org/mailman/listinfo/discuss>
>>>>>> http://lists.osgeo.org/mailman/listinfo/discuss
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Discuss mailing list
>>>>>> <Discuss at lists.osgeo.org> <Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org <mailto: <Discuss at lists.osgeo.org><Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org>
>>>>>> <http://lists.osgeo.org/mailman/listinfo/discuss><http://lists.osgeo.org/mailman/listinfo/discuss>
>>>>>> http://lists.osgeo.org/mailman/listinfo/discuss
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Discuss mailing list
>>>>>> <Discuss at lists.osgeo.org> <Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org
>>>>>> <http://lists.osgeo.org/mailman/listinfo/discuss><http://lists.osgeo.org/mailman/listinfo/discuss>
>>>>>> http://lists.osgeo.org/mailman/listinfo/discuss
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Discuss mailing list
>>>>>> <Discuss at lists.osgeo.org> <Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org
>>>>>> <http://lists.osgeo.org/mailman/listinfo/discuss><http://lists.osgeo.org/mailman/listinfo/discuss>
>>>>>> http://lists.osgeo.org/mailman/listinfo/discuss
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Discuss mailing list
>>>>>> <Discuss at lists.osgeo.org> <Discuss at lists.osgeo.org>
>>>>>> Discuss at lists.osgeo.org
>>>>>> <http://lists.osgeo.org/mailman/listinfo/discuss><http://lists.osgeo.org/mailman/listinfo/discuss>
>>>>>> http://lists.osgeo.org/mailman/listinfo/discuss
>>>>>>
>>>>>>
>>>>> <ATT00001..c>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Discuss mailing list
>>>>> <Discuss at lists.osgeo.org>Discuss at lists.osgeo.org
>>>>> <http://lists.osgeo.org/mailman/listinfo/discuss>
>>>>> http://lists.osgeo.org/mailman/listinfo/discuss
>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/discuss/attachments/20110207/ba86ed4d/attachment-0002.html>
More information about the Discuss
mailing list