search

google-code-export / geobeagle

Automatically exported from code.google.com/p/geobeagle
1 stars 0 forks source link

Many Placed by: null and PARSE ERROR #166

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
After synchronising (via BCAching)I now get many caches with details as:
Placed  by: null 
Placed on: PARSE ERROR
...
These caches seems ok on the geocaching site. Also this does not affect all 
caches, but apparently 70% of them.

Original issue reported on code.google.com by jmlug...@gmail.com on 31 Jul 2010 at 5:23

GoogleCodeExporter commented 9 years ago 
Please email pocket query to stephen@theleengs.com and I will try it out.

Original comment by stephen5...@gmail.com on 31 Jul 2010 at 10:24

GoogleCodeExporter commented 9 years ago 
I tried to find out a way to send you the query (which I did not find), and 
ended up looking at the files on the phone.  I found a few zip file which may 
predate my use of geobeagle, and that was covering the same area.  Eventually I 
deleted all files in geobeagle/data and all similar files in download, I also 
asked GeoBeagle to delete all data and made a synch. This solved the problem.  
So it was probably due to some   older data downloaded directly.  What is 
strange is that GeoBeagle was indeed loading the data from BCaching last, so I 
did not suspect that it ketp some previous data (probably a caching mechanism).
Anyhow you can close the bug, sorry for the inconvenience. I hope my experience 
may help others having the same problem.

Original comment by jmlug...@gmail.com on 1 Aug 2010 at 6:47

GoogleCodeExporter commented 9 years ago

Original comment by stephen5...@gmail.com on 9 Sep 2010 at 3:58