Attributes | Frequently Asked Questions | Data Maintenance

What to do if you make attribute updates

These reach files are for you users and it is assumed that you will want to update any mis-coded features you find. Currently the established protocol allows for attribute updates and they will be accepted after undergoing verification. For example, if a canal (414) is found to be mis-coded in the MINOR1 field as a stream (412), you are allowed to make the correction. A listing of acceptable attribute codes can be found in the metadata document (reachfile).NAR INFO file.

You may want to add names to previously unnamed streams. We will accept new or corrected stream names if they are entered into the feat_name field exactly as they appear on the paper manuscript. If corrections are made, then please email 100k reach manager at StreamNetGIS@psmfc.org with a list of named arcs listed by rrn, which uniquely identifies each arc in the region. For any other attribute changes, a text file listing the reach file, rrn, old value, new value, should also be forwarded to the reach manager. The updates will be incorporated into the master copy and included in the log file. Registered users will periodically be notified if substantial changes are made to a particular huc.

Attributes that cannot be changed are the HUC, SEG, RMI and RRN fields. These values comprise the unique river reach codes for that reach file and must remain static. If, because of some error with the file that could affect the reach code, these corrections must be handled by the Streamnet / PSMFC. Any questions about this should be sent on to the reach manager.

A log file has been created to track all reach files that have undergone additional updates.
You should check this log file periodically to see if you have the most current version of a particular reach file.

What to do about graphic errors

Graphic corrections are still being handled thru the USGS. If you should find a problem with a reach file you should contact us.
The types of graphic problems that can still exist in a reach file may include:

• Arcs flowing in the wrong direction
• Arcs falling into the wrong cataloging unit
• Mis-placement of a connector arc or centerline
• Missing arcs (Appear on the 100K-scale manuscript but not in the graphic file)
• Graphic feature has shifted or been overly generalized

Adding features

As of this date no protocol has been developed for adding features to the reach files. Please contact the 100k reach manager if you have questions concerning the addition of arcs to these coverages.