Check contours for completness

[GoogleCodeExporter]

In case of problems to access a particular SRTM3 contours file, generated 
contours archive is incomplete forever.

Because SRTM3 download failures should have random character and are rare under 
normal circumstances, when processing is running for the first time, temporal 
contours files can be generated. On the second run, final contours are 
generated temporal files sizes are compared to the final ones. If they are the 
same, final file is saved and contours generation is over. If sizes differ, 
bigger file is saved as new temporal contours file and the process will repeat 
on the next run.

Original issue reported on code.google.com by mantl...@gmail.com on 31 Jan 2012 at 1:57

[GoogleCodeExporter]

This issue was updated by revision r119.

Contours are checked for completness as described.

Original comment by mantl...@gmail.com on 31 Jan 2012 at 2:02

[GoogleCodeExporter]

This issue was updated by revision r123.

Uncompressed sizes of contours archives are compared. Compressed sizes can 
differ even for identical files because of timestamps difference.

Original comment by mantl...@gmail.com on 1 Feb 2012 at 10:39

[GoogleCodeExporter]

This issue was updated by revision r124.

Fixed problem with uncompressed lengths. Stats have to be explored from 
ZipFile, not ZipInputStream.

Original comment by mantl...@gmail.com on 1 Feb 2012 at 4:17

[GoogleCodeExporter]

This issue was updated by revision r127.

Mark contours file for re-processing only if not all SRTM data are available.

Original comment by mantl...@gmail.com on 8 Feb 2012 at 2:36

[GoogleCodeExporter]

Original comment by mantl...@gmail.com on 8 Feb 2012 at 2:44

• Changed state: Started

[GoogleCodeExporter]

Original comment by mantl...@gmail.com on 12 Feb 2012 at 11:20

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by mantl...@gmail.com on 12 Feb 2012 at 11:21

• Changed state: Verified