Check List

Top  Previous  Next

Sometimes a calculation returns a different result (route) compared to what you expected or you get no route at all. Both situations are due to issues somewhere in the network and these can be hard to locate.

 

This is a list of things to check:

 

Look inside network_report.txt (generated when calling TImport.execute):

 

1.Are you using the latest version of RW Net?
2.Is the coordinate unit detected correctly?
3.Should Z-level information have been applied?
4.Do some of the objects have errors?
5.Is the average object length realistic?

 

Check for network errors. See also data sources.

 

Reduce the setup as much as possible:

 

1.Call Open(false,false,false,0) (removes one-way restrictions)
2.Set Turnmode = false, when creating TCalc instance
3.Set Hierarchy = false
4.Skip Limits
5.Use SetShortest
6.Set Alpha = 0
7.Set NoDriveThrough = false

 

If this solved the problem, enable these again one by one, until it fails. Then you know where to look.

 

Create maps in your GIS identifying the problem:

 

1.Look at basic map for no physical connection (missing bridge / ferry etc)
2.Create a thematic map of one-way directions and closed links
3.Create a thematic map of attribute field
4.Create a thematic map of hierarchy attributes etc.
5.Call TurnExportGIS to view turn restrictions
6.Call FindNonConnected from RW Net Pro
7.Call SubNet from RW Net Pro

 

If you have multiple points (Matrix or TSP function), it can be tricky to locate which point makes the trouble. One method is to calculate with 2 points first. If that works OK, try with 3 points, then 4 points etc, until the problem pops up. Now the problem is usually somewhere near the last point being added.