logo separator

[mkgmap-dev] [PATCH v1] - beware of the bollards!

From Mark Burton markb at ordern.com on Tue Jul 7 15:23:29 BST 2009

Hi Torsten,

> How about a little more general approach? I would propose the following:
> 
> If a way has a note with an access restriction, the segments of the way
> that connect to the node have the access restrictions from the node
> placed on them.
> 
> This would have the following advantages:
> - With such an a feature, you would not only handle bollards, but also
> gates and other obstacles.

Well, the existing code can handle other barriers if it's told about
them.
 
> - You need not to use a default access restrictions, but you can rely on
> the restriction in the data base. If no access restriction is defined in
> the data, you can still imply one via the style file. (I don't know,
> whether such a style rule would be applied in time before you place the
> restrictions on the way?)
> 
> - The maps would be still usable, if it is run with with false vehicle
> settings. (Only the car setting seems to provide a real good routing, so
> to get good a bicycle routing, you need a specially generated map run in
> the car-mode).
> 
> What do you think about such a modification?

I think your suggestion is a good idea. In fact, while working on this
it occurred to me that the same technique could be used to apply other
attributes to the way, such as width and speed limitations. So a general
approach is probably best. I shall work on it.

Cheers,

Mark



More information about the mkgmap-dev mailing list