Logical Network - To and From Nodes

Certain feature classes require a logical network to be built; others have an optional logical network.  The sanitary sewer pipe and storm sewer pipe modules require the logical network; the street segment feature class has an optional network.

• Feature Class From Node Field - This field stores the name of the string field that will store the Upstream or From Node identifier.  For sewer pipes or storm pipes this is the Upstream Structure, and is required.  For street segments, this is the From Intersection and is optional unless the Accident module is being used, in which case it is required.  This field should be a text or character field.
• Feature Class To Node Field - This field stores the name of the string field that will store the Downstream or To Node identifier. For sewer pipes or storm pipes this is the Downstream Structure and is required.  For street segments, this is the To Intersection and is optional unless the Accident module is being used, in which case it is required.  This field should be a text or character field.

  See Spatial Relationships for information on how to set up the system to automatically update these two fields.  If the spatial relationships function is not used, the user will be responsible for keeping these values current.

• Feature Class From and To Node Table - This is read only.  It shows which table the To and From Nodes will be stored.  The feature class(es) that contains the to and from node point features should be configured to synch to this Lucity table.

  Note: The Water Pipes feature class does not need a From and To Node table.  This information is figured out automatically based on the other configurations.  To have the system automatically populate the From and To Node values into the feature class, make sure there are fields mapped to the water pipe PP_FRM_END, PP_FTYP_CD, PP_TO_END, PP_TTYP_CD fields.  These are not required, but will be automatically populated by Lucity if they exist.