Delete .zip/.gpx File After Import

[GoogleCodeExporter]

Another nice feature would be have GeoBeagle automatically delete files it
has imported to reduce reimport issues. Of course, this should be an option
that can be turned on/off by the user.

Original issue reported on code.google.com by mjpe...@gmail.com on 12 Jul 2009 at 3:46

[GoogleCodeExporter]

The way it currently works is a feature--if the gpx file is deleted, the 
corresponding caches will be deleted too 
from GeoBeagle.

Original comment by stephen5...@gmail.com on 15 Jul 2009 at 2:29

• Changed state: WontFix

[GoogleCodeExporter]

I'm hoping that this comment will be answered, but don't know if google code 
will
re-open this, or show you it when I answer.

I'll use my case as an example: I copy over the .zip archive that I am sent to
/sdcard/download and then run the import. A week later, I get a new .zip 
archive in
my email (same pocket query, same .zip archive name, same .gpx file names in 
the .zip
archive).

What happens when I overwrite the old .zip archive with the new .zip archive? 
How do
my new caches get imported? How do the old ones get updated?

That's the file I'd like to have GeoBeagle remove: The file under 
/sdcard/downloads
that should be useless for the Android user.

Original comment by mjpe...@gmail.com on 15 Jul 2009 at 2:41

[GoogleCodeExporter]

actually there is a bug in the MarketPlace version that keeps this from working 
properly; the latest version on 
the web site should be better.

What should happen is this: any new .zip files will get re-imported.  any old 
zip files will get ignored.  
GeoBeagle gets the times from inside the zip file itself (it uses the 
groundspeak export time, rather than the 
file timestamp).  caches which were in the old zip file will get deleted.

The idea is that geobeagle is "syncing" with the zip files on disk--what you 
see in geobeagle should mirror 
the contents of your import directory.

Original comment by stephen5...@gmail.com on 15 Jul 2009 at 2:48

[GoogleCodeExporter]

In which case, let me say wow. I never thought of doing something similar. Neat 
idea,
and it seems to work quite quickly.

And thank you for your quick responses!

Original comment by mjpe...@gmail.com on 15 Jul 2009 at 2:53

[GoogleCodeExporter]

Any idea when the new version will be pushed to the market? It's annoying to 
reload
my "nearest unfound caches" list and have recently found caches still appear on 
the list.

Original comment by d.b.mcg...@gmail.com on 27 Aug 2009 at 3:19

[GoogleCodeExporter]

The version which fixes the bug in comment 5 was pushed weeks ago, in the 
middle of 
July.  Please file a new bug report if you are seeing a problem.

Original comment by stephen5...@gmail.com on 27 Aug 2009 at 4:06