Source feature edits and join tables

When you edit source features, you may also need to edit tables that relate the features to other data so that the relationships aren't broken. For instance, if you have historical traffic data, you may need to edit the Streets-Profiles and Streets-TMC join tables. If your network has signposts, the table that joins signposts to streets may need to be edited. The specific reason for these possible edits is that each record in these join tables associates data with a source feature, a side of the feature, and a length of the feature using the feature class ID, feature ID, from position, and to position.

Here are some points to consider when editing source features:

• If you change the shape or attributes of a source feature, this won't cause the creation or deletion of any object IDs; therefore, the source feature will continue to be associated with the same data, such as traffic profiles or signposts, after the rebuild process.
• If you delete a source feature, the associated records in the join table will become irrelevant. The associated records should also be deleted, but this is not required.
• If you split an existing source feature, the feature is divided into two parts: one part retains the Object ID of the original feature, and the other part is assigned a new ID. The source feature with the old ID will continue to be associated with the same join-table records as the original source feature. The part with the new ID will not be associated with any join-table records; therefore, you will need to add one or more records to the join table to ensure the previous relationships are maintained.
• New features that you add to the network will not have any associated traffic profiles until you add corresponding records to the Streets Daily-Profiles table and rebuild the network.