Possible Network Errors
Below is shown some examples on networks, which are NOT correct, but all look correct unless you check out the details:
Missing snap at an intersection
This means the network doesn't connect and the movement to from the disconnected section, isn't possible.
In the example below, the gap is just 1 meter and can't be seen at normal zoom levels.
These can be detected by using the Close Node Check.
Split at overpass / underpass
This means a lot of impossible turn movements are suddenly made possible.
However your data may have z-levels in which case these are used to overcome this issue.
The z-levels work in the direction of the road and the elevation is defined by a series of numbers to indicate relative height.
Numbers between -9 and 9 are used for this purpose.
Doesn't split/break at intersections
This means turns are not possible at intersections, because no proper node exists at the point where they touch.
These errors can be detected by using the Node-Link check
Multi sectioned Polylines
Polylines with more than 1 section are ignored. They will not form part of any route.
These errors are detected during the network creation process.
There will be a file called Network_Report.txt in the same folder as the network table.
We recommend you check this file after creating a network