Hi Greg,
the previous rule existed since 2009 and I never liked it. It is not a special
case in Garmin software but a workaround to fix improper tagging. I'd be happy
to remove the new rule completely. If I got that right only Minko wants it.
See again
I think part of the problem is that railway=abandonded is not a
statement either way about
whether it is reasonably physically traversable on foot
whether there is any right of access
so I guess I don't see why a way with railway=abandonded and no highway
tags should be presumed routable in
Version mkgmap-r4429 was committed by gerd on Tue, 21 Jan 2020
Default style: Use railway=abandoned only as routable way when certain
criterias match
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4429
___
mkgmap-dev mailing list
Just for the sake of argument: I don't like [access=no].
It's suggesting [access=no] is "default" access (which it's not).
Next step is to add the Exceptions: [bicycle=yes], [foot=yes].
Double denial, Conflicting information, Contradictio in terminis.
Also wondering: when is [access=no] - ever -
Hi Ticker,
you are right, that's a good point.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Dienstag, 21. Januar 2020 13:18
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] change handling of railway=abandoned
Hi
The
Hi
The advantages of my rule is that it doesn't create a routable line if
there is no need for it and that it can become a footway or cycleway
depending on the tags.
Gerd's rule would create routable track then disable all access modes.
These are chosen as the start/end point of a route if
Hi,
@Bernhard:
adding "access=no" doesn't make a way unroutable when the way has e.g.
vehicle=yes or foot=yes. It just changes the default
access which is assumed for highway=*. See also what happens in inc/access.
Reg. Tickers Rule:
I don't like it because it is more complex and somehow
Hi
Gerd rule should be OK with the addition clause of & highway!=*, but is
there any reason not to have what I suggested.
Ticker
On Tue, 2020-01-21 at 11:36 +0100, Bernhard Hiller wrote:
> Hi Gerd,
> of course, {deletealltags} is a different action: it removes the way
> completely. "{add
Hi Gerd
>From experimenting with one of my Garmins (can't remember which one),
if it couldn't find a label for the correct language, it just picked
the first one in the label area for the object, regardless of the
language. This seemed to be the first one textually in the file from
the couple of
Hi Gerd,
of course, {deletealltags} is a different action: it removes the way
completely. "{add access=no}" just makes it unroutable, but leaves it
visible on the map.
Lte's take a look at the roads in my example (due to changes during the
last couple of hours, be sure to look at last year's
Hi Ticker,
not sure if I like the idea of a default language using English. What happens
when the device is set to e.g. Turkish? Doesn't Garmin provide a good default
string for "Lake" in Turkish?
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Hi all
Patch attached that makes the following changes to mapnik.txt. This is
held in resources/typ-files and distributed in examples/typ-files.
- Add UTF-8 BOM at the start of the file, so that many text editors and
mkgmap will recognise the encoding.
- Add following line near start of file,
12 matches
Mail list logo
