OverviewNL-HikingNL-BicycleBE-HikingBE-Bicycle

Node network analysis

Summary:

  • 77.304 km
  • 246 networks
  • 35.484 network nodes
  • 45.104 routes

Situation on:

2016-12-06 00:00

Details:

DetailTotalThe NetherlandsBelgiumExplanation
HikingBicycleHikingBicycle
Length (km)77.30417.24636.7206.20817.129 Total length in kilometers.
Networks246110613243 Number of networks.
Nodes35.48413.75910.8065.3475.572 Number of network nodes.
Routes45.10417.33813.5827.6816.503 Number of routes.
RoutesNotContinious51321234 Number of networks with broken routes.
50673220411 Number of broken routes.
1,12%0,42%0,01%0,26%6,32% Percentage of broken routes.
RoutesWithIssues1407262636 Number of networks containing routes with issues.
2.30877210980546 Number of routes with issues.
5,12%4,45%0,07%12,76%8,40% Percentage of routes with issues.
IncompleteRoutes1.339358-96714

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.
OrphanNodes111--9615

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).

OrphanRoutes684284253345

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

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

7.589115.2601.1671.151 Total length (km) of the orphan routes (not included in network length above).
IntegrityChecks84284817 Number of networks that include integrity check.
3.2151.9221.247145 Number of nodes with integrity check.
246239115 Number of failed integrity checks.
92,35%87,57%99,92%-88,89% Integrity check pass rate (percentage of ok checks).
9,06%13,97%11,54%0,02%0,81% Integrity check coverage (percentage of nodes that do have integrity check information).
UnusedSegments1971241765 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.
NodesMissing351173511558 Number of routes for which the end node and/or the begin node is not found in any of the ways of the route.
RedundantNodes1921762113 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).
RouteNameMissing238231-52 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.
RouteUnexpectedNode1313--- 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".
ExtraNodes6125-234 Number of network relation members of type "node" that are unexpected (expect only network nodes or information maps as members in the network relation).
ExtraWays9-414 Number of network relation members of type "way" (expect only route relations or network nodes as members in the node network relation).
ExtraRelations157-26 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).
NetworkNameMissing1-1-- Number of networks without "name" tag in the network relation.
Informational:
routesUnaccessible152-49 Number of unaccessible routes.
InvalidSortingOrder6121328821290 Number of routes with ways in wrong sorting order.
ReversedRoutes1.19950717896418 Number of routes where the ways are in reverse order (from high node number to low node number).
NodeNameMismatch28420-128136 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.