In the situation a motorway splits in two motorways (a socalled Y-branch)
I used the following line in my style to make sure the destination:ref and
the destination were displayed in my Garmin:
highway=motorway & destination:ref=* {name
'${destination:ref|highway-symbol:hbox} ${name}' |
'${destin
Hi Johan,
please check
http://www.mkgmap.org.uk/news/2013/12/22/more-flexibility-in-style-files-style
Does that help?
Gerd
Date: Sun, 9 Feb 2014 12:29:49 +0100
From: osm...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Y-branches on motorways
In the situation a motorway sp
Hi
On 08/02/14 13:44, Paulo Carvalho wrote:
The attached OSM file is what I'm using in my tests. I'm now able to
compile the map with the house numbers ok. But there is a problem
(bug?). Only a street called "Rua Armando Santos" has street numbers.
Thanks for the good example.
It seems
On 09/02/14 13:55, Steve Ratcliffe wrote:
I would not normally suggest changing the data, but when viewed with
the background imagery the points don't look to be on opposite sides
of the road, so it would perhaps be appropriate in this case.
Just to follow up, I looked in OSM and see that a lot
Lambertus,
Is the latest bounds file correct?
It is much smaller (72 Mb) than the previous ones (412 Mb)
> On 04-02-14 18:55, Patrik Brunner wrote:
>
>
> ok, thanks sorry to be a pain... ;-)
>
>
> On 04.02.2014 18:52, Lambertus wrote:
>
>
>
> Yes something went wrong ... I tried to op
2014-02-07 0:25 GMT+01:00 Steve Ratcliffe :
Thanks for reporting this. I've looked into it and it is not as simple
> as I previously thought. The names need to be sorted and this is
> happening with the original name and not the transliterated name. So
> the names end up being completely mis-sor
Thanks, Steve. I just wanted to make sure mkgmap would find the numbers by
keeping them as close as possible. I'll follow your advice to take the
numbers a few meters apart, just like they are the real world. If you're
using 32-bit floats for coordinates then we indeed have to take them apart.
Hi Paulo,
FYI:
Garmin format uses a grid with 24 bits. That means ~ 4km / 2^24 =>
~2.38 m
is the highest possible resolution at the equator. OSM precision is a few
cm.
Gerd
Paulo Carvalho wrote
> Thanks, Steve. I just wanted to make sure mkgmap would find the numbers
> by
> keeping them
I just wanted to make sure mkgmap would find the numbers by keeping them
as close as possible.
Hi Paulo,
mkgmap finds all nodes with a distance up to 150m from the street. So
there is no problem if you place them some meters away :-)
Have fun!
WanMil
_
Ok, many thanks! I adjusted the numbers so they are 5-7m away from the
streets centerlines.
2014-02-09 18:06 GMT-02:00 WanMil :
> I just wanted to make sure mkgmap would find the numbers by keeping them
>> as close as possible.
>>
>
> Hi Paulo,
>
> mkgmap finds all nodes with a distance up to 1
I dont know if this is a bug or a setting that I haven't used correctly,
but if I use --transparent in combination with some lines that are also present
in the overview map levels,
they are visible at lower zoom too:
https://www.dropbox.com/s/5eg4470narcbm70/transparent.jpg
The thinner lines need
11 matches
Mail list logo
