quaelnix

> So what to do? The problem in your sample in the first post could be fixed like this: ``` assign costfactor ... switch or highway=proposed highway=abandoned 100000 switch or...

@afischerdev, sounds reasonable, but I would recommend to lower the `SAC_scale_limit` to 2 or maybe even to 1.

> What is the reason for your limit? T3 includes ways which are definitely not suitable for the typical pedestrian. > as an end user I prefer to have a...

Off the top of my head, I would say that multi-level routing is not easily possible with BRouter, but I could be wrong. Adding support for the [`conveying`](https://taginfo.openstreetmap.org/keys/conveying#values) tag might...

The penalty is so high because there is neither a cycle route nor a bicycle tag on this way. Maybe use `consider_traffic` instead of `avoid_unsafe` in such cases?

This tag will be supported once https://github.com/abrensch/brouter/pull/458 is merged.

> that can cause profiles to change their behaviour by just extending the lookup-table But the same is true if "unknowns" are not suppressed? But I agree that changes in...

At first glance, this seems closely related to: https://github.com/abrensch/brouter/issues/522.

We would have to add `railway=ferry` to the lookup table, but it only seems to be used 17 times world wide: https://taginfo.openstreetmap.org/tags/railway=ferry#overview A temporary workaround would be to use bee-line...

| SRTM (3asec) | LIDAR (1asec) | | :---: | :---: | |  |  |