OverviewNL-HikingNL-BicycleBE-HikingBE-Bicycle

Node network analysis

Summary:

  • 80.583 km
  • 253 networks
  • 38.000 network nodes
  • 48.258 routes

Situation on:

2017-05-27 18:00

Details:

DetailTotalThe NetherlandsBelgiumExplanation
HikingBicycleHikingBicycle
Length (km)80.58317.60637.5847.16618.226 Total length in kilometers.
Networks253112603744 Number of networks.
Nodes38.00014.27811.4206.1636.139 Number of network nodes.
Routes48.25818.35914.2808.5917.028 Number of routes.
RoutesNotContinious282--26 Number of networks with broken routes.
763--73 Number of broken routes.
0,16%0,02%--1,04% Percentage of broken routes.
RoutesWithIssues1196112433 Number of networks containing routes with issues.
1.3534542757140 Number of routes with issues.
2,80%2,47%0,01%8,81%1,99% Percentage of routes with issues.
IncompleteRoutes1.205393275654

Number of routes that are marked as having an incomplete definition.

A route definition is explicitely marked incomplete by adding a tag fixme with value incomplete in the route relation.

Fixmetodo----- Number of routes that are marked with fixmetodo.
OrphanNodes-----

Number of network nodes that do not belong to a network.

The node was not added as a member to a valid network relation, and also not added as a member to valid route relation (that itself was added as a member to a valid network relation or is an orphan route).

OrphanRoutes801272131

Number of network routes that do not belong to a network.

The route was not added as a member to a valid network relation.

6.420105.237729442 Total length (km) of the orphan routes (not included in network length above).
IntegrityChecks94354937 Number of networks that include integrity check.
4.1692.2871.834345 Number of nodes with integrity check.
299294--5 Number of failed integrity checks.
92,83%87,14%100,00%100,00%88,89% Integrity check pass rate (percentage of ok checks).
10,97%16,02%16,06%0,05%0,73% Integrity check coverage (percentage of nodes that do have integrity check information).
UnusedSegments63--3 Number of routes where one or more of the ways (or part of ways) are not used in the forward or backward path or in one of the tentacles.
NodesMissing1411--3 Number of routes for which the end node and/or the begin node is not found in any of the ways of the route.
RedundantNodes5747-19 Number of routes where the ways of the route contain extra nodes other than the start and end nodes.
WithoutWays11--- Routes without ways (a route is expected to have at least 1 way).
RouteNameMissing----- Routes without a "note" tag with the route name.
RouteTagMissing----- The route relation does not contain a "route" tag.
RouteTagInvalid----- The value in the "route" tag in the route relation is unexpected.
RouteUnexpectedNode1---1 Number of routes with one or more unexpected node members. In route relations we expect only nodes with tag "rwn_ref" or "rcn_ref".
RouteUnexpectedRelation----- Number of routes with one or more unexpected members. In route relations we expect only members of type "way", or members of type "node" with a tag "rwn_ref" or "rcn_ref".
ExtraNodes----- Number of network relation members of type "node" that are unexpected (expect only network nodes or information maps as members in the network relation).
ExtraWays----- Number of network relation members of type "way" (expect only route relations or network nodes as members in the node network relation).
ExtraRelations----- Number of network relation members of type "relation" that are unexpected (expect only valid route relations or network nodes as members in the node network relation).
NetworkNameMissing----- Number of networks without "name" tag in the network relation.
Informational:
routesUnaccessible----- Number of unaccessible routes.
InvalidSortingOrder7---7 Number of routes with ways in wrong sorting order.
ReversedRoutes31---31 Number of routes where the ways are in reverse order (from high node number to low node number).
NodeNameMismatch6---6 Routes where the route name does not match with the names of the start node and the end node. The route name is expected to contain the start node name and the end node name, separated by a dash. The start node is expected to have a lower number than the end node.