search

mantlik / osm2garmin

Convert OpenStreetMap data to Garmin-compatible format.
http://osm2garmin.mantlik.org/
GNU General Public License v2.0
9 stars 1 forks source link

Problem while downloading South America SRTM #110

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi. I'm having problems with this program. Everything goes just fine, until the 
program starts downloading the South America S17 W69 SRTM. It just stays there, 
doesn't show any error message, and I checked the url of that file and I can 
download it manually without any trouble. I tried deleting that file (I thought 
it was broken) and started the program again, but it always stops there. I 
attach the logs here. Thanks.

Original issue reported on code.google.com by raulgarf...@gmail.com on 2 Jul 2013 at 5:02

Attachments:

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r263.

Broken ZIP file is deleted and re-downloaded when zip item does not exist. 
Warning message is logged.

Original comment by mantl...@gmail.com on 2 Jul 2013 at 9:35

GoogleCodeExporter commented 9 years ago 
Dear user, updated version of the software Build 263 is available in the 
Downloads section. Please uninstall your version and install the updated 
version. This will not affect your data.

The updated version should delete broken download of the SRTM file and download 
the file again. In case of failure it should provide more detailed report of 
the cause of the problem.

If the fix will not help, please attach new versions of both log files here.

Thank you for your patience and co-operation.

Original comment by mantl...@gmail.com on 2 Jul 2013 at 10:17

GoogleCodeExporter commented 9 years ago 
Thanks again. With this version of the program, now it shows the same message 
than the one found on the messages.log file I attached before (at the moment it 
has been displayed 6 times, so far always when downloading South America SRTM 
data), but at least it continues. I'll let it finish to see how it goes, but I 
don't know what those messages mean. I assume that the only difference I'm 
having with this version is that it doesn't get stuck at one file, but the 
error still appears to be present.

Thanks

BTW, the message I'm refering to is the following:

SEVERE (Srtm): 
java.lang.NullPointerException: entry
    at java.util.zip.ZipFile.getInputStream(Unknown Source)
    at org.mantlik.osm2garmin.srtm2osm.Srtm.load(Srtm.java:130)
    at org.mantlik.osm2garmin.srtm2osm.Srtm.get(Srtm.java:310)
    at org.mantlik.osm2garmin.Srtm2Osm.run(Srtm2Osm.java:88)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1452)
    at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2032)

Original comment by raulgarf...@gmail.com on 4 Jul 2013 at 5:59

GoogleCodeExporter commented 9 years ago 
Dear user, thank you for co-operation. 

The intention of the fix r263 was to work around the problem with unreadable 
SRTM zip file. The exception thrown now refers to an unreadable zip after 
download. The invalid file is skipped and processing continues. Possibly, I 
could modify the above message to provide the name of the invalid file.

Original comment by mantl...@gmail.com on 4 Jul 2013 at 7:50

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r264.

Generated verbose message when SRTM entry can't be extracted from the zip file.

Original comment by mantl...@gmail.com on 4 Jul 2013 at 9:01

GoogleCodeExporter commented 9 years ago 
Thanks. So far is going well with this new version (now is downloading and 
processing South Asia SRTM), but the program is having problems downloading the 
planet updates. It's stuck at 99.96%, and is showing always the same error 
messages: Piece download from webseed failed: xxxx (xxxx being 7047, 1409 and 
6259, always those three).

Original comment by raulgarf...@gmail.com on 5 Jul 2013 at 7:18

GoogleCodeExporter commented 9 years ago 
Dear user, both problem with SRTM download and Planet download could be caused 
by a hardware problem of your computer - disk, memory or processor, Internet 
connection problem or a virus infection.

Original comment by mantl...@gmail.com on 5 Jul 2013 at 8:00

GoogleCodeExporter commented 9 years ago 
I really don't think that's the cause of the problem. The computer is doing 
fine in every aspect, and I find it curious that it always fails with those 3 
download pieces only. The SRTM seems to be ok, at least I haven't seen any 
error message again. I really don't know why it can't download those files.

Original comment by raulgarf...@gmail.com on 6 Jul 2013 at 6:52

GoogleCodeExporter commented 9 years ago 
Can you, please, upload both logs with failed download? For the first view the 
problem looks very similar to the problem with SRTM. The file (piece) is 
incorrectly downloaded or stored.

Original comment by mantl...@gmail.com on 6 Jul 2013 at 8:17

GoogleCodeExporter commented 9 years ago 
Here they are. Thanks!

Original comment by raulgarf...@gmail.com on 6 Jul 2013 at 10:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Well, I gave up with that. The program doesn't have problems downloading all 
the other planet update files, but could never download those 3 pieces. So I 
checked the skip planet update box, and started again (from the start, even 
changed the dev, maps and SRTM folders), but now it's having problems while 
creating the maps. It says that australia_nz.osm.pbf (input file) doesn't exit 
or isn't readable. I looked at the folder and indeed that file doesn't exist. 
Any ideas on this? I'm pretty sure it's not a hardware problem. Thanks again!

Original comment by raulgarf...@gmail.com on 9 Jul 2013 at 5:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Dear user,

sorry for delay with reply, I was out of my computer. As I can see from your 
uploaded logs (Comment 10), your problem is not downloading of the planet file, 
but downloading of planet updates. You have mentioned it in your Comment #6, 
but I missed it - sorry. You are facing the problem described in the Issue 104. 
Please follow the procedure described in the Comment #1 of the Issue 104 to fix 
the problem.

Unfortunately, it is not possible to skip planet update until it is at least 
once successfully processed and data structures are finalized. If your working 
directory is seriously broken, the only way would be to start from scratch 
again, possibly re-using your downloaded Planet file if a new one was not 
released yet.

Original comment by mantl...@gmail.com on 9 Jul 2013 at 6:15

GoogleCodeExporter commented 9 years ago 
Issue 116 has been merged into this issue.

Original comment by mantl...@gmail.com on 6 Sep 2013 at 2:54