Hi Andrzej
> I don't understand this. If you have no --levels option then the
> default should be used, which has a maximum of 4.
Looks like there is no defaults now, or maybe only level 0 gets a
default resolution.
There is a default for levels:
DEFAULT_LEVELS = "0:24, 1:22, 2:20, 3:18
The only prob I have with the codes is saying below 17 is to small to split but
not saying this on all maos though
StephenÂ
Original message
From: Andrzej Popowski
Date:20/05/2015 8:45 AM (GMT+10:00)
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] levels in
Hi Steve,
> I don't understand this. If you have no --levels option then the
> default should be used, which has a maximum of 4.
Looks like there is no defaults now, or maybe only level 0 gets a
default resolution.
> What do you think that the message text should be?
Maybe something like "'
Hi Andrzej
If I put no "level=" or no "overview-level=" in command line option nor
in style I get following error:
Error in style: Error: Level number too large, max=1
Could not open style
Number of ExitExceptions: 1
I don't understand this. If you have no --levels option then the
default s
Hi Steve,
I have tested your precompiled jar, levels seems to work correctly.
If I put no "level=" or no "overview-level=" in command line option nor
in style I get following error:
Error in style: Error: Level number too large, max=1
Could not open style
Number of ExitExceptions: 1
I think
... 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 (re
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:
http://files.mkgmap.org.uk/download/267/m
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,
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 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, b
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
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 wrote:
> Hi,
>
> I have defined a rule in style like this:
> highway=path [0x16 road_cl
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
13 matches
Mail list logo
