150 likes | 247 Views
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 –
E N D
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 basin features should be associated with………
ftp://ftp.ftw.nrcs.usda.gov/pub/wbd/status_maps/hucstatusstate.jpgftp://ftp.ftw.nrcs.usda.gov/pub/wbd/status_maps/hucstatusstate.jpg
SPECIAL NOTE: You may complete reach migrations for NHDFlowlines, then NHDWaterbodies for the same subbasin, then move to the next subbasin. Locating features to migrate: Select Subbasin
Open NHDFlowline table: Options, Select by Attributes Create a new selection [ReachCode] LIKE ‘18040012*’ Apply
Select By Location; Remove from the currently selected features in: NHDFlowline That: have their centroid in: Subbasin Use selected features Apply
22 features with ReachCode 18040012* are outside Subbasin boundary
Pan around extent of subbasin to view selected features and to make determination which subbasin the features should be associated with In this area all but one of the selected features require migration This feature will stay In subbasin 18040012
Repeat steps for NHDWaterBody Sub type LakePond
NHD Geo Edit Tool toolbar: Utilities dropdown Assign Permanent Reach Code - Selection
√ NHDFlowline OK 18040012 18040005 Selected features belong to subbasin 18040012 and need to be migrated to Subbasin 18040005 (99999999) for training purposes
Repeat steps for NHDWaterBody Sub type LakePond