Closed GoogleCodeExporter closed 9 years ago
It seems that the OSMImporter plugin hangs / fails when asked for data from the
MapnikRenderer plugin. Could you make the .osm file you used available to me?
Does the program crash, stop the preprocessing ( displaying a red 'X' next to
the renderer plugin ) or just hang?
If the preprocessing just stops without an error message, you have most likely
a .osm file containing no bounding box. You could try r222 to check for this as
I added some missing debug messages for failed file open operations.
If you are missing the bounding box: Is it common for some .osm files to
contain no bounding box? If this is the case I could switch to computing one
based on the nodes in the .osm file.
Original comment by veaac.fd...@gmail.com
on 2 Sep 2010 at 9:16
Hello Christian:
The *.osm XML data file is 4.3MB -- quiet a large file. I downloaded this data
from the OpenStreetMap website -- please see details below.
Step 1: Using Firefox enter this URL.
http://www.openstreetmap.org/?lat=25.04&lon=-77.365&zoom=11&layers=M
Step 2: Then click the Export tab.
Step 3: For format to export select "OpenStreetMap XML Data".
Step 4: Download and save the "nassau_new_providence_bahamas_map.osm" to your
local storage (HDD).
Attached are two screen shots with information that you may find useful.
In the mean time I will try MoNav svn r222.
Thank you.
P.E.A.
Original comment by peteadde...@gmail.com
on 2 Sep 2010 at 9:58
Attachments:
I got it, it was the missing bounding box item:
The downloadable .osm extract have an entry:
<bound box="53.73236,-5.43455,54.67060,-3.68872"
origin="http://www.openstreetmap.org/api/0.6"/>
While the exported osm file has:
<bounds minlat="24.8140000" minlon="-77.6170000" maxlat="25.2660000" maxlon="-77.1130000"/>
I do not know whether this discrepancy is intentional no standard exists for
the bounding box, but I added the "bounds" variant to the OSMImporter in r223
Could you please try whether this fixes the bug?
Original comment by veaac.fd...@gmail.com
on 2 Sep 2010 at 10:25
Hello:
Christian your "missing bounding box" remedy in MoNav r223 appears to have
solved the problem. Precessing completed successfully.
Original comment by peteadde...@gmail.com
on 2 Sep 2010 at 11:16
Attachments:
Original comment by veaac.fd...@gmail.com
on 2 Sep 2010 at 11:16
Original issue reported on code.google.com by
peteadde...@gmail.com
on 2 Sep 2010 at 8:50