Multiple planet files

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Just run the tool once (used 266)

What is the expected output? What do you see instead?

Expected one planet file, see three:

planet.osm.pbf
planet_old.osm.pbf
planet-130904.osm.pbf

also seeing an update file: update.osc.gz

The planet files are 22GB each and it would be nice if I wouldn't need all 
three, so what is needed and expected to be left after a successful run?

Original issue reported on code.google.com by rbi...@gmail.com on 10 Sep 2013 at 12:56

[GoogleCodeExporter]

Dear user, when the WHOLE process is finished successfully at least once and 
your regions maps are created, you can safely delete both planet-yymmdd.osm.pbf 
and planet_old.osm.pbf.

Please note:
- the above files are kept as backups because in most cases re-downloading is 
more expensive than disk space used by backups
- if the planet.osm.pbf file is corrupted during update for any reason, 
planet_old.osm.pbf can safely replace it in most situations. Osm2garmin tries 
to handle similar cases seamlessly where possible. If you delete 
planet_old.osm.pbf, such an automatic recovery is not possible and you could 
possibly end up with complete erasure of the working directory and re-starting 
from scratch.

Original comment by mantl...@gmail.com on 10 Sep 2013 at 1:07

• Changed state: WontFix
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

One more note: Any update<number>.osc.gz and update.osc.gz files can be safely 
deleted after successful processing. Under some circumstances it is even 
recommended to delete these files after a processing crash.

To save more disk space, you can safely delete the whole contents of the 
replication/hour folder in your working directory after successful planet 
update.

Original comment by mantl...@gmail.com on 10 Sep 2013 at 1:16

[GoogleCodeExporter]

Thanks for the answer!

Original comment by rbi...@gmail.com on 10 Sep 2013 at 5:30