<p dir="ltr">Actually, you might want to check the zip and tarball, but local settings might not make it into the builds from the demo anyway.</p>
<p dir="ltr">I can't remember the details off the top of my head though and don't have time to look for a couple days.</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Jul 2, 2016 04:01, "Dan Little" <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If Jim makes progress on getting <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a> back up and running we<br>
can switch back to it. For 2.9.1, I've added directions on how to get<br>
the Google Geocoder to work and have added code that requires that an<br>
API Key be added to local_settings.ini for it function.<br>
<br>
This does mean, however, the demo on Geomoose.org will not have a<br>
functioning geocoder.<br>
<br>
Thanks folks!<br>
<br>
On Fri, Jul 1, 2016 at 3:33 PM, James Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>> wrote:<br>
> Fixing <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a> might be good overall though and if we help we aren't<br>
> grifting.<br>
><br>
> The grifting argument applies to not using Google or others either which<br>
> leaves us with nothing.<br>
><br>
><br>
> On Jul 1, 2016 14:15, "Dan Little" <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>> wrote:<br>
>><br>
>> A pile of effort for minimal gain to our application.<br>
>><br>
>> If we want to release our stuff then. we can't be dependent on a service<br>
>> we were grifting.<br>
>><br>
>> On Jul 1, 2016 21:14, "James Klassen" <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>> wrote:<br>
>>><br>
>>> What about d) figure out what happened to <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a>?<br>
>>><br>
>>><br>
>>> On Jul 1, 2016 14:07, "Eli Adam" <<a href="mailto:eadam@co.lincoln.or.us">eadam@co.lincoln.or.us</a>> wrote:<br>
>>>><br>
>>>> On Fri, Jul 1, 2016 at 9:31 AM, Basques, Bob (CI-StPaul)<br>
>>>> <<a href="mailto:bob.basques@ci.stpaul.mn.us">bob.basques@ci.stpaul.mn.us</a>> wrote:<br>
>>>> > More discussion needed for anything other than “a”.<br>
>>>> ><br>
>>>> > We have some options we’ve been using locally that might work as a<br>
>>>> > replacement, but need to talk more about it first. Hence my, release<br>
>>>> > now,<br>
>>>> > and move to change later.<br>
>>>><br>
>>>> If we have no plans for "c" to come about in the near- or mid- term,<br>
>>>> then "b" would be the immediate and mid-term option. "a" to just<br>
>>>> delay "b" is not a good option. If we're going with "b" in the<br>
>>>> mid-term, let's go with "b" now.<br>
>>>><br>
>>>> Those are my thoughts, Eli<br>
>>>><br>
>>>> ><br>
>>>> > bobb<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > On Jul 1, 2016, at 11:24 AM, Dan Little <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > In terms of level of effort:<br>
>>>> > a. This is already done in master.<br>
>>>> > b. This would be 30-45 minutes worth of work.<br>
>>>> > c. Probably an hour, maybe two hours with testing.<br>
>>>> ><br>
>>>> > I'm willing to do "b" if folks think that dropping the geocoder from<br>
>>>> > the demo is a viable move.<br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 11:22 AM, Eli Adam <<a href="mailto:eadam@co.lincoln.or.us">eadam@co.lincoln.or.us</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > Good point Bob, I think we need two discussions: What to do past<br>
>>>> > 2.9.1? and What to do for 2.9.1?<br>
>>>> ><br>
>>>> > For beyond 2.9.1, I favor c, especially if Mapzen or something else is<br>
>>>> > a viable option. If there aren't viable options, then b sounds good<br>
>>>> > for long term.<br>
>>>> ><br>
>>>> > For 2.9.1, I think any options will work except we might want to<br>
>>>> > decide based on the long term. i.e. if the long term route is b, we<br>
>>>> > should do that now for 2.9.1 too.<br>
>>>> ><br>
>>>> > Eli<br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 9:16 AM, Basques, Bob (CI-StPaul)<br>
>>>> > <<a href="mailto:bob.basques@ci.stpaul.mn.us">bob.basques@ci.stpaul.mn.us</a>> wrote:<br>
>>>> ><br>
>>>> > My vote would be for “a”, with a Note about probable deprecation of<br>
>>>> > service<br>
>>>> > in the demo. Then figure out what the next version will look like.<br>
>>>> ><br>
>>>> > bobb<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > On Jul 1, 2016, at 11:08 AM, Dan Little <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > Should we:<br>
>>>> > a. Deliver 2.9.1 with Google.<br>
>>>> > b. Deliver 2.9.1 without any 'enabled' Geocoder (comment out the entry<br>
>>>> > in the mapbook) and write a quick "How To Enable The Googs".<br>
>>>> > c. Deliver 2.9.1 with an alternative geocoder to replace <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a><br>
>>>> > and leave the google code dormant as it was in 2.9.<br>
>>>> ><br>
>>>> > Aside:<br>
>>>> > I'm not sure which of a-c would necessitate switching to 2.10 but<br>
>>>> > these are all methods for addressing the same 'bug.'<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 10:41 AM, Eli Adam <<a href="mailto:eadam@co.lincoln.or.us">eadam@co.lincoln.or.us</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > There is this,<br>
>>>> ><br>
>>>> > <a href="https://mapzen.com/products/search/?lng=-124.01556&lat=44.66743&zoom=12" rel="noreferrer" target="_blank">https://mapzen.com/products/search/?lng=-124.01556&lat=44.66743&zoom=12</a><br>
>>>> > not certain on licensing but seems very unrestricted.<br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 8:03 AM, Dan Little <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > We could ship 2.9.1 with Google and do a next-step. 2.9.1, I think,<br>
>>>> > is basically ready for testing.<br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 9:58 AM, James Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > It may be old school, but I didn't see any good alternatives mentioned<br>
>>>> > though.<br>
>>>> ><br>
>>>> > 1. Violate Google TOS<br>
>>>> ><br>
>>>> > 2. Cripple the Demo, but let people add it back. Also, removes it<br>
>>>> > from<br>
>>>> > regular testing.<br>
>>>> ><br>
>>>> > 3. Who needs geocoders anyway? This might be OK for the parcel app<br>
>>>> > users<br>
>>>> > because they probably already have better local data anyway. But it<br>
>>>> > doesn't<br>
>>>> > help anyone else.<br>
>>>> ><br>
>>>> > Also, this means the 2.9.0 on OSGeo Live should be fixed.<br>
>>>> ><br>
>>>> ><br>
>>>> > On Jul 1, 2016 09:49, "Dan Little" <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>> wrote:<br>
>>>> ><br>
>>>> ><br>
>>>> > <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a> was useful but the momentum for geocoding TIGER files in<br>
>>>> > Berkeley databases is not considered particularly modern.<br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 9:48 AM, James Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > I think an email saying we noticed it was down and offering to help<br>
>>>> > maintain<br>
>>>> > it might be worthwhile.<br>
>>>> ><br>
>>>> ><br>
>>>> > Yes, a nice courtesy.<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > I guess my real question is if <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a> is still useful to the<br>
>>>> > community<br>
>>>> > or has the world moved on to something else (OSM)? If it is useful to<br>
>>>> > us<br>
>>>> > and to others, we should look into helping maintain/support it.<br>
>>>> ><br>
>>>> ><br>
>>>> > On Jul 1, 2016 09:37, "Dan Little" <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>> wrote:<br>
>>>> ><br>
>>>> ><br>
>>>> > Schuyler Earl. Good luck. It's like 12 projects ago for him.<br>
>>>> ><br>
>>>> > On Fri, Jul 1, 2016 at 9:35 AM, James Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> ><br>
>>>> > Do we know who was running <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a>? Maybe we could get it fixed.<br>
>>>> ><br>
>>>> ><br>
>>>> > On Jul 1, 2016 05:03, "Dan Little" <<a href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>> wrote:<br>
>>>> ><br>
>>>> ><br>
>>>> > Hey Folks,<br>
>>>> ><br>
>>>> > <a href="http://geocoder.us" rel="noreferrer" target="_blank">geocoder.us</a> appears to be defunct. The website doesn't load and<br>
>>>> > there<br>
>>>> > certainly does not appear to be any geocodes being returned. This<br>
>>>> > was<br>
>>>> > our default geocoder.<br>
>>>> ><br>
>>>> > The other geocoder with which we have code is the Google Geocoder.<br>
>>>> > I'm fixing it up right now to work (it wasn't) and to also include<br>
>>>> > an<br>
>>>> > appropriate credit/disclaimer. However, I'm a bit worried as we are<br>
>>>> > probably running afoul the Google TOS. I see a few options:<br>
>>>> ><br>
>>>> > 1. Run with it. We're a very small fish in a very large pond.<br>
>>>> > 2. Do not include a Geocoder by default but provide instructions for<br>
>>>> > adding back in the Google geocoder (including setting an API key).<br>
>>>> > This runs ... "less" afoul the TOS depending on how you read them.<br>
>>>> ><br>
>>>> ><br>
>>>> > Running a demo of geocoding in GeoMoose seems fine as a demonstration.<br>
>>>> > We probably shouldn't distribute a working demo with an API key.<br>
>>>> > Right now, it would take work to run a different demo than what we<br>
>>>> > distribute as the demo. So that makes a case for remove it from the<br>
>>>> > demo.<br>
>>>> ><br>
>>>> > With something like this, it seems providing directions and maybe an<br>
>>>> > example (but not working with an API key) is the correct path. That<br>
>>>> > allows the user to evaluate the TOS and whether they are appropriate<br>
>>>> > for them.<br>
>>>> ><br>
>>>> ><br>
>>>> > 3. Remove all the geocoders. They're all broken. Folks may not<br>
>>>> > like<br>
>>>> > to see the code disappear.<br>
>>>> ><br>
>>>> > Long term (and I will file a ticket to this regard) we should<br>
>>>> > probably<br>
>>>> > write our own Geocoder instructions or write a crappy<br>
>>>> > DIY/off-the-shelf-libs geocoder that works with the default parcel<br>
>>>> > data.<br>
>>>> ><br>
>>>> ><br>
>>>> > Let's avoid writing geocoders, even lame parcel ones.<br>
>>>> ><br>
>>>> > Best regards, Eli<br>
>>>> ><br>
>>>> ><br>
>>>> > Cheers,<br>
>>>> ><br>
>>>> > -Duck<br>
>>>> ><br>
>>>> > Reference tickets:<br>
>>>> > - <a href="https://github.com/geomoose/geomoose/issues/150" rel="noreferrer" target="_blank">https://github.com/geomoose/geomoose/issues/150</a><br>
>>>> > - <a href="https://github.com/geomoose/geomoose/issues/152" rel="noreferrer" target="_blank">https://github.com/geomoose/geomoose/issues/152</a><br>
>>>> > _______________________________________________<br>
>>>> > geomoose-psc mailing list<br>
>>>> > <a href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a><br>
>>>> > <a href="http://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
>>>> ><br>
>>>> > _______________________________________________<br>
>>>> > geomoose-psc mailing list<br>
>>>> > <a href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a><br>
>>>> > <a href="http://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
>>>> ><br>
>>>> > _______________________________________________<br>
>>>> > geomoose-psc mailing list<br>
>>>> > <a href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a><br>
>>>> > <a href="http://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > "I'm not interested in preserving the status quo; I want to overthrow<br>
>>>> > it.”<br>
>>>> > - Niccolo Machiavelli<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > "I like nonsense; it wakes up the brain cells."<br>
>>>> > - Dr. Seuss<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> _______________________________________________<br>
>>>> geomoose-psc mailing list<br>
>>>> <a href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a><br>
>>>> <a href="http://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote></div></div>