Oh okay, well then let's put this on the list. I know the remove-short-arcs function is not touching it, but it's 2448 that breaks it. There must be something else touched on the routing side of it. And I would say it's very likely not only happening here, but probably happening in quite a few cases - it just popped up there.
On 30.01.2013 22:19, Gerd Petermann wrote:
Hi Felix,

sorry, I have no idea what goes wrong. With r2466, the remove-short-arcs function doesn't touch the way 38693214 or 83196110.
I think this is something Steve must look at.

Gerd
P.S. I don't know why my answer to your first mail did not go to the list. This was not intended.



Date: Wed, 30 Jan 2013 17:47:44 +0100
From: extremecarver@gmail.com
To: gpetermann_muenchen@hotmail.com
Subject: Re: [mkgmap-dev] Regression: Revision 2448 breaking routing in some cases

okay great, well I think there is some routing information missing on the road. Just see what happens when you try to click on it for a route with Basecamp or Mapsource - it puts the routing node somewhere completly else (a little bit, like what happens with merge-lines, just much further away).
On 30.01.2013 17:39, Gerd Petermann wrote:
Hi Felix,

okay, I see if I can find anything special in this file. We already know that the algorithm is not 100 % correct, and I hope Steve will find a better solution,but
maybe I can improve the existing algo first.

Gerd


Date: Wed, 30 Jan 2013 17:22:30 +0100
From: extremecarver@gmail.com
To: gpetermann_muenchen@hotmail.com
Subject: Re: [mkgmap-dev] Regression: Revision 2448 breaking routing in some cases


On 30.01.2013 16:23, Gerd Petermann wrote:
Hi Felix,

I want to find the special case in this. Please provide the osm data (66570017.osm.pbf )
it's here now: http://openmtbmap.org/65250017.osm.pbf
Are you able to reproduce the problem with the default style?
No, I'm really lost on the style issue. I can cut down the style quite far, and it's still broken. But even if I change routable lines, that are created after the breaking road (further down in the lines file), it can suddenly work again.
On the other hand, there seems to be nothing special about the osm data there at all.

Gerd

> Date: Wed, 30 Jan 2013 11:46:24 +0100
> From: extremecarver@gmail.com
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: [mkgmap-dev] Regression: Revision 2448 breaking routing in some cases
>
> Well, I got notified that there is a routing problem in one of my maps,
> and after trying around a long time, I tracked it down to release 2448
> that breaks routing under certain occasions. Here is a screenshot of the
> the routing failing:
>
> http://openmtbmap.org/broken_routing.jpg
>
> So for a very short distance, the routing will actually route over the
> broken road (the section where the route is missing).
> However for longer sections on that road, or route that actually has a
> routepoint manually set on it, Mapsource/Basecamp/GPS will fail to
> calculate a route at all. (e.g. if you try to route from the North point
> of the route in the picture, South to the Bergkirchen place POI/node).
>
>
> It is dependant on the the style - but I played with deleting lots of
> stuff from the style, and it seems to be quite random.
> So here are the downloads (all .exe are lzma packed, just unpack them if
> not on windows):
>
> http://openmtbmap.org/velonordrhein-westfalen_working_2447.exe
> http://openmtbmap.org/velonordrhein-westfalen_broken_2448.exe
>
> Search for Bergkirchen, it is in the tile 66570017
>
>
> Maps are compiled with:
> c:\OpenMTBMap\maps>start /low /b /wait java -jar -Xms4000M -Xmx10400M
> c:\openmtbmap\mkgmap.jar --max-jobs=8 --generate-sea --latin1
> --precomp-sea=c:\openmtbmap\maps\sea
> "--style-file=c:\openmtbmap\velomap_style" --nsis --index --transparent
> --adjust-turn-headings --add-pois-to-areas --ignore-maxspeeds
> --reduce-point-density=3 --x-reduce-point-density-polygon=6
> --link-pois-to-ways --ignore-turn-restrictions --remove-short-arcs=5.4
> --min-size-polygon=18 --description=velomap_dnw --show-profiles=1
> --location-autofill=bounds,is_in,nearest
> --bounds=c:\openmtbmap\maps\bounds --route --country-abbr=dnw
> --country-name=nordrhein-westfalen --mapname=66570000 --family-id=6657
> --product-id=1 --series-name=velomap_nordrhein-westfalen_30.01.2013
> --family-name=velomap_dnw_30.01.2013 --tdbfile
> --overview-mapname=mapsetc --keep-going
> --area-name="nordrhein-westfalen_30.01.2013_velomap.org" -c
> c:\openmtbmap\maps\template.nordrhein-westfalen 7*.img 1>NUL
>
> --remove-short-arcs == resulting road will be broken
> --remove-short-arcs=5.4 == resulting road will be broken
> without remove-short-arcs == resulting road will be broken
>
> So it doesn't directly have to do with the --remove-short-arcs function.
>
>
> (also Compiled with --remove-short-arcs=5.4 )
> http://openmtbmap.org/velonordrhein-westfalen_broken_2466.exe
>
> then Uncommented the following lines in my style-file, which shouldn't
> affect routing at all, but it does as the mistake is gone:
> # power=line [0x29 resolution 22 continue]
> # power=minor_line | powerline=yes | power_line=yes | powerline=true |
> power_line=true [0x29 resolution 24 continue]
> http://openmtbmap.org/velonordrhein-westfalen_nopower_2466.exe
>
> However I can also leave that line in the style-file, and delete some
> other lines, and routing will work again. There seems to be no clear
> pattern (except that the bug go introduced with rev 2448). I use the
> same line in my openmtbmap, and there the routing error doesn't happen.
>
>
> --
> keep on biking and discovering new trails
>
> Felix
> openmtbmap.org & www.velomap.org
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- 
keep on biking and discovering new trails

Felix
openmtbmap.org & www.velomap.org

-- 
keep on biking and discovering new trails

Felix
openmtbmap.org & www.velomap.org

-- 
keep on biking and discovering new trails

Felix
openmtbmap.org & www.velomap.org