Hi Gerd
Sorry for the late answer, i'm have to spent some time for my job ;-)
You're right, there's really no inc/access, it looks like an error, but i can
find every address on a polygon, that i have searched for, tested with my O650
On the other side, there are only six messages, 'houses not
Hi all,
I just noticed that mkgmap treats POI with
0x2000 = type 0x2800
special.
It looks for the tags
exit:to=* and exit:facility=* to add extra information to
the POI.
This info is shown when you click on an exit in Basecamp,
it shows the fields Name, Description, and Overnight Parking.
Hi Gerd
you're right, it should be inc/address.
After adding this to inc/polygons i didn't get any error messages for DACH.
IMHO you can merge housenumbers2 to trunk
Bernd
Am Dienstag, 19. Mai 2015, 10:21:12 schrieb Gerd Petermann:
Hi Bernd,
thanks for testing.
Just to make sure: it's
Hi Bernd,
thanks for testing.
Just to make sure: it's inc/address I was looking for, not inc/access.
The effect of the missing include is that
mkgmap:city etc. are not filled for the (house) polygon.
In that case the value from the road is taken, so you
will only see a problem when you search
Hi,
On Tue, May 19, Gerd Petermann wrote:
Hi all,
I just noticed that mkgmap treats POI with
0x2000 = type 0x2800
special.
It looks for the tags
exit:to=* and exit:facility=* to add extra information to
the POI.
This info is shown when you click on an exit in Basecamp,
it shows
Hi Dave,
the patch changes the rules in the default style so that exist on primary roads
are taken
into account.
More important for your test case: It also changes the code so that
exists on motorway_links to other motorway_links are taken into account.
The old code only looked at exits on
When you say you didn't change the echotags code, did you rewrite the style
rule? If you did that I'm embarrassed to admit I am unable to see the
difference.
AFAIK I'm using the exact same style file for both runs, but the run with
the older executables produced no output. I replaced that jar
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 po...@poczta.onet.pl
Date:20/05/2015 8:45 AM (GMT+10:00)
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re:
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
Hi Dave,
I am not sure if you understand that echotags always worked.
The problem is/was that the rule was not executed because
the expression evaluated to false.
In other words, I did not change the echotags code,
I changed the code so that it is more likely that the
term mkgmap:exit_hint=true
11 matches
Mail list logo
