Locating Features Requiring Reach Migration& Migrating Reaches using NHD Geo Edit Tool

If Watershed / SubWatershed units exist in your personal geodatabase –WBD boundaries have been certified and loaded to GeoDatabase

However,

Do not assume that the WBD are correct –

In many cases the certified WBD do not agree with the NHD.You must still make logical decisions as to which sub basinfeatures should be associated with………

ftp://ftp.ftw.nrcs.usda.gov/pub/wbd/status_maps/hucstatusstate.jpg

Locating features to migrate:

Select Subbasin

SPECIAL NOTE: You may complete reach migrations for NHDFlowlines, then NHDWaterbodies for the same subbasin, then move to the next subbasin.

Open NHDFlowline table:Options, Select by AttributesCreate a new selection[ReachCode] LIKE ‘18040012*’Apply

Selected Reaches

Select By Location;Remove from the currently selected features in:NHDFlowlineThat: have their centroid in:SubbasinUse selected featuresApply

22 features with ReachCode 18040012* are outside Subbasin boundary

Pan around extent of subbasin to view selected features and to makedetermination which subbasin the features should be associated with

In this area all but one of the selected features require migration

This feature will stayIn subbasin 18040012

Repeat steps for NHDWaterBodySub type LakePond

Migrating Reaches using NHD Geo Edit Tool

NHD Geo Edit Tool toolbar:Utilities dropdownAssign Permanent Reach Code - Selection

√ NHDFlowlineOK

18040005

18040012

Selected features belong to subbasin18040012 and need to be migrated toSubbasin 18040005 (99999999) for training purposes

New reach codes are allocated for subbasin 99999999

Repeat steps for NHDWaterBodySub type LakePond