Renumber Nodes (Coverage)

Summary

Updates arc–node topology by renumbering nodes for the input coverage arcs and identifies arcs that share the same node locations.

The tool renumbers the internal node numbers for each arc, assigns the same node number for arcs that share a common node location, and updates the FNODE# and TNODE# items in the arc attribute table (AAT) when it exists.

Learn more about how Renumber Nodes works

Illustration

Usage

• If you specify one elevation item, you must specify the other. These items must be numeric.

• 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 does the same thing as Build with the NODE option.

• All nodes in the input coverage are sequentially renumbered starting with 1.

• All feature attribute tables as well as polygon topology and arc–node topology are maintained by Renumber Nodes.

• Renumber Nodes updates the arc–node topology by renumbering the From Node Elevation Item and To Node Elevation Item of each arc and identifying arcs that share the same node locations. Renumber Nodes renumbers the internal node numbers for each arc, assigns the same node number for arcs that share a common node location, and updates the FNODE# and TNODE# items in the AAT when it exists.

  If you want to run Renumber Nodes on a coverage in the AAT, both of these items must be present and specified for the Renumber Nodes process to work while building nodes.

• Renumber Nodes dissolves coincident and duplicate nodes into single nodes. Use Renumber Nodes with caution. For example, while modeling freeway ramps, you may run into situations having coincident arcs in different planes with multiple nodes sharing the same x,y coordinates. Running Build with the LINE option will preserve this topology. However, running Renumber Nodes will collapse the coincident nodes into single nodes and destroy the topology.

• Build with POLY will eliminate overpass/underpass situations. Coincident nodes at different elevations will dissolve.

• The term "elevation" as referenced here is relative. It doesn't need to be the real world or three dimensional elevation. Rather, it signifies the elevation of the ends of an arc relative to another arc that it may meet or cross. Its primary use is in building the arc-node topology to reflect transportation network situations, such as an overpass/underpass.

• You can model an underpass/overpass situation by giving one set of node elevation values to arcs AB, BC, while arcs XY, YZ could share a different set of node elevation values. Running Renumber Nodes with the elevation arguments will actually retain two distinct nodes at the cross point. As in real life, this will prevent a path between nodes A and Z. Many transportation data vendors make such information available in their data products.

• The "elevation" values for all nodes where there is no conflict could be set to zero. Only in cases where there are multiple nodes sharing the same x,y coordinates will the elevation values be looked up to determine whether they are in the same plane and dissolved or in different planes and retained.

• The coordinate precision of the coverage is unaffected by Renumber Nodes.

• Overlay commands, such as Clip and Dissolve will honor these extra nodes and preserve topology.

Syntax

Renode_arc (in_cover, {from_item}, {to_item})

Parameter	Explanation	Data Type
in_cover	The coverage whose nodes will be renumbered.	Coverage
from_item (Optional)	The item signifying the elevation of the from_node of each arc.	ArcInfo Item
to_item (Optional)	The item signifying the elevation of the to_node of each arc.	ArcInfo Item

Code Sample

Renode example (stand-alone script)

The following stand-alone script demonstrates how to renumber nodes in a coverage.

# Name: Renode_Example.py
# Description: Renumbers the nodes in a coverage
# Requirements: ArcInfo Workstation
# Author: ESRI

# Import system modules
import arcpy
from arcpy import env

# Set environment settings
env.workspace = "C:/data"

# Set local variables
inCover = "major_rds_raw"

# Execute Renode
arcpy.Renode_arc (inCover)

Environments

Current Workspace, Level Of Comparison Between Projection Files, Precision For Derived Coverages, Precision For New Coverages, Scratch Workspace

Licensing Information

ArcView: No

ArcEditor: No

ArcInfo: Requires ArcInfo Workstation installed