vmarc

Tested on macOS/Safari: not possible to reproduce the problem.

In node network tagging (and in the knooppuntnet analysis logic) it is important to be able to differentiate between what kind of network we are dealing with: - hiking -...

I can confirm your number for France. When restricting the MongoDB query to France it finds 40. In Germany there are 54.

The analysis logic has been changed so that _RouteTagInvalid_ is no longer generated when the _"route"_ tag contains multiple values separated by semicolon(s). Support for MTB routes is still a...

> Note: the facts are still visible in the history in version 2 The fact will remain visible in the history until release v4.0 where the history of all nodes/routes/networks...

> But the route is not rendered on the riding map Yes, this is because the analysis at this moment is still network based, and the route is now analyzed...

The relevant logic can be found in the [AccessibilityAnalyzerImpl](https://github.com/vmarc/knooppuntnet/blob/develop/server/src/main/scala/kpn/server/analyzer/engine/analysis/route/analyzers/AccessibilityAnalyzerImpl.scala) code: ```scala private def bicycleAccessible(way: Way): Boolean = { (way.tags.has("highway") || way.tags.has("highway:virtual") || way.tags.has("route", "ferry") || way.tags.has("bicycle", "yes")) && !way.tags.has("bicycle", "no")...

To show all relevant boundaries in the knooppuntnet maps will require an additional vector based map tile set containing these boundaries. The background vector tiles that are generated with OpenMapTiles...

Closing this issue. See https://github.com/vmarc/knooppuntnet/issues/217#issuecomment-2172873627.

Look again at this issue within the scope of the knooppuntnet re-design.