In german city Hameln turn-restrictions are used like hell, but they don't seem to work. <http://www.bilder-space.de/show.php?file=02.12Ft6hRZHIiEanBbI.gif> On the left side the only_straight_on restriction is not applied, on the right side there is a "funny" routing. MapSource-Setting is Car/Shortest from A to B. Just tried the latest (1413) with default style, routing is the same like in my map show on the picture. This is the area: <http://www.openstreetmap.org/?lat=52.10494&lon=9.3719&zoom=16> Chris
Hi Chris,
In german city Hameln turn-restrictions are used like hell, but they don't seem to work.
<http://www.bilder-space.de/show.php?file=02.12Ft6hRZHIiEanBbI.gif>
On the left side the only_straight_on restriction is not applied, on the right side there is a "funny" routing.
I looked at that area. The right side doesn't go North on Basbergerstrasse because it's oneway at the bottom. As for the problem on the left, I do not know why the restriction failed. I am looking into that. Cheers, Mark
<http://www.bilder-space.de/show.php?file=02.12Ft6hRZHIiEanBbI.gif>
On the left side the only_straight_on restriction is not applied, on the right side there is a "funny" routing.
The routing on the right side is caused by a wrong 'oneway=yes' on way #24229789. So remains the question why <http://www.openstreetmap.org/browse/relation/154097> is not working. Chris
Chris-Hein Lunkhusen escribió:
In german city Hameln turn-restrictions are used like hell, but they don't seem to work.
<http://www.bilder-space.de/show.php?file=02.12Ft6hRZHIiEanBbI.gif>
On the left side the only_straight_on restriction is not applied, on the right side there is a "funny" routing.
There's a oneway portion of Basbergstraße street causing the detour in right side of your picture.
MapSource-Setting is Car/Shortest from A to B.
Just tried the latest (1413) with default style, routing is the same like in my map show on the picture.
This is the area:
<http://www.openstreetmap.org/?lat=52.10494&lon=9.3719&zoom=16>
Chris
Mark Burton schrieb:
In german city Hameln turn-restrictions are used like hell, but they don't seem to work.
Err, yes. I broke them. Fixed now in 1414.
Hi Mark, don't works for me. Still MapSource routes me directly to Koppenstraße or Hunoldstraße coming from B1 left. v1414 (latest) my command line: java -Xmx1200m -ea -esa -jar ..\mkgmap\mkgmap.jar --latin1 --description=test --country-name=DE --country-abbr=DE --family-id=5 --product-id=55 --series-name=test --family-name=test --area-name=DE --mapname=63250001 --remove-short-arcs --route --net --gmapsupp --tdbfile *.osm Chris
Hi Chris,
don't works for me.
Still MapSource routes me directly to Koppenstraße or Hunoldstraße coming from B1 left.
v1414 (latest)
my command line:
java -Xmx1200m -ea -esa -jar ..\mkgmap\mkgmap.jar --latin1 --description=test --country-name=DE --country-abbr=DE --family-id=5 --product-id=55 --series-name=test --family-name=test --area-name=DE --mapname=63250001 --remove-short-arcs --route --net --gmapsupp --tdbfile *.osm
Hmm, well please see attached - that's what I get. Before 1414, it would turn left at the TR, now it doesn't. If I pick a destination point further to the N it chooses a different route but still obeys the TR. Cheers, Mark
Mark Burton schrieb:
don't works for me.
Still MapSource routes me directly to Koppenstraße or Hunoldstraße coming from B1 left.
v1414 (latest)
my command line:
java -Xmx1200m -ea -esa -jar ..\mkgmap\mkgmap.jar --latin1 --description=test --country-name=DE --country-abbr=DE --family-id=5 --product-id=55 --series-name=test --family-name=test --area-name=DE --mapname=63250001 --remove-short-arcs --route --net --gmapsupp --tdbfile *.osm
Hmm, well please see attached - that's what I get. Before 1414, it would turn left at the TR, now it doesn't. If I pick a destination point further to the N it chooses a different route but still obeys the TR.
Mark, very mysterious indeed. I now deactivated all other maps in MS-Registry (6.13.7), rebuild mkgmap.jar freshly from trunk, but get again the wrong routing. Could you give me your command line and send me your mkgmap.jar? If the java version matters, this is mine (WinXP): java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing) Thank you in advance Chris
very mysterious indeed.
I now deactivated all other maps in MS-Registry (6.13.7), rebuild mkgmap.jar freshly from trunk, but get again the wrong routing.
Could you give me your command line and send me your mkgmap.jar?
Thank you Mark for sending your mkgmap.jar and your command line. And now the reason for my map not using the TRs : the missing "--ignore-osm-bounds" ! So, if I understand correctly : when compiling data that comes out of splitter --ignore-osm-bounds should not be used, but when compiling small areas (from XAPI or stored from JOSM), --ignore-osm-bounds should be used ? Chris
Hi Chris,
And now the reason for my map not using the TRs :
the missing "--ignore-osm-bounds" !
So, if I understand correctly :
when compiling data that comes out of splitter --ignore-osm-bounds should not be used, but when compiling small areas (from XAPI or stored from JOSM), --ignore-osm-bounds should be used ?
Yes, don't ignore the bounds when the file is produced by the splitter but in most other cases you probably do want to ignore the bounds. For example, if you are using josm and you download more than 1 region and save the multiple regions in a single file, that file will contain multiple bounds elements, 1 for each of the downloads. If you don't tell mkgmap to ignore the bounds elements, it just uses one of them (I think) and so all of the data that falls outside of that 1 bounded area will get ignored. Cheers, Mark
participants (3)
-
Carlos Dávila -
Chris-Hein Lunkhusen -
Mark Burton