[geomoose-psc] Google Geocoder

[Dan Little]

Not Mapbox -- Licensing problems
MapQuest -  Requires us to ship an API key in the demo in order for it
to function.

On Fri, Jul 1, 2016 at 9:49 AM, Brian Fischer <bfischer at houstoneng.com> wrote:
> Could we switch it to this?  https://open.mapquestapi.com/geocoding/ or https://www.mapbox.com/geocoding/    Still requires a key but maybe a little bit more flexible on licensing than Google or others.  Also uses OpenStreetMap data.
>
> Brian Fischer
> Vice President, GIS Project Manager
> Houston Engineering, Inc.
> O 763.493.4522 | D 763.493.6664 | M 763.229.2734
>
>
> -----Original Message-----
> From: geomoose-psc [mailto:geomoose-psc-bounces at lists.osgeo.org] On Behalf Of Dan Little
> Sent: Friday, July 01, 2016 9:38 AM
> To: James Klassen <klassen.js at gmail.com>
> Cc: GeoMOOSE PSC <geomoose-psc at lists.osgeo.org>
> Subject: Re: [geomoose-psc] Google Geocoder
>
> 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
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-psc