They are processed correctly - but there is no support for level 0 being
different to 24 yet (at least if you want to have things like autorouting
or address search).
On 18 May 2015 at 13:58, Andrzej Popowski po...@poczta.onet.pl wrote:
Hi,
I have defined a rule in style like this:
Hi all,
attached patch changes mkgmap so that
a) the process-exits and process-destination options are also checking
highway=primary roads and also those cases were
a link divides into two or more further link roads.
b) the exit_to tag on a highway=motorway_junction node is ignored
when the
Hi,
I have defined a rule in style like this:
highway=path [0x16 road_class=0 road_speed=0 level 0]
When I compile map with --levels=0:24, then I get paths correctly.
When I use option --levels=0:23, then paths are missing.
I would expect paths on level 0 regardless of resolution.
--
Best
On 18/05/15 12:58, Andrzej Popowski wrote:
Hi,
I have defined a rule in style like this:
highway=path [0x16 road_class=0 road_speed=0 level 0]
When I compile map with --levels=0:24, then I get paths correctly.
When I use option --levels=0:23, then paths are missing.
I would expect paths on
Hi all,
As regards Felix's comment, even if the lack of routing and index is
still true (but I thought that Gerd had fixed that?), the line should
still be present but it isn't. Also removing the road_speed/class
parameters doesn't affect the outcome.
I once thought that I fixed it, but
Version mkgmap-r3598 was committed by gerd on Mon, 18 May 2015
fix possible NPE when way has destination:forward or destination:backward tag
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi,
I think problem is with initial conversion levels - resolution.
I thought, that levels in style are depreciated, but Steve's suggestion
works, I get correct results when using proper levels inside options file.
If I delete levels form style, then command line values still aren't
used.
Hi Bernd,
got no feedback yet. Does it mean you found no errors?
I ask because I still don't see inc/address in your polygons file,
but I see the line
addr:housenumber=* {set mkgmap:execute_finalize_rules=true}
Gerd
Bernd Weigelt wrote
Hi Gerd
thank you for the good work
i'll test
Hi
I've only taken a quick look so far, but it seems that the command line option
is applied too late and the built in default is used initially to convert the
level to resolution. So level 0 is converted to resolution 24 and this is then
(correctly) omitted from a resolution 23 level.
I did
Hi
initially to convert the level to resolution. So level 0 is
converted to resolution 24 and this is then (correctly) omitted from
a resolution 23 level.
Here is a patch to have the --levels option work in this case.
A ready built jar file is here:
... and here is the patch
Index: src/uk/me/parabola/mkgmap/osmstyle/StyleImpl.java
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
+UTF-8
===
--- src/uk/me/parabola/mkgmap/osmstyle/StyleImpl.java
Hi Uli,
thanks for reporting. This is fixed with r3598.
Gerd
Date: Sun, 17 May 2015 22:29:34 -0700
From: ulib...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Commit: r3597: corrections for process-exits option
With this latest version i get the following
Hi Gerd,
just to confirm:
Version 3598 works correctly on the same dataset.
Thank you for this really quick response! :)
Best regards, Uli
--
View this message in context:
http://gis.19327.n5.nabble.com/Commit-r3597-corrections-for-process-exits-option-tp5844899p5845001.html
Sent from the
13 matches
Mail list logo
