afischerdev

@quaelnix What is the reason for your limit? I thought to make it variable for direct use. ``` assign SAC_scale_limit 3 # %SAC_scale_limit% | all paths with sac_scale higher than...

Added the 'conveying' to the next [generation lookups.dat](https://github.com/afischerdev/brouter/commit/c6660a15d7666a548163bbe848d2f723a3260731).

> So we would need to inject the parameter before the profile is parsed This is done in lib 1.6.4. In [RoutingContext](https://github.com/afischerdev/brouter/blob/6d64da3a84d56bab2acfeff5041d5f61017f9bec/brouter-core/src/main/java/btools/router/RoutingContext.java#L111) the routine readGlobalConfig() calls the setVariableValue with true...

In this special case we could exclude highway=unknown in all.brf As we do for the unknown waterways So the other unknown values are still available.

We have [via ferrata](https://wiki.openstreetmap.org/wiki/Tag%3Ahighway%3Dvia_ferrata) already in the next [lookups.dat](https://github.com/afischerdev/brouter/blob/update-lookups/misc/profiles2/lookups.dat) from #458 So we need an update for the profiles anyway.

Inspired by @radim-asamm we will start with a proof of concept in my branch [add-warnings](https://github.com/afischerdev/brouter/tree/add-warnings). Please have a look there, the first code is arrived.

@devemux86 > So now we must set engine mode 6 for rerouting and 0 for routing? No, routing and rerouting goes as always engine mode 0 The idea behind engine...

> How does it work for the users, who sets the engine mode to 6? This is not transparent for the user. It is just a call from the routing...

This was reverted with #679

@abrensch It seems you have some ideas for testing the data. Great. I have already prepared an update, but it will take some days for preparation.