RGIS::ce0ded5a-0764-4c39-b7bc-5b796d43cdc1::ISO-19115:2003 eng; USA Linda Branch New Mexico National Resource Conservation Service State Office (505) 761-4438 6200 Jefferson NE, Suite 305 Alburquerque New Mexico 87109 Linda.Branch@nm.usda.gov Please email questions and requests. pointOfContact 2014-06-16 ISO 19115 Geographic Information - Metadata ISO 19115 3231 3233 3232 4 United States North American Datum of 1983 revision http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 resourceProvider 4269 Geodetic Reference System 80 revision http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:ellipsoid:EPSG::7019 resourceProvider 7019 New Mexico 6th Code Subwatersheds (12-digit) 2009-07-20T00:00:00 publication Downloadable Data New Mexico Natural Resources Conservation Service State Office (NRCS) originator U.S. Department of Agriculture, Natural Resources Conservation Service Fort Worth Texas publisher This data set is a complete digital hydrologic unit boundary layer to the Subwatershed (12-digit) 6th level for the State of New Mexico. This data set consists of geo-referenced digital data and associated attributes created in accordance with the "FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02"(http://www.ftw.nrcs.usda.gov/huc_data.html). Polygons are attributed with hydrologic unit codes for 4th level sub-basins, 5th level watersheds, 6th level subwatersheds, name, size, downstream hydrologic unit, type of watershed, non-contributing areas and flow modification. Arcs are attributed with the highest hydrologic unit code for each watershed, linesource and a metadata reference file. The Watershed and Subwatershed hydrologic unit boundaries provide a uniquely identified and uniform method of subdividing large drainage areas. The smaller sized 6th level sub-watersheds (up to 250,000 acres) are useful for numerous application programs supported by a variety of local, State, and Federal Agencies. This data set is intended to be used as a tool for water-resource management and planning activities, particularly for site-specific and localized studies requiring a level of detail provided by large-scale map information. The dataset will be appended to a larger seamless nationally consistant geospatial database as other states complete their portion of the watershed boundary dataset. The dataset was created by the U.S. Geological Survey (USGS) in Utah, along with the U.S. Geological Survey in New Mexico, with full funding, cooperation, and oversight provided by the Natural Resources Conservation Service (NRCS) in New Mexico. All generated linework and attribution was reviewed and approved by NRCS in New Mexico along with other in state interagency partners. Linda Branch New Mexico National Resource Conservation Service State Office (505) 761-4438 6200 Jefferson NE, Suite 305 Alburquerque New Mexico 87109 Linda.Branch@nm.usda.gov Please email questions and requests. HUC Hydrologic Units Hydrologic Unit Code Region Sub-region Basin Sub-basin Watershed Watershed Boundaries boundaries Subwatershed WBD Watershed Boundary Dataset None New Mexico USA None Access Constraints: None. Use Constraints: The distributor shall not be held liable for improper or incorrect use of this data, based on the description of appropriate/inappropriate uses described in this metadata document. It is strongly recommended that this data is directly acquired from the distributor and not indirectly through other sources which may have changed the data in some way. These data should not be used at scales greater than 1:24,000 for the purpose of identifying hydrographic watershed boundary feature locations in New Mexico. The NRCS should be acknowledged as the data source in products derived from these data. The New Mexico Watershed Boundary Dataset is public information and may be interpreted by all organizations, agencies, units of government, or others based on needs; however, they are responsible for the appropriate application of the data. Federal, State, or local regulatory bodies are not to reassign to the Natural Resources Conservation Service any authority for the decisions they make. The Natural Resources Conservation Service will not perform any evaluations of these maps or purposes related solely to State or local regulatory programs. Photographic or digital enlargement of these maps to scales greater than that at which they were originally delineated can result in misrepresentation of the data. If enlarged, the maps will not include the fine detail that would be appropriate for mapping at the small scale. Digital data files are periodically updated. Files are dated, and users are responsible for obtaining the latest version of the data from the source distributor. eng; USA inlandWaters Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.3000 -109.054553 -103.001961 31.332172 37.072479 ground condition true Entity and Attribute Information http 1) .pat attributes Huc_8 : Eight Digit Hydrologic Unit Code - (REQUIRED) A unique 8-digit code from the USGS map series "Hydrologic Unit Maps". The same number was used in every record that pertains to a subwatershed that resides within the same 8-digit sub-basin.Numbers were assigned in an upstream to downstream fashion. Where no downstream/upstream relationship could be determined numbers were assigned in a clockwise fashion. Huc_10: Ten Digit Hydrologic Unit Code - (REQUIRED) This field provides a unique 10-digit code for each watershed. This same number was used in every record that pertains to a subwatershed that resides within the same 10-digit watershed. Numbers were assigned in an upstream to downstream fashion. Where no downstream/upstream relationship could be determined numbers were assigned in a clockwise fashion. Huc_12: Twelve Digit Hydrologic Unit Code - (REQUIRED) This field provides a unique 12-digit code for each subwatershed. Numbers were assigned in an upstream to downstream fashion. Where no downstream/upstream relationship could be determined numbers were assigned in a clockwise fashion. Acres: Acres - (REQUIRED) Area of subwatershed including non-contributing areas calculated to acres as a whole number, no decimals. The "Acres" field was calculated from the "Area" field. States: States - (REQUIRED) The "States" field includes the names of all state(s) that the subwatershed falls within. The 2-digit postal abbreviation in upper case and in alphabetical order was used, separated with a comma. Ncontrb_a: Non-Contributing Area - (FIELD REQUIRED, ATTRIBUTES OPTIONAL) Drainage areas that do not flow toward the outlet of any hydrologic unit are considered non-contributing. If a non-contributing area is on the boundary between two or more hydrologic units, the non-contributing area is associated with the hydrologic unit adjacent to the low point on the boundary. This attribute should be the total of the non-contributing areas within a hydrologic unit calculated in acres. Hu_10_ds: Fifth Level Downstream Hydrologic Unit Code - (FIELD REQUIRED, ATTRIBUTES OPTIONAL) This field has the 10-digit code of the 5th level hydrologic unit that is receiving the majority of the flow from the watershed that the 6th level HU falls within. Outlets created by ditching or other artificial drainage were not considered for this field. If an HU flows into an ocean or the Gulf of Mexico, this field was populated with "OCEAN" and if a HU flows into one of the Great Lakes the term "LAKE" was used. If a HU flows across international borders, "CANADA" or "MEXICO" was used depending on which country the HU drains into. If an HU is a closed basin, then the term "CLOSED BASIN"was used. Hu_10_name: Fifth Level Hydrologic Unit Name - (FIELD REQUIRED, ATTRIBUTES OPTIONAL) This field used officially recognized names only. This field was populated by following the directions in subsection 6.3 "Watershed and Subwatershed Naming Protocol". The name used to attribute the watershed was used only once within a 4th level unit. Hu_10_mod: Fifth Level Hydrologic Unit Modifications - (REQUIRED) This field identifies any type of modifications to natural overland flow that alters the location of the hydrologic unit boundary for a 10-digit watershed. This field shows the most significant to least significant modification(s) to the watershed boundary. One or more of the following abbreviations was used. SC - Stormwater Canal ID - Irrigation Ditch IT - Interbasin Transfer BC - Barge Canal SD - Stormwater Ditch PD - Pipe Diversion CD - Channel Diversion NC - Non-Contributing Area KA - Karst LE - Levee NM - No Modifications OC - Overflow Channel DM - Dam at outlet or HU boundary GC - General Canal PS - Pumping Station DD - Drainage Ditch AD - Aqueduct RS - Reservoir TF - Transportation Feature (road, railroad, docks etc.) GF - Ground Water Flow MA - Mining Activity UA - Urban Area OT - Other Hu_10_type: Fifth Level Hydrologic Unit Type - (REQUIRED) Populate this field with the hydrologic unit type from the list provided that most closely identifies the watershed. Use any of the one-digit abbreviations in uppercase that is provided in the list. S - "Standard" hydrologic unit - Any land HU with drainage flowing to a single outlet point, excluding non-contributing areas. This includes areas or small triangular wedges between adjacent HU's that remain after classic hydrologic units are delineated. Some examples include "true", "classic", "composite", and "remnant" hydrologic units. C - "Closed Basin" hydrologic unit - A drainage area that is 100% non-contributing. This means all surface flow is internal, no overland flow leaves the hydrologic unit through the outlet point. F - "Frontal" hydrologic unit - Areas along the coastline of lakes, oceans, bays, etc. that have more than one outlet. These HU's are predominantly land with some water areas at or near the outlet(s). W - "Water" hydrologic unit - Hydrologic units that are predominantly water with adjacent land areas, ex. lake, easturies, harbors. I - "Island" hydrologic unit - A hydrologic unit that is one or more islands and adjacent water out to the toe of the shore face. U - "Unclassified" hydrologic unit - A hydrologic unit that can't be defined or doesn't fit into one of the types that have been listed. Hu_12_ds: Sixth Level Downstream Hydrologic Unit Code - (FIELD REQUIRED, ATTRIBUTES OPTIONAL) Populate this field with the 12-digit code of the 6th level hydrologic unit that is receiving the majority of the flow from the subwatershed. Outlets created by ditching or other artificial drainage are not to be considered for this field. If a HU flows into an ocean or the Gulf of Mexico populate this field with "OCEAN" and if a HU flows into one of the Great Lakes use the term "LAKE". If a HU flows across international borders use "CANADA" or "MEXICO" depending on which country the HU drains into. If an HU is a closed basin, then populate this record with the term "CLOSED BASIN". Hu_12_name: Sixth Level Hydrologic Unit Name - (FIELD REQUIRED, ATTRIBUTES OPTIONAL) This field is for officially recognized names only. Populate this field by following the directions in subsection 6.3 "Watershed and Subwatershed Naming Protocol". The name used to attribute the subwatershed should be used only once within a 6th level unit. Some 10-digit HU were assigned the huc_12 number when no GNIS name was identified on the DRG-Es. Hu_12_mod: Sixth Level Hydrologic Unit Modifications - (REQUIRED) This field should identify any type of modifications to natural overland flow that alters the location of the hydrologic unit boundary for a 12-digit subwatershed. In the attribute field, identify from most significant to least significant modification(s). Use one or more of the following abbreviations in uppercase to identify your modification(s). If using more than one abbreviation, separate with a comma with no space after the comma. SC - Stormwater Canal ID - Irrigation Ditch IT - Interbasin Transfer BC - Barge Canal SD - Stormwater Ditch PD - Pipe Diversion CD - Channel Diversion NC - Non-Contributing Area KA - Karst LE - Levee NM - No Modifications OC - Overflow Channel DM - Dam at outlet or HU boundary GC - General Canal PS - Pumping Station DD - Drainage Ditch AD - Aqueduct RS - Reservoir TF - Transportation Feature (road, railroad, docks etc.) GF - Ground Water Flow MA - Mining Activity UA - Urban Area OT - Other Hu_12_type: Sixth Level Hydrologic Unit Type - (REQUIRED) Populate this field with the hydrologic unit type from the list provided that most closely identifies the subwatershed. Use any of the one digit abbreviations in uppercase that is provided in the list. S - "Standard" hydrologic unit - Any land HU with drainage flowing to a single outlet point, excluding non-contributing areas. This includes areas or small triangular wedges between adjacent HU's that remain after classic hydrologic units are delineated. Some examples include "true", "classic", "composite", and "remnant" hydrologic units. C - "Closed Basin" hydrologic unit - A drainage area that is 100% non-contributing. This means all surface flow is internal, no overland flow leaves the hydrologic unit through the outlet point. F - "Frontal" hydrologic unit - Areas along the coastline of lakes, oceans, bays, etc. that have more than one outlet. These HU's are predominantly land with some water at or near the outlet(s). W - "Water" hydrologic unit - Hydrologic units that are predominantly water with adjacent land areas, ex. lake, easturies. I - "Island" hydrologic unit - A hydrologic unit that is one or more islands and adjacent water out to the toe of the shore face. U - "Unclassified" hydrologic unit - A hydrologic unit that can't be defined or doesn't fit into one of the types that have been listed. HU_10_GNIS#: 5th level GNIS Feature Identification Number - (Field Required, Attribute Optional) The Geographic Names Information System (GNIS) has a unique Feature Identification Number for each officially recognized name in the country. This number is 6-7 characters long. If a hydrologic unit name uses two or mure features, then this field woudl have two GNIS feature numbers with a space separating each number. As of August, 2004 this field does not need to be populated, but plans are to develope a semi_automated method to do this. HU_12_GNIS#: 6th level GNIS Feature Identification Number - (Field Required, Attribute Optional) The Geographic Names Information System (GNIS) has a unique Feature Identification Number for each officially recognized name in the country. This number is 6-7 characters long. If a hydrologic unit name uses two or mure features, then this field woudl have two GNIS feature numbers with a space separating each number. As of August, 2004 this field does not need to be populated, but plans are to develope a semi_automated method to do this. ArcInfo (.pat) and ArcView Polygon Format Item name Width Output Type (ArcView) N.Dec. Example Huc_8 8 8 C - 01080201 Huc_10 10 10 C - 0108020103 Huc_12 12 12 C - 010802010310 Acres 8 12 F N 0 026739 States 11 11 C - KS,MO,OK Ncontrb_a 8 12 F N 0 357 Hu_10_ds 10 10 C - 1710020504 Hu_10_name 80 80 C - Upper Blue River Hu_10_mod 20 20 C - CB,NC,ID Hu_10_type 1 1 C - S Hu_12_ds 12 12 C - 171002050402 Hu_12_name 80 80 C - Drift Creek-Big Bear River Hu_12_mod 20 20 C - SD,KA,PD Hu_12_type 1 1 C - C HU_10_GNIS# 23 23 C - 102354 238437 HU_12_GNIS# 23 23 C - 1023547 2384378 2) .aat attributes Hu_level: Hydrologic Unit Level - (REQUIRED) This field provides the means to create cartographically pleasing maps. Populate this field with the highest hydrologic unit level (smallest number) for the line (arc) represented by the record. Record the level using numbers 1 through 6 representing each level with 1 being the highest and 6 the lowest level. An example would be if a line represents a region, subregion, basin, subbasin, watershed, and subwatershed boundary, then this cell would be populated with a 1 (Region). Example two would be if a line is a subbasin, watershed, and subwatershed boundary, then the cell would get a 4 (Subbasin). Use one of the levels provided in the list below. Level Digit# Name 1 2 Region 2 4 Subregion 3 6 Basin 4 8 Subbasin 5 10 Watershed 6 12 Subwatershed Linesource: Line Spatial Data Source - (REQUIRED) The Linesource should indicate the base map source(s) used to delineate at 1:24,000 scale. Populate the field using one of the standardized code(s) listed below in uppercase. If using more than one code, separate with a comma with no space after the comma. TOPO24 - Delineation from hardcopy 1:24,000 scale topographic maps TOPO25 - Delineation from hardcopy 1:25,000 topgraphic maps, only Alaska and Caribbean TOPO63 - Delineation from hardcopy 1:63,360 topographic maps, only Alaska and Caribbean DRG24 - Delineation from 1:24,000 scale Digital Raster Graphics DRG25 - Delineation from 1:25,000 Digital Raster Graphics, only Alaska and Caribbean DRG63 - Delineation from 1:63,360 Digital Raster Graphics, only Alaska and Caribbean DEM10 - Derived from 10 meter Digital Elevation Model DEM30 - Derived from 30 meter Digital Elevation Model NED30 - Derived from 30 meter National Elevation Dateset Model EDNA30 - (formally NED-H), derived from 30 meter Elevation Derivatives for National Applications BATH"scale" (ex. BATH24) - Interpreted from NOAA 1:24,000 scale bathymetric data HYPSO"scale" (ex. HYPSO24)- Delineated from 1:24,000 scale contour data ORTHO"scale" (ex. ORTHO12) - Interpreted from 1:12,000 scale Ortho-imagery DEDEM10 - Drainage enforced 10 meter Digital Elevation Model DEDEM30 - Drainage enforced 30 meter Digital Elevation Model GPS - Derived from Global Positioning System LIDAR - Derived from LIDAR IFSAR - Derived from IFSAR data OTH - Other UNK - Unknown All other reference and source maps not listed should be noted in the metadata. Meta_id: Metadata ID Number - (REQUIRED) Metadata ID is a code that identifies which metadata file applies to the arc. In many cases there will only be one metadata file. However, in some cases more than one metadata file may be created to identify different groups and/or procedures used to produce the lines. These separate metadata files may be identified for each separate arc. The metadata ID should be a 4-character code starting with the 2-letter state postal code, followed by a 2-digit sequence number. For example "OK01", "ID02", etc. ArcInfo Line (.aat) Attribute Format Item name Width Output Type N.Dec. Example Hu_level 1 1 I - 6 Linesource 20 20 C - DEM30,DRG24,GPS Meta_id 4 4 C - OK01 Federal Standard for Delineation of Hydrologic Unit Boundaries Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu ZIP 159 http://gstore.unm.edu/apps/rgisarchive/datasets/ce0ded5a-0764-4c39-b7bc-5b796d43cdc1/nm_huc12shp.original.zip http://gstore.unm.edu/apps/rgisarchive/datasets/ce0ded5a-0764-4c39-b7bc-5b796d43cdc1/nm_huc12shp.original.zip http://gstore.unm.edu/apps/rgisarchive/datasets/ce0ded5a-0764-4c39-b7bc-5b796d43cdc1/metadata/FGDC-STD-001-1998.xml http://gstore.unm.edu/apps/rgisarchive/datasets/ce0ded5a-0764-4c39-b7bc-5b796d43cdc1/metadata/FGDC-STD-001-1998.html http://gstore.unm.edu/apps/rgisarchive/datasets/ce0ded5a-0764-4c39-b7bc-5b796d43cdc1/metadata/ISO-19115:2003.xml http://gstore.unm.edu/apps/rgisarchive/datasets/ce0ded5a-0764-4c39-b7bc-5b796d43cdc1/metadata/ISO-19115:2003.html There are no unclosed polygons, intersections without nodes, or polygons without labels or with more than one label. Arc/Info's topological checking program CLEAN was used to correct intersections without nodes, identify unclosed polygons and remove duplicate lines with the same beginning and ending nodes. All sliver polygons were removed either using eliminate, merge or manually in ArcEdit. General subwatershed boundaries were created using EDNA30. These general raster lines were used as reference lines for on-screen digitizing 2003-01-01T00:00:00 EROS Linework was digitized to 24k map accuracy standards using the DRG's as the official base map as outlined in the standard. DOQQs were used as a reference in extreme manmade altered areas that reflected permanent change, namely along the Rio Grande. It was agreed upon initially between the NRCS and USGS that this would be the process. The resolution of all linework was completed in accordance with the National Standards for Spatial Data Accuracy (NSSDA). All 1:24,000 meter scale linework was generated digitally on screen inside of Arcmap. The initial scope of work divided the state into 6 areas for interim delivery to NRCS for review. NRCS in turn would post for in state coordinating agencies review for a pre-determined period of time. Comments on suggested edits were provided back to USGS for inclusion into the dataset after compilation and acceptance by NRCS. 2004-01-01T00:00:00 USGSDRG Edgematching with Arizona and Utah was straight forward as those datasets are stable. At this time there was no data to edgematch with across the Mexico border. Oklahoma was coordinated with and provided their dataset which was mostly complete. Texas also provided their dataset and agreed at some juncture to extend the linework shown on the New Mexico side of the border, where the Texas portion was above the acceptable size limit for subdivision. Colorado is edgematched as closely as possible at this time. It is assumed that Colorado will dissolve out small polygons, and estimations were made as to where those would best be implemented in order to edgematch as best as possible the linework and attribution across the border. Colorado borders are not currently being work on. 2004-01-01T00:00:00 Linework was digitized to 24k map accuracy standards using the DRG's as the official base map as outlined in the standard. DOQQs were used as a reference in extreme manmade altered areas that reflected permanent change, namely along the Rio Grande. It was agreed upon initially between the NRCS and USGS that this would be the process. The resolution of all linework was completed in accordance with the National Standards for Spatial Data Accuracy (NSSDA). All 1:24,000 meter scale linework was generated digitally on screen inside of Arcmap. The initial scope of work divided the state into 6 areas for interim delivery to NRCS for review. NRCS in turn would post for in state coordinating agencies review for a pre-determined period of time. Comments on suggested edits were provided back to USGS for inclusion into the dataset after compilation and acceptance by NRCS. 2004-01-01T00:00:00 USGSDOQ Edgematching with Arizona and Utah was straight forward as those datasets are stable. At this time there was no data to edgematch with across the Mexico border. Oklahoma was coordinated with and provided their dataset which was mostly complete. Texas also provided their dataset and agreed at some juncture to extend the linework shown on the New Mexico side of the border, where the Texas portion was above the acceptable size limit for subdivision. Colorado is edgematched as closely as possible at this time. It is assumed that Colorado will dissolve out small polygons, and estimations were made as to where those would best be implemented in order to edgematch as best as possible the linework and attribution across the border. Colorado borders are not currently being work on. 2004-01-01T00:00:00 Upon completion of all linework, attribution was performed statewide on the dataset by USGS in Utah, and delivered to NRCS for review and comment. Comments have been addressed and incorporated. 2004-01-01T00:00:00 First draft of metadata created by kjones using FGDCMETA.AML ver. 1.2 05/14/98 on ARC/INFO data set h:\wbd\edgematching_shapefiles\final\metadata\nm\nm_hu12_geo83 2005-08-11T00:00:00 hydrologic unit map delineation and digitize map 24000 Digital Raster Graphic USGSDRG U.S. Geological Survey map delineation 1999-01-01 ARCView coverages for creation of raster lines 30 EDNA (EDNA30) Elevation Derivitives for National Applications-Stage 2 package EROS EROS Data Center publication date GIS raster coverage used for reference in watershed boundary delineation 24000 Digital Orthophoto Quads USGSDOQ U.S. Geological Survey publication date Reference for 8-digit watershed delineation 250000 250K Hydrologic Unit Boundaries USGS2 U.S. Geological Survey ground condition GIS coverage used for reference in watershed boundary delineation 24000 National Hydrography Dataset NHD U.S. Geological Survey map delineation Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT custodian