Hi Gerd
I thought this case would never happen. I think I know how to make it
work. I'll download .de from geofabik and try my std split and params
to see if I can reproduce. If not I'll ask you for input files/split
params/cfg...
Ticker
On Thu, 2017-01-12 at 23:10 -0700, Gerd Petermann wrote:
>
Hi Ticker,
here is my areas.list for splitter (use with --split-file=areas.list)
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Freitag, 13. Januar 2017 09:54:01
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] new branch split
Hi Greg,
If you want your roads with different thickness depending on zoom, then
simply do not give any graphics in TYP for roads. Additional bonus is
that GPS (at least nuvi) will draw arrows on on-way roads. This probably
won't work for other lines like rivers.
About combining, you have mu
El 10/01/17 a las 08:34, Gerd Petermann escribió:
Hi all,
while testing roundabouts4.patch I found this place:
https://www.openstreetmap.org/relation/1518208
I think the relation is completely wrong, but it also causes some missleading
warning messages
because the mp-code creates some addition
Hi Greg,
in case of routable lines, make sure that 23 (in the example below) is a
routable line.
20-22 can be any non routable line (I am using 0x1 and above for that).
e.g.
highway=motorway & network=e-road [0x10101 resolution 14-16 continue
with_actions]
highway=motorway
El 11/01/17 a las 21:12, Andrzej Popowski escribió:
Hi,
there is command line version of GMapTool too. You can run it in a
batch like this:
>gmt.exe -w -c 1.02 gmapsupp.img
Map version is in bytes 8-9 of the header. Support in mkgmap could be
added as easy as option --hide-gmapsupp-on-pc. On
If there are too many address tags (or maybe also other tags) mkgmap
generates a lot of error messages.
For all these error messages the is missing at the end, if it runs
under windows.
Would it be possible to add the correct EOL chars so that the logfile keeps
it's readability?
All other messa
Hi Walter,
hmm, all log messages are written with the same routine, each message is one
line,
and they should all have the correct line ending.
When you say logfile, is that the output written to stderr or do you use java
option
like -Dlog.config=logging.properties to configure the details?
See
