sent from a phone

> On 6. Apr 2018, at 03:50, <> 
> <> wrote:
> It doesn't tell you to leave the problem unsolved. It only tells you that 
> tagging the legal default if there is nothing on the ground is not the 
> correct solution to the problem.

defaults on areas are complicated because you can have an infinite number of 
them and while inheriting them in a routing db might be “easy” (unless they are 
contradicting), they are not directly visible on the elements they affect, 
hence troubleshooting could become a nightmare.

We are already mapping “defaults” explicitly for example with maxspeed 
according to context.

Tagging mailing list

Reply via email to