OverviewNL-HikingNL-BicycleBE-HikingBE-Bicycle

Node network analysis

Summary:

  • 86.321 km
  • 256 networks
  • 41.936 network nodes
  • 53.577 routes

Situation on:

2018-02-23 06:00

Details:

DetailTotalThe NetherlandsBelgiumExplanation
HikingBicycleHikingBicycle
Length (km)86.32120.43838.0448.26319.575 Total length in kilometers.
Networks256115603843 Number of networks.
Nodes41.93616.40511.9887.0576.486 Number of network nodes.
Routes53.57721.29814.8349.7557.690 Number of routes.
RoutesNotContinious62112 Number of networks with broken routes.
133118 Number of broken routes.
0,02%0,01%0,01%0,01%0,10% Percentage of broken routes.
RoutesWithIssues884312321 Number of networks containing routes with issues.
735332134557 Number of routes with issues.
1,37%1,56%0,01%3,54%0,74% Percentage of routes with issues.
IncompleteRoutes689299-34941

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

OrphanRoutes1153473827

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.6882455.120878444 Total length (km) of the orphan routes (not included in network length above).
IntegrityChecks114485646 Number of networks that include integrity check.
6.9014.0462.804546 Number of nodes with integrity check.
405401-13 Number of failed integrity checks.
94,13%90,09%100,00%80,00%93,48% Integrity check pass rate (percentage of ok checks).
16,46%24,66%23,39%0,07%0,71% Integrity check coverage (percentage of nodes that do have integrity check information).
UnusedSegments74-12 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.
NodesMissing11--- Number of routes for which the end node and/or the begin node is not found in any of the ways of the route.
RedundantNodes4736-110 Number of routes where the ways of the route contain extra nodes other than the start and end nodes.
WithoutWays----- 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.
RouteUnexpectedNode----- 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).
ExtraRelations33--- 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.
InvalidSortingOrder1---1 Number of routes with ways in wrong sorting order.
ReversedRoutes----- Number of routes where the ways are in reverse order (from high node number to low node number).
NodeNameMismatch----- 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.