Hi
> I have been replacing my use of base-style with 'include' statements and
> encountered a problem using eg 'include "points" from default;'. When I
> do this, mkgmap reports that it can't find 'inc/address' , which is
> included in the default style points file. It turns out that mkgmap is
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Steve,
an easy solution could be adding a second code-word eg. include_default.
Henning
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.20 (MingW32)
iQEcBAEBAgAGBQJSHOBfAAoJEPFgsWC7jOeTiwMIAOjbAnnarnM8EA6XyHeeOf8i
UaJ3P7Ai23PY7WJxfv+V4cUcEIhRIMa
mkgmap has a LineMergeFilter but that does not merge the road network.
Attached patch performs a merging in the OSM data just before the road
network is created. This has the advantage that the source code for the
merging is quite easy. Turn restrictions and through routes are considered.
I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi WanMil,
I think the list should contain all tags which are used in
style-files, or are these keys are checked in a seperate way and the
list contains only internal tags?
Henning
Am 27.08.2013 21:31, schrieb WanMil:
> For anyone who is interested
>
> Hi WanMil,
> I think the list should contain all tags which are used in
> style-files, or are these keys are checked in a seperate way and the
> list contains only internal tags?
>
> Henning
>
Hi Henning,
the list need not contain all tags of the style file because the ways
are merged after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi WanMil,
so you are merging objects with the same Garmin-ID, unless they
containing one key of the mentioned list. In this case the list seems
to be quite ok. Wasn't there something like mkgmap:street or
streetname or am I wrong?
As you pointed out
Hi,
does roads have to have the same post code? I don't know internal
representation of these data, but in mp sources single road can have
parts with different post code or city/region.
Do you check angle at which roads are merged?
Imagine a two-way road, which splits into 2 one-way roads befo
