The HydroAdd Data Schema

Click here to see this page in full context

The HydroAdd Data Schema

HydroAdd requires your data be in the HydroAdd schema. Both core and QC fields are required.

Learn how to put your data into the HydroAdd schema.

HydroAdd point schema, core fields

Field Name	Field Description	Source	Notes	Field Type	Length	Domain	Allow Nulls
SourceID	Unique identifier of source data feature.	User	Required. Can be pre-populated by the user. Any alphanumeric text is acceptable. HydroAdd uses the SourceID as the feature identifier in the queue. SourceID is also used as the feature label in the map. SourceID is required to save any new or updated features.	text	130		No
SourceAgency	Source agency. Owner of data.	User	Name or description of agency. Can be pre-populated by the user. For example: U. S. Geological Survey.	text	130		Yes
SourceDataset	Description of source data.	User	Name or description of dataset. Can be pre-populated by the user. For example: National Water Information System.	text	130		Yes
SourceFeatureURL	Unique URL to source feature data.	User	Use for a unique or general web address to your feature data on the internet. For example: https://waterdata.usgs.gov/monitoring-location/09380000/#parameterCode=00065&period=P7D	text	255		Yes
FeatureType	Type of feature or type of hydro observation.	User	Type of hydro observation. Can be pre-populated by the user. Any data type is acceptable. For example: dam, stream gage, divergence structure, hydrologic unit outlet, spring, seep, sink, rise, biologic sampling site, point source pollution, Wild and Scenic River, Waters of the United States, stretches of river for recreational rafting, dye traces in a karst landscape; algal blooms on reservoirs, or hyacinth overgrowth on reservoirs.	text	60		Yes
ReachCode	ReachCode of network address.	Populated by HydroAdd	ReachCode can be pre-populated by the user prior to running Batch QC with HydroAdd. Batch QC will use the pre-existing ReachCode for addressing if an NHD feature with a matching ReachCode is available in the search tolerance.	text	14		Yes
Measure	Measure of network address.	Populated by HydroAdd	The measure is a number between zero and one-hundred--zero being downstream and one hundred being upstream. In the NHD HR model, the From Measure is always upstream--the larger measure, while the To Measure is always downstream--the smaller measure. Measure can be thought of as a "percent upstream" on a ReachCode.	double			Yes
ReachSMDate	Most recent date of spatial modification of underlying NHD reached feature.	Populated by HydroAdd	ReachSMDate is a time stamp of most recent geometry edit to the feature. Pulled from NHDReachCodeMaintenance table	date			Yes
AddressDate	Date of addressing.	Populated by HydroAdd	Date of creation or most recent edit of user's addressed data.	date			Yes
Catchment	NHDPlus HR Catchment. NHDPlus ID.	Populated by HydroAdd	Pulled from the most recent snapshot of NHDPlus HR catchments	double			Yes
HU	WBD HU12.	Populated by HydroAdd	HU12 is populated by default. User can manually enter any HU-level up to HU16.	text	16		Yes
OnNetwork	Indicates if an item is located on the flowline network or not.	Populated by HydroAdd	For unaddressed items, OnNetwork=No. After addressing OnNetwork=Yes.	short		NoYes Domain	No
HydroAddressID	Unique identifier. 40-digit GUID.	Populated by HydroAdd	HydroAdd creates a unique identifier for all new features. For existing features, if HydroAddressID is not already populated, HydroAdd will create a GUID when the feature is updated and saved.	text	40		Yes

HydroAdd point schema, QC fields

Field name	Field Description	Source	Notes	Field type	Length	Domain	Allows Nulls
GNIS_NAME	GNIS_NAME at network address. Populated by HydroAdd tool during manual addressing or Batch QC.	Populated by HydroAdd	♦ Can be pre-populated by the user prior to running Batch QC with HydroAdd. ♦ Batch QC will use the pre-existing GNIS_NAME for addressing if an NHD feature with a matching GNIS_NAME is available in the search tolerance.	text	65		Yes
GNIS_ID	GNIS_ID at network address. An QC optional field. If the field is present in the user’s data, HydroAdd will populate it during manual addressing or Batch QC.	Populated by HydroAdd	♦ Can be pre-populated by the user prior to running Batch QC with HydroAdd. ♦ Optional field	text	10		Yes
SnapTolerance	User input. SnapTolerance is a buffer around the input point. Points will snap to an NHDFlowline feature within the SnapTolerance.	User input	♦ If SnapDistance <= SnapTolerance, then InSnapTolerance = Yes. ♦ If no NHDFlowlines are in the SnapTolerance, then InSnapTolereance = No, InQCTolerance = No, and QCApproved = No	double			No
SnapDistance	Distance in meters from the original point feature to the newly addressed location.	Populated by HydroAdd	Indicates how far a point moved during update or Batch QC.	double			No
InSnapTolerance	Indicates if the original point feature is within the SnapTolerance.	Populated by HydroAdd	If SnapDistance <= SnapTolerance, then InSnapTolerance = Yes.	short	1	NoYes	No
QCTolerance	User input. Maximum allowable distance in meters to approve snapped feature. The QC tolerance is the maximum distance where the point is automatically approved.	User input	If SnapDistance <= QCTolerance, then InQCTolerance = Yes	double			No
InQCTolerance	Indicates if the SnapDistance is within the user input QCTolerance.	Populated by HydroAdd	♦ If SnapDistance <= QCTolerance, then InQCTolerance = Yes ♦ If no NHDFlowlines are in the SnapTolerance, then InSnapTolereance = No, InQCTolerance = No, and QCApproved = No	short	1	NoYes	No
QCApproved	Indicates approval status.	Populated by HydroAdd	QCApproved = NO means the user should manually QC the item in an editing queue	short	1	NoYes	No

HydroAdd line schema, core fields

Field Name	Field Description	Source	Notes	Field Type	Length	Domain	Allow Nulls
SourceID	Unique identifier of source data feature.	User	Required. Can be pre-populated by the user. Any alphanumeric text is acceptable. HydroAdd uses the SourceID as the feature identifier in the queue. SourceID is also used as the feature label in the map. SourceID is required to save any new or updated features.	text	130		Yes
SourceAgency	Source agency. Owner of data.	User	Name or description of agency. Can be pre-populated by the user. For example: U. S. Geological Survey	text	130		Yes
SourceDataset	Description of source data.	User	Name or description of dataset. For example: National Water Information System	text	130		Yes
SourceFeatureURL	Unique URL to source feature data.	User	Use for a unique or general web address to your feature data on the internet. Can be pre-populated by the user. For example: https://waterdata.usgs.gov/monitoring-location/09380000/#parameterCode=00065&period=P7D	text	255		Yes
FeatureType	Type of feature or type of hydro observation.	User	Type of hydro observation. Can be pre-populated by the user. Any data type is acceptable. For example: dam, stream gage, divergence structure, hydrologic unit outlet, spring, seep, sink, rise, biologic sampling site, point source pollution, Wild and Scenic River, Waters of the United States, stretches of river for recreational rafting, dye traces in a karst landscape; algal blooms on reservoirs, or hyacinth overgrowth on reservoirs.	text	60		Yes
ReachCode	ReachCode of network address.	Populated by HydroAdd	ReachCode can be pre-populated by the user prior to running Batch QC with HydroAdd. Batch QC will use the pre-existing ReachCode for addressing if an NHD feature with a matching ReachCode is available in the search tolerance.	text	14		Yes
FromMeasure	From measure of network address.	Populated by HydroAdd	The measure is a number between zero and one-hundred--zero being downstream and one hundred being upstream. In the NHD HR model, the From Measure is always upstream--the larger measure, while the To Measure is always downstream--the smaller measure. Measure can be thought of as a "percent upstream" on a ReachCode.	double			Yes
ToMeasure	To measure of network address.	Populated by HydroAdd	The measure is a number between zero and one-hundred--zero being downstream and one hundred being upstream. In the NHD HR model, the From Measure is always upstream--the larger measure, while the To Measure is always downstream--the smaller measure. Measure can be thought of as a "percent upstream" on a ReachCode.	double			Yes
ReachSMDate	Most recent date of spatial modification of underlying NHD reached feature.	Populated by HydroAdd	ReachSMDate is a time stamp of most recent geometry edit to the feature. Pulled from NHDReachCodeMaintenance table	date			Yes
AddressDate	Date of addressing.	Populated by HydroAdd	Date of creation or most recent edit of user's addressed data.	date			Yes
FromCatchment	NHDPlus HR Catchment associated with the FromMeasure of line addressed data. The NHDPlus ID.	Populated by HydroAdd	Pulled from the most recent snapshot of NHDPlus HR catchments.	double			Yes
ToCatchment	NHDPlus HR Catchment associated with the ToMeasure of line addressed data. The NHDPlus ID.	Populated by HydroAdd	Pulled from the most recent snapshot of NHDPlus HR catchments.	double			Yes
FromHU	WBD HU12 associated with the FromMeasure of line addressed data.	Populated by HydroAdd	HU12 is populated by default. User can manually enter any HU-level up to HU16.	text	16		Yes
ToHU	WBD HU12 associated with the FromMeasure of line addressed data.	Populated by HydroAdd	HU12 is populated by default. User can manually enter any HU-level up to HU16.	text	16		Yes
OnNetwork	Indicates if an item is located on the flowline network or not.	Populated by HydroAdd	For unaddressed items, OnNetwork=No. After addressing OnNetwork=Yes.	short		NoYes Domain	No
HydroAddressID	Unique identifier. 40-digit GUID.	Populated by HydroAdd	HydroAdd creates a unique identifier for all new features. For existing features, if HydroAddressID is not already populated, HydroAdd will create a GUID when the feature is updated and saved.	text	40		Yes

HydroAdd line schema, QC fields

Point QC field name	Field Description	Source	Notes	Field type	Length	Domain	Allows Nulls
GNIS_NAME	GNIS_NAME at network address. Populated by HydroAdd tool during manual addressing or Batch QC.	Populated by HydroAdd	♦ Can be pre-populated by the user prior to running Batch QC with HydroAdd. ♦ Batch QC will use the pre-existing GNIS_NAME for addressing if an NHD feature with a matching GNIS_NAME is available in the search tolerance.	text	65		Yes
GNIS_ID	GNIS_ID at network address. An QC optional field. If the field is present in the user's data, HydroAdd will populate it during manual addressing or Batch QC.	Populated by HydroAdd	♦ Can be pre-populated by the user prior to running Batch QC with HydroAdd. ♦ Optional field	text	10		Yes
SnapTolerance	User input. SnapTolerance is a buffer around the start and end points of the input line. Start and end points will snap to an NHDFlowline feature within the SnapTolerance only if both points are in SnapTolerance.	User input	♦ Both start and end point must be in SnapTolerance for the new line to draw ♦ If no NHDFlowlines are in the SnapTolerance, then InSnapTolereance = No, InQCTolerance = No, and QCApproved = No ♦ If MaxSnap <= SnapTolerance, then InSnapTolerance = YES	double			No
FromSnapDistance	Distance in meters of the From point of the original line feature to the From point of the newly addressed line feature.	Populated by HydroAdd	From refers to the upstream end of the flowline. In the NHD HR model, the flowlines go From upstream To downstream.	double			No
ToSnapDistance	Distance in meters of the To point of the original line feature to the To point of the newly addressed line feature.	Populated by HydroAdd	To refers to the downstream end of the flowline. In the NHD HR model, the flowlines go From upstream To downstream.	double			No
MaxSnap	The greater value of either FromSnapDistance or ToSnapDistance.	Populated by HydroAdd	♦ If MaxSnap <= SnapTolerance, then InSnapTolerance = YES ♦ Both start and end point must be in SnapTolerance for the new line to draw	double			No
InSnapTolerance	Indicates if MaxSnap is within the SnapTolerance.	Populated by HydroAdd	♦ If MaxSnap <= SnapTolerance, then ‎InSnapTolerance = YES ♦ Both start and end point must be in Snap Tolerance for the new line to draw	short	1	NoYes Domain	No
QCTolerance	User input. Maximum allowable distance in meters to approve snapped line feature. The QC tolerance is the maximum distance where the point is automatically approved.	User input	If MaxSnapDistance <= QCTolerance, then InQCTolerance = Yes	double			No
InQCTolerance	Indicates if MaxSnap is within QCTolerance	Populated by HydroAdd	♦ If no flowlines are within the SnapTolerance, then InQCTolerance = No, QCApproved = No, and InLengthChangeTolerance = No ♦ If MaxSnap <= QCTolerance, InQCTolerance = Yes	short	1	NoYes Domain	No
LengthChangeTolerance	User input. Percent length change acceptable during batch QC.	User input	If LengthChange <= LengthChangeTolerance, then InLengthChangeTolerance= Yes	double			No
LengthChange	Percent length change of new feature.	Populated by HydroAdd	Abs [length new feature - length original feature)/length original feature] * 100	double			No
InLengthChangeTolerance	Indicates if newly addressed line feature is within the LengthChangeTolerance.	Populated by HydroAdd	If LengthChange <= LengthChangeTolerance then InLengthTolerance=Yes	short	1	NoYes Domain	No
QCApproved	Indicates approval status.	Populated by HydroAdd	QCApproved = No means the user should manually QC the item in an editing queue	short	1	NoYes Domain	No