Thanks!
I've comitted a fix.
WanMil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 08.09.2013 14:01, schrieb WanMil:
Hi
* Instead of using hardcoded rules for maxspeed it is now possible
to control that via style file. Set the mkgmap:road-speed-class tag
to the desired class value (0
Thanks Felix,
I have to think about your proposals.
WanMil
Well to make styles easier, maybe we could have a third command which
works like a in between add and set.
That command would only set mkgmap: tags, in case they are not default,
therefore you could later on in the style run rules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 15.09.2013 19:07, schrieb WanMil:
Thanks! I've comitted a fix.
thank you, too
it works now
Bernd
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlI1+v8ACgkQwCMdlf933K8dAwCdG7riv8/UKkz3ZHRqomtIgSgl
Version 2704 was committed by steve on Sun, 15 Sep 2013
Fix for 'mdr20 value changed' message.
Space was being treated as a non-character so any names that differed only
by a space would be treated the same during sorting although not during
separation
into different streets while building the
Hi
http://garmin.osmapa.pl/mkgmap/OSM-Poland-split-ogonki.zip
I have fixed the problem, which was that space was being treated as
an ignored character for sorting purposes in cp 1250.
The commit message gives a bit more detail if you are interested!
I found that it was only 66005025.img that
Hi,
In that case is likely eventually that you will get something
like '??? ??' and '?? ???' followed by '??? ??' again
Well, yes, we get a map with all names like this. You can imagine how
silly it looks like. I have asked once without success, maybe this is
better opportunity to request
