Hi Ticker,
> Is this logic general enough to move into the default style?
This is a solution for my maps and I have tried to make it universal.
There could be other propositions, for example some people could prefer
name of the road over ref number or include name into shield (but it
doesn't
Hi Andrzej
Is this logic general enough to move into the default style?
I assume it replaces:
# Display highway shield for mayor roads if they have a ref and make
them searchable by their name
(highway=motorway | highway=trunk) & ref=* {name '${ref|highway
-symbol:hbox}'; addlabel '${name}'}
Hi Gerd, type=route & route=mtb{ apply mem_pos() = [first,x,last] { set ... }} Could do the job. Andreas Gesendet von Mail für Windows 10 Von: Gerd PetermannGesendet: Mittwoch, 21. November 2018 11:32An: mkgmap-dev@lists.mkgmap.org.ukBetreff: Re: [mkgmap-dev] Add a POI to the start of a
Hi Andreas,
> The problem is that most other relations dont have members with role
> „Start“
I see, that I have repeated an answer already given, sorry.
The main problem is, that many relation aren't quite clean. For example,
segments aren't in order or relation could be not a single line but
Hi,
for some time mkgmap allows for code like this:
type=route & route=mtb
{
apply role=start {
set ...
}
apply role=stop {
set ...
}
}
I'm not sure about "role=stop", it is described as a bus stop, but maybe
for cycle route it has a different meaning.
--
Best regard,
Hi Andreas,
I still don't see where to handle this in mkgmap. A way can be the member of
several route relations.
It might be the start of one and the end of two others, or vice versa. When
the route describes a closed ring it would be start and end.
I don't want to handle those cases in the
