Hi all,
please try r4213 in the country-border branch, I think it is ready for merge
into trunk:
http://www.mkgmap.org.uk/download/mkgmap.html
I hope this description is clear enough, please suggest improvements /
corrections:
--add-boundary-nodes-at-admin-boundaries=NUM
This optio
Hi Henning,
reg. performance: I think it is now clearly less then 1 s per tile for level 2
boundaries.
reg. option:
I see two ways to control this:
1) style rules may set a special tag mkgmap:xyz on those lines which should be
considered as boundaries.
I have no idea how to name such a tag, and
Hi Gerd,
How much performance does it take?
Wouldn't it be better to create those nodes automatically at every level 2 and
4 boundary and give a possibility to define a individual poly for it for any
other special case?
Henning
On 26 Jul 2018, 19:23, at 19:23, Gerd Petermann
wrote:
>Hi Andrzej
Hi Gerd,
in my opinion this is valuable change and should be merged to trunk. I
would even suggest to use admin level 2 as default. This would lead to
compatibility between maps, even if authors are unaware of this feature.
--
Best regards,
Andrzej
Hi Andrzej,
okay, seems there are many ways to test this ;-)
I've created the routes in MapSource and transferred them to the Oregon.
Next, I looked at them in the Route Manager. With other routes, when I select
button "Map" in the Route Manager
the route is also first displayed as a straight lin
Hi Gerd,
I have imported your routes to BaseCamp and then sent to Dakota. It
looks ok. When I select route as a destination, Dakota shows route for a
moment as a straight line and then recalculates on roads, see pic
"go-to". If I start navigation, then Dakota calculates again, adding a
leg to
