logo separator

[mkgmap-dev] Nearby poi feature

From Ticker Berkin rwb-mkgmap at jagit.co.uk on Fri Jun 19 13:00:37 BST 2020

Hi

I have this in my style:

# stop routing on service roads (esp. service=parking_aisle) if there
might be a gate
highway=service & mkgmap:way-has-pois=true {add access=destination}

It isn't foolproof.

Elsewhere (in points) I don't make any assumptions about a
barrier=gate... restricting access over what the access= tag specfies.

Ticker
 
On Fri, 2020-06-19 at 10:13 +0000, Gerd Petermann wrote:
> Hi Joris,
> 
> yes, the --link-pois-to-ways feature can be quite confusing, esp. in
> combination with --add-pois-to-lines.
> The original barrier node is used by the --link-pois-to-ways feature
> to possibly create a route restriction (after the style rules were
> applied to both the barrier node and the way). The POIs which are
> generated by the --add-pois-to-x feature do not have any influence on
> routing.
> I think you get the best results when you don't change the access tag
> for the barrier node.
> 
> Gerd
> 
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> von Joris Bo <jorisbo at hotmail.com>
> Gesendet: Freitag, 19. Juni 2020 11:57
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Nearby poi feature
> 
> Hi Gerd
> 
> Sorry, I did not know that. I did used it very intensily to get
> access tags to barriers linked to highways.
> It works as assumed to 'catch' the poi's and use them.
> I made some 'unittests' based on the values and also they work fine
> as well.
> So I think it's a go.
> 
> Nevertheless my initial goal of applying the access tags to barriers
> did not work for now.
> Because there are two poi's passing by, the original osm node stil
> gets access = no
> The access I set to the poi derived from the line based on the from
> -node code is ignored by basecamp routing. I can only tell the
> routing mechanism to use the barrier if I set access = yes on the
> original osm node.
> I stopped further testing because of my lack of indept mkgmap logic
> and the many changes I had to make to my style.
> 
> Kind regards
> Joris



More information about the mkgmap-dev mailing list