[mkgmap-dev] SEVERE internal error in restriction relation

Fri Apr 10 10:51:07 BST 2015

Hi Thorsten,

yes, a very special case. With r3530 I've changed the code to handle that.
I hope it doesn't introduce new problems.

It seems the restriction itself has no effect on routing,
Garmin doesn't select this way.

BTW: With r3528 the problem appears with 
java -jar mkgmap.jar --route 71200051.osm.pbf
and disappears with
java -jar mkgmap.jar --route --preserve-element-order 71200051.osm.pbf

The random order just avoids the problem situation, it could as well 
be vice versa.

Gerd

> Date: Thu, 9 Apr 2015 13:03:21 +0200
> From: kukuk at suse.de
> To: mkgmap-dev at lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] SEVERE internal error in restriction relation
> 
> 
> Hi,
> 
> On Wed, Apr 08, Gerd Petermann wrote:
> 
> > Hi Thorsten,
> > 
> > with trunk version r3528 I've changed the code to report the restriction relation, but
> > I was not able to reproduce the problem with the input file.
> > 
> > Did you use your style files dated 2015-02-19, 10:27 ?
> 
> Something newer, I have uploaded that now, but the changes there shouldn't
> have any impact on this.
> 
> I still see the error:
> 2015/04/09 11:59:51 SEVERE (RestrictionRelation): 71200051.osm.pbf: Turn restriction (no_right_turn) http://www.openstreetmap.org/relation/4769034 (at http://www.openstreetmap.org/?mlat=53.084337&mlon=8.851024&zoom=17) internal error: number of via points and via ways no longer fits
> 
> And yes, this restriction is really strange...
> 
>   Thorsten
> 
> > Gerd
> > 
> > > Date: Wed, 8 Apr 2015 11:14:15 +0200
> > > From: kukuk at suse.de
> > > To: mkgmap-dev at lists.mkgmap.org.uk
> > > Subject: [mkgmap-dev] SEVERE internal error in restriction relation
> > > 
> > > 
> > > Hi,
> > > 
> > > Today I found in the log files this severe error message:
> > > 2015/04/08 03:16:45 SEVERE (RestrictionRelation): 71200051.osm.pbf: internal error: number of via points and via ways no longer fits
> > > 
> > > osm.thkukuk.de/tmp/71200051.osm.pbf is the input file.
> > > 
> > > I don't know, but at least for me it would be helpful to have a
> > > reference, at least the coordinates, where this happens, so that
> > > I could check if the OSM data is buggy or what else the reason could
> > > be.
> > > 
> > >   Thorsten
> > > -- 
> > > Thorsten Kukuk, Senior Architect SLES & Common Code Base
> > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> > > GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
> > > _______________________________________________
> > > mkgmap-dev mailing list
> > > mkgmap-dev at lists.mkgmap.org.uk
> > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> >  		 	   		  
> 
> > _______________________________________________
> > mkgmap-dev mailing list
> > mkgmap-dev at lists.mkgmap.org.uk
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> 
> -- 
> Thorsten Kukuk, Senior Architect SLES & Common Code Base
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150410/0e860374/attachment.html>