Version mkgmap-r3803 was committed by gerd on Mon, 13 Feb 2017
tags_sorted.patch : print tags ordered by key names
This effects the echotags style function and logging, not the map created by
mkgmap.
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=3803
Version mkgmap-r3802 was committed by gerd on Mon, 13 Feb 2017
surface_v7.patch: change detection of unpaved roads for default style
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=3802
___
mkgmap-dev mailing list
Version mkgmap-r3801 was committed by gerd on Mon, 13 Feb 2017
merge split-shape branch
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=3801
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Gerd,
just have tested following version:
# Roundabouts
junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c
road_class=4 road_speed=2 resolution 24 continue]
junction=roundabout & (highway=trunk | highway=trunk_link) [0x10801
resolution 18]
junction=roundabout &
Am 12.02.2017 um 13:56 schrieb Ticker Berkin:
Hi
With these default rules, my device (Etrex Legend HCx) renders
roundabouts nicely (dark medium line, looks same as 0x04/0x05 line) and
has a suitable 'hover' label. No typ file.
Ticker
Yes, on my Etrex20 and Nuvi 250 I'm also getting a
Hi Gerd,
Regarding routable types without a road_speed or road_class attribute: this can
create other problems when searching for an address along that street, routing
could cause straight lines on the device. Since it is unlikely that there are
any addresses on a roundabouts you can ignore
Hi Andrzej,
good points. I'll try your suggestions.
Gerd
Von: mkgmap-dev im Auftrag von Andrzej
Popowski
Gesendet: Sonntag, 12. Februar 2017 13:56:32
An: mkgmap-dev@lists.mkgmap.org.uk
Hi lig fietser,
hmm, maybe I was mislead by the results of GPSMapEdit. It seems that it shows
some
defaults when a line with a routable type is not in the NOD file. So, only the
type 0xc
line is added to the NOD file, but we also know that it is not good to use
routable types
without a
Hi Gerd,
yes, I understand. The more capable options, the more problems could
arise. But I'm not afraid, I think these options would be used in
scripts, where they would be correct after first debugging.
In case of style-option you could issue a warning if command line
style-option is not
On 02/12/2017 01:45 PM, Gerd Petermann wrote:
> I also thought that this would be the best solution, so I tried to
> modify the OFM lite style like that, but without success. My
> knowledge about typ files is near zero :-(
You don't need a lot of knowledge to copy a polyline definition with
Hi Gerd,
IMO you won't get good routing for cars, if you set all roundabouts to
class 0. My understanding is, that roads with road_class 4 and 3 should
create a proper, continuous network. If you break network at
roundabouts, long distance routing will suffer.
I doubt you will get a nice
Hi
With these default rules, my device (Etrex Legend HCx) renders
roundabouts nicely (dark medium line, looks same as 0x04/0x05 line) and
has a suitable 'hover' label. No typ file.
Ticker
On Sun, 2017-02-12 at 11:39 +, Gerd Petermann wrote:
> Hi all,
>
> the default style contains these
Ralf's approach is better, if I would start rebuild my map I would choose to do
the same, but it will take too much time to rebuilt my map from scratch.
@Gerd, I see now that setting junction=roundabout {set access=no} after the
roundabout rules doesn't work at all, do you have any
Hi Ralf,
I also thought that this would be the best solution, so I tried to modify the
OFM lite style like that, but without success.
My knowledge about typ files is near zero :-(
Gerd
Von: mkgmap-dev im Auftrag
On 02/12/2017 12:59 PM, lig fietser wrote:
> I have used such approach for my bicycle maps and received quite a few
> negative reports with two routable lines on top of each other,
> especially near and at roundabouts. A lot of devices will crash
> (completely shut down) so I'd not recommend
Hi Andrzej,
yes, I think that can be done. Note that this opens a box of worms
because rules may not work as expected when a style-option is missing or has a
typo.
(the tag would be empty).
The user has to find out what options are needed to make the style work.
The options are probably "hidden"
Hi Gerd,
I think this is a good solution for variable styles. Only I would prefer
a more simple use. Regular expressions looks clattered and probably are
more expensive then simple comparison. Could you consider something like
this:
mkgmap option with multiple "key=value", empty value could
Hi ligfietser,
in fact the OFM lite style was the reason that I tried to find a better
solution.
I noticed some strange routing results for this roundabout:
https://www.openstreetmap.org/way/8325782
coming from north (e.g. node 76474542 going south (to node 1601722162).
with setting "OFM racing
Gerd,
I have used such approach for my bicycle maps and received quite a few negative
reports with two routable lines on top of each other, especially near and at
roundabouts. A lot of devices will crash (completely shut down) so I'd not
recommend this. In Lambertus' generic new we use an
Hi all,
the default style contains these rules for roundabouts:
# Roundabouts
junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3
road_speed=2 resolution 18]
junction=roundabout & (highway=primary | highway=primary_link) [0x0c
road_class=3 road_speed=2 resolution 19]
Hi all,
I see no need to use if-then for this. Attached is a quick patch to add an
option like
--style-option=
to mkgmap. If specified, it tells mkgmp to add the tag
mkgmap:style-option=
to each element before style processing.
Sample usage with the attached patch:
java -jar mkgmap.jar
21 matches
Mail list logo