|
Check list
|
Previous Top Next |
| · | Look inside network_report.txt (generated when calling NWcreate):
|
| 1. | Are you using the latest version of RW Net?
|
| 2. | Is the coordinate unit correct?
|
| 3. | Should Z-level information have been applied?
|
| 4. | Do some of the objects have errors?
|
| 5. | Is the average object length reasonable?
|
| · | Check for network errors. See also data sources.
|
| · | Do you create and load your network in the correct order? See flowchart.
|
| · | Do you check the return code from all function calls?
|
| · | Reduce the setup as much as possible:
|
| 1. | Call Attributeload(false) (removes oneway restrictions) or
|
| 2. | Skip calling Attributeload (removes oneway restrictions and mode restrictions)
|
| 3. | Set Turnmode = false
|
| 4. | Set Hierarchy = false
|
| 5. | Skip Limits
|
| 6. | Use SetShortest instead of SetFastest
|
| 7. | Set Alpha = 0
|
| · | 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 TurnExport2_GIS to view turn restrictions
|
| 6. | Call FindCloseNodes from RW Net Pro
|
| 7. | Call NodeLinkCheck from RW Net Pro.
|
| 8. | Call SubNet from RW Net Pro
|
| 9. | If you don't have RW Net Pro version, try Isolink2 with a large stepsadd() value
|