[geomoose-psc] Google Geocoder
Dan Little
theduckylittle at gmail.com
Fri Jul 1 07:49:28 PDT 2016
geocoder.us was useful but the momentum for geocoding TIGER files in
Berkeley databases is not considered particularly modern.
On Fri, Jul 1, 2016 at 9:48 AM, James Klassen <klassen.js at gmail.com> wrote:
> I think an email saying we noticed it was down and offering to help maintain
> it might be worthwhile.
>
> I guess my real question is if geocoder.us is still useful to the community
> or has the world moved on to something else (OSM)? If it is useful to us
> and to others, we should look into helping maintain/support it.
>
>
> On Jul 1, 2016 09:37, "Dan Little" <theduckylittle at gmail.com> wrote:
>>
>> Schuyler Earl. Good luck. It's like 12 projects ago for him.
>>
>> On Fri, Jul 1, 2016 at 9:35 AM, James Klassen <klassen.js at gmail.com>
>> wrote:
>> > Do we know who was running geocoder.us? Maybe we could get it fixed.
>> >
>> >
>> > On Jul 1, 2016 05:03, "Dan Little" <theduckylittle at gmail.com> wrote:
>> >>
>> >> Hey Folks,
>> >>
>> >> geocoder.us appears to be defunct. The website doesn't load and there
>> >> certainly does not appear to be any geocodes being returned. This was
>> >> our default geocoder.
>> >>
>> >> The other geocoder with which we have code is the Google Geocoder.
>> >> I'm fixing it up right now to work (it wasn't) and to also include an
>> >> appropriate credit/disclaimer. However, I'm a bit worried as we are
>> >> probably running afoul the Google TOS. I see a few options:
>> >>
>> >> 1. Run with it. We're a very small fish in a very large pond.
>> >> 2. Do not include a Geocoder by default but provide instructions for
>> >> adding back in the Google geocoder (including setting an API key).
>> >> This runs ... "less" afoul the TOS depending on how you read them.
>> >> 3. Remove all the geocoders. They're all broken. Folks may not like
>> >> to see the code disappear.
>> >>
>> >> Long term (and I will file a ticket to this regard) we should probably
>> >> write our own Geocoder instructions or write a crappy
>> >> DIY/off-the-shelf-libs geocoder that works with the default parcel
>> >> data.
>> >>
>> >> Cheers,
>> >>
>> >> -Duck
>> >>
>> >> Reference tickets:
>> >> - https://github.com/geomoose/geomoose/issues/150
>> >> - https://github.com/geomoose/geomoose/issues/152
>> >> _______________________________________________
>> >> geomoose-psc mailing list
>> >> geomoose-psc at lists.osgeo.org
>> >> http://lists.osgeo.org/mailman/listinfo/geomoose-psc
More information about the geomoose-psc
mailing list