<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
My vote would be for “a”, with a Note about probable deprecation of service in the demo. Then figure out what the next version will look like.
<div class=""><br class="">
</div>
<div class="">bobb</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 1, 2016, at 11:08 AM, Dan Little <<a href="mailto:theduckylittle@gmail.com" class="">theduckylittle@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Should we:<br class="">
a. Deliver 2.9.1 with Google.<br class="">
b. Deliver 2.9.1 without any 'enabled' Geocoder (comment out the entry<br class="">
in the mapbook) and write a quick "How To Enable The Googs".<br class="">
c. Deliver 2.9.1 with an alternative geocoder to replace <a href="http://geocoder.us" class="">
geocoder.us</a><br class="">
and leave the google code dormant as it was in 2.9.<br class="">
<br class="">
Aside:<br class="">
I'm not sure which of a-c would necessitate switching to 2.10 but<br class="">
these are all methods for addressing the same 'bug.'<br class="">
<br class="">
<br class="">
<br class="">
On Fri, Jul 1, 2016 at 10:41 AM, Eli Adam <<a href="mailto:eadam@co.lincoln.or.us" class="">eadam@co.lincoln.or.us</a>> wrote:<br class="">
<blockquote type="cite" class="">There is this, <a href="https://mapzen.com/products/search/?lng=-124.01556&lat=44.66743&zoom=12" class="">
https://mapzen.com/products/search/?lng=-124.01556&lat=44.66743&zoom=12</a><br class="">
not certain on licensing but seems very unrestricted.<br class="">
<br class="">
On Fri, Jul 1, 2016 at 8:03 AM, Dan Little <<a href="mailto:theduckylittle@gmail.com" class="">theduckylittle@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class="">We could ship 2.9.1 with Google and do a next-step. 2.9.1, I think,<br class="">
is basically ready for testing.<br class="">
<br class="">
On Fri, Jul 1, 2016 at 9:58 AM, James Klassen <<a href="mailto:klassen.js@gmail.com" class="">klassen.js@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class="">It may be old school, but I didn't see any good alternatives mentioned<br class="">
though.<br class="">
<br class="">
1. Violate Google TOS<br class="">
<br class="">
2. Cripple the Demo, but let people add it back. Also, removes it from<br class="">
regular testing.<br class="">
<br class="">
3. Who needs geocoders anyway? This might be OK for the parcel app users<br class="">
because they probably already have better local data anyway. But it doesn't<br class="">
help anyone else.<br class="">
<br class="">
Also, this means the 2.9.0 on OSGeo Live should be fixed.<br class="">
<br class="">
<br class="">
On Jul 1, 2016 09:49, "Dan Little" <<a href="mailto:theduckylittle@gmail.com" class="">theduckylittle@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class=""><br class="">
<a href="http://geocoder.us" class="">geocoder.us</a> was useful but the momentum for geocoding TIGER files in<br class="">
Berkeley databases is not considered particularly modern.<br class="">
<br class="">
On Fri, Jul 1, 2016 at 9:48 AM, James Klassen <<a href="mailto:klassen.js@gmail.com" class="">klassen.js@gmail.com</a>><br class="">
wrote:<br class="">
<blockquote type="cite" class="">I think an email saying we noticed it was down and offering to help<br class="">
maintain<br class="">
it might be worthwhile.<br class="">
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br class="">
Yes, a nice courtesy.<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class=""><br class="">
I guess my real question is if <a href="http://geocoder.us" class="">geocoder.us</a> is still useful to the<br class="">
community<br class="">
or has the world moved on to something else (OSM)? If it is useful to<br class="">
us<br class="">
and to others, we should look into helping maintain/support it.<br class="">
<br class="">
<br class="">
On Jul 1, 2016 09:37, "Dan Little" <<a href="mailto:theduckylittle@gmail.com" class="">theduckylittle@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class=""><br class="">
Schuyler Earl. Good luck. It's like 12 projects ago for him.<br class="">
<br class="">
On Fri, Jul 1, 2016 at 9:35 AM, James Klassen <<a href="mailto:klassen.js@gmail.com" class="">klassen.js@gmail.com</a>><br class="">
wrote:<br class="">
<blockquote type="cite" class="">Do we know who was running <a href="http://geocoder.us" class="">
geocoder.us</a>? Maybe we could get it fixed.<br class="">
<br class="">
<br class="">
On Jul 1, 2016 05:03, "Dan Little" <<a href="mailto:theduckylittle@gmail.com" class="">theduckylittle@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class=""><br class="">
Hey Folks,<br class="">
<br class="">
<a href="http://geocoder.us" class="">geocoder.us</a> appears to be defunct. The website doesn't load and<br class="">
there<br class="">
certainly does not appear to be any geocodes being returned. This<br class="">
was<br class="">
our default geocoder.<br class="">
<br class="">
The other geocoder with which we have code is the Google Geocoder.<br class="">
I'm fixing it up right now to work (it wasn't) and to also include<br class="">
an<br class="">
appropriate credit/disclaimer. However, I'm a bit worried as we are<br class="">
probably running afoul the Google TOS. I see a few options:<br class="">
<br class="">
1. Run with it. We're a very small fish in a very large pond.<br class="">
2. Do not include a Geocoder by default but provide instructions for<br class="">
adding back in the Google geocoder (including setting an API key).<br class="">
This runs ... "less" afoul the TOS depending on how you read them.<br class="">
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br class="">
Running a demo of geocoding in GeoMoose seems fine as a demonstration.<br class="">
We probably shouldn't distribute a working demo with an API key.<br class="">
Right now, it would take work to run a different demo than what we<br class="">
distribute as the demo. So that makes a case for remove it from the<br class="">
demo.<br class="">
<br class="">
With something like this, it seems providing directions and maybe an<br class="">
example (but not working with an API key) is the correct path. That<br class="">
allows the user to evaluate the TOS and whether they are appropriate<br class="">
for them.<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">3. Remove all the geocoders. They're all broken. Folks may not<br class="">
like<br class="">
to see the code disappear.<br class="">
<br class="">
Long term (and I will file a ticket to this regard) we should<br class="">
probably<br class="">
write our own Geocoder instructions or write a crappy<br class="">
DIY/off-the-shelf-libs geocoder that works with the default parcel<br class="">
data.<br class="">
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br class="">
Let's avoid writing geocoders, even lame parcel ones.<br class="">
<br class="">
Best regards, Eli<br class="">
<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">
<blockquote type="cite" class=""><br class="">
Cheers,<br class="">
<br class="">
-Duck<br class="">
<br class="">
Reference tickets:<br class="">
- <a href="https://github.com/geomoose/geomoose/issues/150" class="">https://github.com/geomoose/geomoose/issues/150</a><br class="">
- <a href="https://github.com/geomoose/geomoose/issues/152" class="">https://github.com/geomoose/geomoose/issues/152</a><br class="">
_______________________________________________<br class="">
geomoose-psc mailing list<br class="">
<a href="mailto:geomoose-psc@lists.osgeo.org" class="">geomoose-psc@lists.osgeo.org</a><br class="">
http://lists.osgeo.org/mailman/listinfo/geomoose-psc<br class="">
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
_______________________________________________<br class="">
geomoose-psc mailing list<br class="">
<a href="mailto:geomoose-psc@lists.osgeo.org" class="">geomoose-psc@lists.osgeo.org</a><br class="">
http://lists.osgeo.org/mailman/listinfo/geomoose-psc<br class="">
</blockquote>
</blockquote>
_______________________________________________<br class="">
geomoose-psc mailing list<br class="">
<a href="mailto:geomoose-psc@lists.osgeo.org" class="">geomoose-psc@lists.osgeo.org</a><br class="">
http://lists.osgeo.org/mailman/listinfo/geomoose-psc</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); font-family: 'Comic Sans MS'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 20px; widows: 1; background-color: rgb(255, 255, 255);" class=""><br class="Apple-interchange-newline">
"I'm not interested in preserving the status quo; I want to overthrow it.”</span></div>
<div style="color: rgb(0, 0, 0); font-family: 'Comic Sans MS'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 20px; widows: 1; background-color: rgb(255, 255, 255);" class=""><span class="Apple-tab-span" style="white-space: pre;"></span>- Niccolo
Machiavelli</span><br style="box-sizing: border-box; color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 20px; widows: 1; background-color: rgb(255, 255, 255);" class="">
<br class="">
</div>
<div style="color: rgb(0, 0, 0); font-family: 'Comic Sans MS'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
</div>
</body>
</html>