oops, the proposed rule was missing a plus sign:
# make sure that mkgmap:road-speed is also set when mkgmap:road-speed-max (or
-min) is set
(mkgmap:road-speed-max=* | mkgmap:road-speed-min=*) mkgmap:road-speed!=* {
add mkgmap:road-speed=+0}
Gerd
From: gpetermann_muenc...@hotmail.com
To:
Hi,
I think the java code works as documented in the style manual.
A possible solution in the style:
Add the following two lines at the end of inc/roadspeed:
# make sure that mkgmap:road-speed is also set when mkgmap:road-speed-max is
set
mkgmap:road-speed-max=* mkgmap:road-speed!=* { add
Hi Gerd,
The tag mkgmap:road-speed-max=* is only evaluated
by mkgmap when the tag mkgmap:road-speed=*.
If mkgmap:road-speed is not set, the value in
mkgmap:road-speed-max is completely ignored.
My early proposition for limiting speed looked like this:
... { set mkgmap:road-speed='-0'; set
Hi Andrjez,
I've tested with the attached patch and it seems to work fine.
I think the advantage of my version is that it doesn't override
an existing mkgmap:road-speed=* tag.
Gerd
To: mkgmap-dev@lists.mkgmap.org.uk
From: po...@poczta.onet.pl
Date: Fri, 14 Aug 2015 10:30:25 +0200
I'm having a weird routing problem!
I'm using CreateIMG (which uses mkgmap to do the work) to create a Garmin
compatible map of the UK. I've installed this map into BaseCamp, and I'm
trying to create a route.
There's a point on a local minor road which BaseCamp refuses to route
through
Am 12.08.2015 um 10:46 schrieb Gerd Petermann:
I'd like to remove the code and the option, I think it produces more or less
unpredictable results
and I found no problems with maps created without the option.
ok for me.
Chris
___
mkgmap-dev
Hi Bernd,
Maybe if i try to '+0'
My guess is that simple +0 is a number while '+0' is a string, and
probably mkgmap:road-speed expect a string. So I suggest to try:
mkgmap:road-speed='+0'
--
Best regards,
Andrzej
___
mkgmap-dev mailing list
Hi Gerd
When i test this new rule, i got this, i use the default inc/roadspeed
java.lang.NumberFormatException: Zero length string
at java.lang.Integer.decode(Integer.java:1162)
at java.lang.Byte.decode(Byte.java:277)
at
There is something wrong with 'add mkgmap:road-speed=+0'.
Maybe if i try to '+0', when (mkgmap:road-speed-max=* | mkgmap:road-speed-
min=*) = '0'?
Bernd
Am Freitag, 14. August 2015, 09:44:10 schrieb Gerd Petermann:
oops, the proposed rule was missing a plus sign:
# make sure that
Hi Gerd,
I think the advantage of my version is that it doesn't override
an existing mkgmap:road-speed=* tag.
Yes, I have noticed. Maybe that kind of action would be simpler:
... { add mkgmap:road-speed='-0'; set mkgmap:road-speed-max = 2 }
I think that making mkgmap:road-speed-max
Hi Andrzej,
I agree that the relation between tag mkgmap:road-speed='-0'
and mkgmap:road-speed-max is hard to understand.
I see no good reason for keeping the java code.
Gerd
popej wrote
Hi Gerd,
I think the advantage of my version is that it doesn't override
an existing
I changed the last to this two lines
# make sure that mkgmap:road-speed is also set when mkgmap:road-speed-max is
set
highway=* mkgmap:road-speed-max=* mkgmap:road-speed!=* { add mkgmap:road-
speed = '${mkgmap:road-speed-max}' }
highway=* mkgmap:road-speed-min=* mkgmap:road-speed!=* { add
in the lines file is there a way to have primary, seconday, teritary and
living streets with side street displayed .
so that in the Header box more indication is given , so far only highway =
motor way is is hboxed
any iideas ?
Stephen
___
13 matches
Mail list logo