quaelnix

@poutnikl, the problem is the `issidewalk` logic.

I would suggest that we don't fix this bug because, as you said, it would very likely do more harm than good.

@poutnikl, what if we would replace: ``` or issidewalk ``` with: ``` or and issidewalk not access=no ``` This would likely almost exclusively affect ways that are closed for construction.

Unfortunately it's not that simple. To make it really work, we would need something ugly like this: ``` or and issidewalk not ( and access=no and ( or bicycle= bicycle=no...

My home lap contains a 5 km long monotonous ascend in a valley, which does highlight the limitations of the SRTM data:   

The barometer data was obtained from the average of 10 trips (5 in each direction) along the route:   

> It's not space savings that prevented updating to 1'' srtm data so far. It's just that I could not prove a significant effect on the results. Unless I've done...

@abrensch, I've been using the LiDAR elevation data extensively over the past few weeks, and I have to say it's amazing. --- However, depending on what elevation data we use,...

My winter commute along two rivers with several bridges and many underpasses:  @rkflx, I'm having a hard time finding even one place where the LIDAR data (1asec) fails.

I also think that we should not support false tagging practices like this: - [tracktype=grade3-5](https://taginfo.openstreetmap.org/tags/tracktype=grade3-5) - [highway=traffic_signals;crossing](https://taginfo.openstreetmap.org/tags/highway=traffic_signals%3Bcrossing) - [traffic_sign:direction=forward;backward](https://taginfo.openstreetmap.org/tags/traffic_sign%3Adirection=backward%3Bforward) - [traffic_signals:direction=forward;backward](https://taginfo.openstreetmap.org/tags/traffic_signals%3Adirection=backward%3Bforward)