On Mon, 10 Oct 2022 at 22:05, ael wrote:
> On Mon, Oct 10, 2022 at 09:39:11PM +0200, Felix Herwegh wrote:
>
>
> I have mapped gates in a fence/wall which are not on routable lines.
> These are very important if you are to find your way out of an enclosure
> or field. I am thinking of just such a
Hi (another) Felix,
yes, you can omit the clause mkgmap:line2poi=true.
I've only added this check to make clearer that the rule only works with the
--add-pois-to-lines option.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Herwegh
Gesendet: Montag, 10.
On Mon, Oct 10, 2022 at 09:39:11PM +0200, Felix Herwegh wrote:
> Hey,
>
> I'm new here (Hello!), so please be patient if I'm missing points ;-)
>
> @ Felix
>
> >/...so I will put useless [] symbols into the map - as there is no way to
> check whether or not it //*is*//attached to a routable
Hey,
I'm new here (Hello!), so please be patient if I'm missing points ;-)
@ Felix
>/...so I will put useless [] symbols into the map - as there is no way
to check whether or not it //*is*//attached to a routable line./
But couldn't you check whether the line the point is attached to later
*mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...]*
--- I will give this a try. Is this implemented in the main branch? I
thought this tag was related to patch poi-tagged-v3.patch
and never accepted.
I had not fully understood how it worked however. Will try this out and see
Ah okay thanks for the clarification - well okay then those ways are not
removed - except if they already have themselves an access=private on them.
However I cannot check this from the points file - so I will put useless
gate symbols into the map - as there is no way to check whether or not it
is
Hi Eric,
the option --add-pois-to-lines is operates on the nodes of the ways before any
style rules were executed. So,
whatever you do in the lines rules has no effect on the generated points.
Gerd
Von: mkgmap-dev im Auftrag von
ankeric@gmail.com
Hi Felix,
please check the docu for special tag mkgmap:from-node:attname . I think this
allows to filter a barrier node which on a highway.
A rule in points like this should work with option --add-pois-to-line:
mkgmap:line2poi=true & highway=* & mkgmap:from-node:barrier=gate [...]
I didn't try
Hi Gerd,
I also have a - similar? - issue implementing poi2line.
I cannot Add or Delete poi2line nodes.
Perhaps (as you said):
"One problem with your suggested solution is that the current implementation in
mkgmap processes (tagged) nodes before lines".
In 'lines' this is working OK:
Hi Felix,
the current implementation of the link-pois-to-ways doesn't transfer the access
tag(s) to the way. It just creates a route restriction which tells Garmin
that it must not route the given vehicles through the barrier. Older
implementations created a short stub close to the barrier
Also I don't like using --link-pois-to-ways to put an access=private onto a
road - and then remove this road. Because in the case of a park - the
footways/pathes on both sides of the gate do exist. So an access=private
does not actually apply to the road. So it's correct to show the road, and
show
Hi Gerd,
No --*add-poi-to-lines* creates points from a line that has certain tags.
What I try to achieve is actually to remove points that are NOT part of a
line / or part of a line that is not rendered in the map. There is no
reason to show a gate if you don't have a line/road.So essentially
Hi Felix,
my first thought was that --add-poi-to-lines is all that you need, but maybe
I've missed something?
One problem with your suggested solution is that the current implementation in
mkgmap processes
(tagged) nodes before lines. I can't remember exactly why but a change probably
causes
13 matches
Mail list logo
