How Renumber Nodes (Coverage) works

There are many commands that do not establish or reset internal node numbers. For example, Generate does not set internal node numbers; they have a value of zero for new arcs created with Generate. Eliminate and Dissolve will keep the existing internal node numbers of the input coverage. Build with the LINE option will not correct these situations. Build with the POLY option and Clean will also renumber nodes in addition to their other operations. Thus, Renumber Nodes is a fast, efficient method to renumber nodes.

It is desirable for the internal numbers of all nodes to be sequentially numbered and have nonzero values. Also, if two or more nodes occur at the same x,y location, they should be identified by the same internal node numbers.

These conditions are important when using other commands

• To list and display node errors, look for different node numbers on arcs. If only two arcs share the same internal node number, the node is identified as a pseudo node. If only one arc has the internal node number, the node is identified as a dangling node. Thus, connecting arcs should share the same node number; otherwise, node error verification and correction can be more difficult.
• ArcInfo Workstation network uses the internal node numbers to define the connectivity of arcs in a network. Arcs that have a common from-node or to-node number are assumed to be connected to each other.
• Before creating a DLG file using Export To DLG, each node should be sequentially numbered using Renumber Nodex.

Use caution with coverages containing coincident and duplicate nodes

• Using From Node Elevation Item and To Node Elevation Item can create more nodes than are actually present. To delete unwanted nodes, run the tool again without specifying these items.
• If the Input Coverage has a node attribute table (NAT), Renumber Nodes works the same as Build with the NODE option.