On Mon, Jan 25, 2010 at 09:39:56PM +, Adrian wrote:
I don't think these warnings are bogus. Mkgmap definitely has problems
with multipolygons. The Languedoc-Roussillon extract (southern France)
from Geofabrik provokes about a hundred of these warnings. But I believe
that the intersected
Hi WanMil,
thank you for having a look.
On Tue, Jan 26, 2010 at 07:05:39PM +0100, WanMil wrote:
On Mon, Jan 25, 2010 at 09:39:56PM +, Adrian wrote:
I don't think these warnings are bogus. Mkgmap definitely has problems
with multipolygons. The Languedoc-Roussillon extract (southern
I don't think these warnings are bogus. Mkgmap definitely has problems
with multipolygons. The Languedoc-Roussillon extract (southern France)
from Geofabrik provokes about a hundred of these warnings. But I believe
that the intersected ways are being generated by mkgmap and that the OSM
data is
Hi Adrian,
I don't think these warnings are bogus. Mkgmap definitely has problems
with multipolygons. The Languedoc-Roussillon extract (southern France)
from Geofabrik provokes about a hundred of these warnings. But I believe
that the intersected ways are being generated by mkgmap and that
Am 25.01.2010 23:03, schrieb WanMil:
Hi Adrian,
I don't think these warnings are bogus. Mkgmap definitely has problems
with multipolygons. The Languedoc-Roussillon extract (southern France)
from Geofabrik provokes about a hundred of these warnings. But I believe
that the intersected ways
The new MP code has a problem with inner polygons that touch the outer.
What you say makes me think that whenever the splitter splits an inner
polygon it's going to cause trouble because it splits outers/inners
along the same line so they will always intersect then.
There is more to it than
WanMil,
Adrian: I want to check the tile from Lambertus. Can you give the
download link? I haven't found it.
http://planetosm.oxilion.nl/~lambertus/garmin/routable/20-01-2010/63240406.img
To find it, visit http://garmin.na1400.info/routable.php, zoom in to
the south of France, click on the
It is the point of view to say the OSM data is OK.
I ran r1475, r1502 and r1507 against exactly the same input files
(the Geofabrik extract split into two tiles by splitter). r1475
produced no error messages at all. I admit I don't know whether
r1475 might have done less error checking, but
On 25.01.2010 23:03, WanMil wrote:
It is the point of view to say the OSM data is OK. The Geofabrik dumps
contain incomplete ways and incomplete relations. To get a 100% correct
handling of multipolygons if is required to have complete data or to get
the shape of the OSM dump.
The
Hi Marko
I still can't view the gmapsupp.img because of a NullPointerException:
I can only think that this is due to an img that has failed to build
properly. I saw one case of this was using the command line option
--keep-going, are you using that? If so remove it and see if the error
is
On Tue, Jan 19, 2010 at 10:20:38AM +, Steve Ratcliffe wrote:
Hi Marko
I still can't view the gmapsupp.img because of a NullPointerException:
I can only think that this is due to an img that has failed to build
properly. I saw one case of this was using the command line option
On Tue, Jan 19, 2010 at 12:42:46PM +0200, Marko Mäkelä wrote:
The r1501 fixed it. But why was no TRE section generated by mkgmap
in the first place? Will it do any harm if it is missing? Or was the
TRE section generated in the wrong place? I am using --max-jobs on a
dual core processor. I
I am attempting to reproduce from your script.
OK I have reproduced the problem. It appears that the directory withing
the IMG is empty and yet the file is quite large, so something is very
wrong.
$ jv test.ListFile 63240001.img
Block size: 512
. 0
I don't see the problem
Hi Steve,
I am attempting to reproduce from your script.
OK I have reproduced the problem. It appears that the directory withing
the IMG is empty and yet the file is quite large, so something is very
wrong.
Can you add some diagnostics for this case? Preferrably near the place
where
Hi Marko
OK the directory overflows for that file because there are more than
64k blocks. You can either reduce the size of the file or use the
--block-size=1024 parameter to make the blocks bigger and so reduce the
number.
The bug is that it doesn't trigger the error message when the
I am getting these for yesterday's finland.osm.bz2 and mkgmap r1499.
I suspect that these are coming from the branches/mp merge:
SEVERE (MultiPolygonRelation): Multipolygon
http://www.openstreetmap.org/browse/relation/5828 contains intersected ways
This relation or the containing points have
16 matches
Mail list logo
