Knooppuntnet analysis
About | Planner | Analysis | Monitor | Issues | ||||||||||||||||||||||||||||||||||||||
(Work in progress) Knooppuntnet Analysis is an Analysis and Maintenance application for node networks. It supports bicycle, walking, horse, inline skating, canoe and motorboat networks.
To use this tool, you need to have an understanding of the structure and editing of OSM, route relations in OSM and tagged junction nodes in OSM. Feel free to explore to get a feel of the concepts and structure. If you really want to dive in please follow this link first: /Maintaining Node Networks in OSM/ Get StartedKnooppuntnet Analysis is reached from the Knooppuntnet home page by clicking or tapping the Analysis icon. The Analysis start page is displayed. You can retun to the home page from anywhere in the application by clicking or tapping the name Knooppuntnet in the upper left corner. This might be a good moment to create a bookmark or add this page to your favorites! The information side bar on the left is quite empty. At the bottom, you can switch languages, and you may log in with your OSM user account. If you do not have an OSM account and want to do serious maintenance work, please go to [1] and create one. Then come back and log in with your OSM account. Without logging in, you can still access the data, but you cannot access the history (changes) and you cannot use the application to redirect you to OSM editing functions. In the main window, these active icons are available:
Statistics Overview: Opens a table showing actual attribute and validation statistics for all the node networks for all countries and all modes of transport Changes Select the icon for the Network type you want to analyse.
Next, select either Analysis by Network (the legacy method) or Analysis by Area (the new method). Analysis by Network is built on Network relations containing all the nodes and all the routes of a named network, including connection routes and connection nodes which are in two network relations. Analysis by Area is built on the hierarchy of administrative areas as recorded in OSM. It ignores the legacy Network relations. Then select the country. As networks spread and expand, more countries will be added. If you selected Analysis by network, the entire list of networks for the country is displayed. The planner map for the chosen type is displayed. This might be a good moment to create a bookmark or add this page to your favorites! The map shows the nodes and node routes of the chosen network type. You can always switch to a different type from the map display. PagesNodeRouteNetworkChangesLocationOverview in numbersSubset networksSubset factsSubset orphan nodesSubset orphan routesSubset mapSubset ChangesLoginLogoutGlossaryAccessibleThe analyzer tries to determine whether the routes as defined in the network are actually accessible for the user for which the network is intended. For implementation details see [2]. The validation rules for hiking-, bicycle-, horse- and skate-routes dictate that one of the following is true for each way in the route relation for the route to be considered "accessible":
The respective access-value must not be set to "no". Motorboat network:
Canoe network, at least 1 of:
The way must not have the tag canoe=no. Orphan nodesAn orphan node is a network node without a known network or route that it belongs to. We can see that the node is a network node because it has the required "network:type node_network", but the node was not added as a member to a known network relation, and also not added as a member to known route relation. If there is something wrong the relation that the node is added to (for example when that relation is not following the rules for a valid network or route relation), then the network node is also considered "orphan".
Orphan routesAn orphan route is a network route without a known network that it belongs to. We can see that the relation represents a network route because it has the required tags, but the relation was not added as a member to a known network relation. If there is something wrong the relation that the route is added to, then the route is also considered "orphan". There is nothing wrong with a route not belonging to a network. In fact in the future we may completely ignore the network relations, so that the notion of orphan routes completely disappears from the application. Information mapInformation maps are situated along the network routes and provide an overview of the network. They can be mapped using nodes that can be optionally be added to the network relation. The analysis logic expects at least the following tags on the node to recognize it as an information map:
|