tucotuco
commented
11 years ago I have a theory, but I'm finding it interesting to test. Looking in the data store I see cached values for entities based on oakland no georeferences, suggesting that there is a primordial cache entry for 'oakland' that has no georeference. I did some GQL queries to locate them as Cache, Clause, and Locality entities, deleted them (they indeed had no georfefs), Flushed Memcache, and requeried on 'oakland' - still with no results.
I would completely flush the cache, but we've loaded a whole bunch of good stuff in there and I don't want to have to pay to load it again. Any ideas to figure out how to ferret out and purge the putative oakland with missing geocode?
On Tue, Mar 5, 2013 at 5:11 PM, Michelle Koo notifications@github.comwrote:
Not sure what's the issue here as one works and the other doesn't (tried with lower and uppercase on placename without effect) This locality query fails "2 mi W oakland":
which is confusing since this one worked "2 mi E alameda":
— Reply to this email directly or view it on GitHubhttps://github.com/GeomancerProject/geomancer-api/issues/70 .
eightysteele
Not sure what's the issue here as one works and the other doesn't (tried with lower and uppercase on placename without effect) This locality query fails "2 mi W oakland": http://beta.geomancer-api.appspot.com/api/georef?q=2%20mi%20W%20oakland&k=6b76a34e-00ec-4108-b197-f5acf8432165
which is confusing since this one worked "2 mi E alameda": http://beta.geomancer-api.appspot.com/api/georef?q=2%20mi%20E%20alameda&k=6b76a34e-00ec-4108-b197-f5acf8432165