You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See: https://www.epa.gov/waterdata/nhd-event-data-dictionary for the schema.
US EPAUS EPA NHD Event Data Dictionary | US EPA
The Reach Address Database (RAD) stores reach address information for each Water Program feature that has been linked to the underlying surface water features (streams, lakes, etc) in the National Hydrology Database (NHD) Plus dataset.
Sep 18th, 2015
12:56
I think if you open up the 303d feature table, you'll see a 1:many between permanent_identifier / source_featureid : reachcode in many cases. 12:56
That is the issue that gives me pause. 12:57
If we can index these using the downstream most reach in the 1:many to make it 1:1, then we have something to go forward with.
The text was updated successfully, but these errors were encountered:
See: https://www.epa.gov/waterdata/nhd-event-data-dictionary for the schema.
US EPAUS EPA
NHD Event Data Dictionary | US EPA
The Reach Address Database (RAD) stores reach address information for each Water Program feature that has been linked to the underlying surface water features (streams, lakes, etc) in the National Hydrology Database (NHD) Plus dataset.
Sep 18th, 2015
12:56
I think if you open up the 303d feature table, you'll see a 1:many between permanent_identifier / source_featureid : reachcode in many cases.
12:56
That is the issue that gives me pause.
12:57
If we can index these using the downstream most reach in the 1:many to make it 1:1, then we have something to go forward with.
The text was updated successfully, but these errors were encountered: