Re: [mkgmap-dev] Test if POI is part of a line

2022-10-15 Thread Felix Herwegh
> I would only like to display barrier/highway=gate point icons if they 
are part of a (best routable) line.


Since I try to declutter my maps as best as possible I too had "remove 
non-relevant gates" on my to do list and followed up on that today.
Accounting for points mapped on or between ways and access restrictions 
optionally stemming from point and/or way I was able, to already thin 
out my gates significantly. The include file is just "re-used" from my 
lines processing.


   /# NoAccess gates on relevant highways//
   //# only works w/ mkgmap option --add-pois-to-lines//
   //if (mkgmap:from-node:barrier ~ '.*(gate)' & highway=*) then//
   //# gate on highway//
   //   include "../inc/RaceSurf"; //
   //   # tagging of (preselected) elements w/ hgh:surface=(Race|noRace)//
   //   # depending on quality in regard to race (and gravel) bike use//
   
   //  if (hgh:surface=Race) then //
   //   (mkgmap:from-node:access ~ 'no|private//
   //    & !(mkgmap:from-node:bicycle ~ 'yes|permissive')
        ...//)
   //  # relevant access restricted by point//
   // |//
   //   (access ~ 'no|private' //
   //    & !(bicycle ~ 'yes|permissive')
        ...//)
   // # relevant access restricted by road segment//
   //[...]//
   //end //
   //end/

But I was not able, to solve the probably most interesting situation:
If a (gate) point is part of two (or more) consecutive ways, it is 
processed multiple times from --add-pois-to-lines, but one would need 
the tags of all ways involved at the same time to make the final 
decision on whether or not to render this point. (That is -for 
starters-, if not at least two ways were deemed interesting, the gate 
might not be rendered although from one way alone, it would).


Is there a concept, allowing to do that?

The only idea I came up with would be, to use the mkgmap:line2poitype 
tag to flag these POIs somehow and finally delete all, if not at least 2 
of those where placed at the exact same location. Somewhat similar to 
deleting identical POIs at the same location as documented for the 
nearby-poi-rules. In the latter case (>2), delete all but one...


Cheers, Felix
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Indexing street belonging to two cities

2022-10-15 Thread Gerd Petermann
Hi Piotr,

reg. [SIGN]: I think we support this with OSM files, so there should be code to 
write the data,
but the current code ignores [SIGN] in *.mp input. So, yes, would be good to 
have a working example.
Please make it small, just a few cities, not a full map of Poland ;) I think I 
just need the *.img file,
but you can also provide all the output from cgpsmapper.

Gerd


Von: mkgmap-dev  im Auftrag von Piotr 
Wawrzyniak 
Gesendet: Freitag, 14. Oktober 2022 22:13
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Indexing street belonging to two cities

pt., 14 paź 2022 o 20:24 Gerd Petermann
 napisał(a):
> Hi Piotr,
> yes, with *.mp files this should be easier. Please provide a sample input and 
> desccribe the expected result
> and also attach the output from cgpsmapper.
> You can upload a zipp here: https://files.mkgmap.org.uk/

That could be possible. What is enough for you, just an img file, or
all files required by Mapsource/Basecamp? Additionally, cgpsmapper
will also include data for [SIGN] sections that allows to control what
is printed on the top bar of garmin devices (eg, Exit 2 toward XXX). I
wonder how difficult would it be to support this feature as well.
Piotr
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev