Re. Issue 119. Too many updates. state.txt file problem?

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Updates following planet file download
2.
3.

What is the expected output? What do you see instead?
Reinstalled build 266, deleted the working directory, downloaded planet 130904 
ok. Update then started and looked like it would be around 10-15GB. Download 
was very slow, ran for 48hrs and completed only about 20%.

Please use labels and text to provide additional information.
Found issue 119. My state.txt file was full of garbage, downloaded a new 
state.txt and re-ran program. However same result, started a very large 
download and the state.txt file was back to garbage.

Original issue reported on code.google.com by nickw...@gmail.com on 12 Sep 2013 at 11:07

Attachments:

• report.log
• state.txt

[GoogleCodeExporter]

The attached state.txt file is in fact one of the xxx.osc.gz files. It looks 
like the change file xxx.osc.gz is copied instead of xxx.state.txt file. I will 
look at the source code of the Build 266.

As a workaround, replacing of the state.txt with the correct file downloaded 
from planet.openstreetmap.org and renamed to state.txt and restarting 
Osm2garmin should fix the problem in case the full planet download process was 
already completed, i.e. planet.osm.pbf or planet_old.osm.pbf is present in the 
working directory.

Original comment by mantl...@gmail.com on 12 Sep 2013 at 11:41

• Changed state: Started

[GoogleCodeExporter]

Original comment by mantl...@gmail.com on 12 Sep 2013 at 11:41

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This issue was updated by revision r267.

Fixed problem with incorrect state.txt download URL.

Original comment by mantl...@gmail.com on 5 Oct 2013 at 2:50

[GoogleCodeExporter]

Original comment by mantl...@gmail.com on 5 Oct 2013 at 3:07

• Changed state: Fixed