Sixth/Seventh Field Hydrologic Units for the CLAMS Area

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: Zoe Rickenbach,Sharon Clarke,Kelly Burnett

Publication_Date: 20000530

Title: Sixth/Seventh Field Hydrologic Units for the CLAMS Area

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Corvallis, OR

Publisher: Forest Science Data Bank

Other_Citation_Details: none

Online_Linkage: http:\\www.fsl.orst.edu\clams

Description:

Abstract:

Nested 6th and 7th code Hydrologic Units (HU) were produced for the Coastal Landscape Analysis and Modeling Study (CLAMS). Preliminary 6th code HU were produced using the USGS GIS Weasel program with 10m Drainage Enforced-Digital Elevation Models (DE-DEM). These boundaries were hand edited to remove very small Basins. In an effort to conform to existing and ongoing efforts, the boundaries were given to the USFS and BLM for review. Working with the BLM and FS we produced both a 6th and 7th code HU coverage combining our original lines, their lines, and digitizing new lines where necessary. We discussed discrepancies in boundaries with the Salem, Eugene, Coos Bay, and Roseburg districts of the Bureau of Land Management(BLM) and Siuslaw National Forest (SNF). The final 6th and 7th code HUs are attributed with: 1)unique identifiers, 2) corresponding 5th code HU code number (7th codes HU have the corresponding 6th code HUnumber as well), 3) 4th and 5th code HU names, and 4)codes to differentiate between true, composite and frontal watersheds. Basins meet the National Resource Conservation Service's guidelines for 6th code HUs.

Purpose:

To provide a 6th/7th field HU coverage for the CLAMS area, for use in natural resource research, management planning and regional ecology studies on both public and private lands.

Supplemental_Information:

Procedures_Used:

Revisions: This is version one. Reviews_Applied_to_Data: Data reviewed by Chester Novak, Kirk Appleman (Salem BLM); Barb Ellis-Sugai (USFS-SNF); Mary D'Aversa (Eugene BLM); Dan Carpenter, Lance Finnegan (Coos Bay BLM); Rick Momsen, Lowell Duell (Roseburg BLM); and Sharon Clarke, Alissa Moses (OSU),

References: USGS GIS Weasel (<http://wwwbrr.cr.usgs.gov/weasel/>) 10m Drainage Enforced Digital Elevation Models (DE-DEM) (<http://www.reo.gov/dem/ore>) (<http://www.averstar.com/news/dedem.html>) Coastal Landscape Analysis and Modeling Study (CLAMS) (<http://www.fsl.orst.edu/clams/>) Fifth field HUC (<http://www.sscgis.state.or.us/data/themes.html>) Digital Raster Graphics (DRG) (<http://mcmcweb.er.usgs.gov/drg/>) 1:24,000 Hydrology Digital Line Graphs (DLG) (<http://edcwww.cr.usgs.gov/doc/edchome/ndcdb/ndcdb.html>) USFS Interagency Guideline on Delineation of Watershed and Subwatershed Hydrologic Unit Boundaries (<http://wwwga.usgs.gov/gis/iag.html>) Mapping and Digitizing Watershed and Subwatershed Hydrologic Unit Boundaries (<http://www.nhq.nrcs.usda.gov/hu/ni170304.html>)

Time_Period_of_Content:

Time_Period_Information:

Range_of_Dates/Times:

Beginning_Date: 1999

Ending_Date: 2000

Currentness_Reference: available data

Status:

Progress: Complete

Maintenance_and_Update_Frequency: Irregular

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -124.658569

East_Bounding_Coordinate: -122.379229

North_Bounding_Coordinate: 46.237790

South_Bounding_Coordinate: 42.539380

Keywords:

Theme:

Theme_Keyword_Thesaurus: None

Theme_Keyword: sixth field watersheds

Theme_Keyword: seventh field watersheds

Theme_Keyword: watersheds

Theme_Keyword: 6th field watersheds

Theme_Keyword: 7th field watersheds

Theme_Keyword: DE-DEM

Theme_Keyword: gis weasel

Theme_Keyword: HU

Theme_Keyword: basins

Theme_Keyword: 6th code HU

Theme_Keyword: 7th code HU

Theme_Keyword: sixth code HU

Theme_Keyword: seventh code HU

Theme_Keyword: Hydrologic Unit

Theme_Keyword: CLAMS

Place:

Place_Keyword_Thesaurus: None

Place_Keyword: CLAMS Area

Place_Keyword: Coastal Landscape Analysis and Modeling Study

Place_Keyword: Coast Range of Oregon

Place_Keyword: Oregon

Stratum:

Temporal:

Access_Constraints: none

Use_Constraints:

Notify CLAMS when distributing any work based on or derived from original CLAMS data. Inform recipients of your derived work that it is not original CLAMS data. Do not redistribute original data. Cite Sharon Clarke/Kelly Burnett unpublished data in published work. We would appreciate a copy of any publication that cites our data. Please send to: Sharon Clarke, Forestry Sciences Lab, 3200 Jefferson Way, Corvallis OR 97331

Point_of_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Kelly Burnett

Contact_Organization: USDA Forest Service

Contact_Position: Fish Biologist

Contact_Address:

Address_Type: mailing and physical address

Address: Forestry Sciences Laboratory, 3200 Jefferson Way

City: Corvallis

State_or_Province: OR

Postal_Code: 97331

Country: USA

Contact_Voice_Telephone: 541-750-7309

Contact_Electronic_Mail_Address: kmburnett@fs.fed.us

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report: no test for accuracy was preformed

Logical_Consistency_Report:

No logical inconsistencies were detected using the Arc/Info BUILD command

Completeness_Report:

Fifth code basins were done in the CLAMS area, with the exception of 1710030212 (Ollala Creek/Lookingglass Creek). HUs were not made for this 5th code because it flows into the South Fork of the Umpqua River which is outside of the CLAMS area. Fifth codes that straddled the boundary were only completed for the CLAMS area.

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report: no estimate of horizontal accuracy

Vertical_Positional_Accuracy:

Vertical_Positional_Accuracy_Report: does not apply

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: USGS

Publication_Date: 1999

Title: DE-DEM

Geospatial_Data_Presentation_Form: grid

Publication_Information:

Publication_Place: Oregon

Publisher: Avastar

Type_of_Source_Media: electronic files

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 1999

Source_Currentness_Reference: publication date

Source_Citation_Abbreviation: DE-DEM

Source_Contribution: elevation data

Process_Step:

Process_Description:

Complete 6th and 7th code HU coverage for the CLAMS area was non-existent. For some of the federal ownership where HU data was available, the data was inconsistent; created by different agencies for different purposes. Our goal was to produce consistent HUs, incorporating existing work. We used the USGS GIS Weasel program with 10m Drainage Enforced-Digital Elevation Models (DE-DEM) to produce a Hydrologic Unit(HU) coverage for the Coastal Landscape Analysis and Modeling Study (CLAMS) area. Where possible, the watersheds were generated by 4th code HU using a threshold value of 110,000 pixels (1100 ha). Initially, several different threshold values were evaluated to determine an appropriate range of drainage areas and to ensure that basins from the automated process approximated the basins hand drawn by the Eugene BLM and Siuslaw NF using 1:24K topographic maps. We hand edited the boundaries of the computer-delineated basins to: 1) eliminate any polygons less than 1000 square meters, 2) adjust HUs that were too small (<600 ha) or too large (> 6000 ha), 3) match them to existing 5th code HUs boundaries, unless the 5th codes were incorrect, and 4) delineate 6th code HUs for small coastal basins including basins draining into the Columbia River, where computer generated basins were hydrologically incorrect. For basins smaller than 600 ha, 100k stream names were used to choose which adjacent HU to merge with the >600 ha HU. To reduce the size of HU larger than 6000 ha, additional HU boundary lines were screen digitized using contours shown on Digital Raster Graphics (DRG) to identify ridgelines. Additionally, we hand drew hydrologic unit boundaries for some of the smaller coastal basins where running the GIS Weasel program was inefficient and prone to errors. It is difficult for the GIS Weasel to differentiate between low gradient terrestrial areas and estuaries or the ocean on the DEMs. Consequently, the mouth of coastal HUs frequently were a series of parallel lines extending to the limit of the DEM coverage. A coverage identifying the coastline and bays was needed as a boundary for our HU. Because we were unable to locate a ""standard"" coastline coverage and we wanted the boundary line to match our 10m DEM, we generated a coastline coverage from the 10m DE-DEM. Using the Arc/Info Grid command contour, contours were made starting at zero. The contour coverage was edited in ArcEdit to eliminate contours that were not 0 and any islands. The resulting coastline coverage was added to the HU coverage and the coastal HUs were hand edited to this boundary. We worked with agencies that had existing HUs to produce a coverage that incorporated their boundaries while maintaining consistency throughout the CLAMS area. This improved the mostly computer-generated lines with human decision making skills. Using the computer generated lines provided some consistency and were faster to produce than hand-drawn lines. Our intention was to produce a coverage that was acceptable for both theirs and our use. Because the starting point was different for each agency or district, our methods had to be flexible to incorporate their existing work. The 5th code HU coverage provided an organization structure for editing. Both the Forest Service and BLM owned lands in some 5th codes. They either worked together in these areas or defaulted to the other agency. Following is a description of the methods we used on a case by case basis. SALEM BLM The draft HU coverage was given to the Salem BLM for their review. In comparing it to some of their preliminary 6th and 7th code HUs, they found that our size range from 600-6000 ha, straddled their 6th (4000-16,000) and 7th (800-4000) HU size ranges. To maximize the utility of our work for other groups and provide flexibility for our research it was worth the effort to develop both a 6th and 7th code HU coverage from our draft coverage. Through a series of interactive meetings, the Salem BLM used our draft HUs and identified ""concept lines"". These were lines that were screen digitized using only streams for guidance. These ""concept lines"" provided further delineations to our draft lines to make 7th code HU. They also identified groups of adjacent 7th code HUs to merge into one 6th code HU. We made topographically correct basins from their ""concept lines"" by digitizing along ridgetops shown on the DRGs. In addition, they provided lines for Washington County, an area where the 10m DE-DEMs from which to generate draft 6th codes were non-existent. EUGENE BLM Concurrently with our efforts, the Eugene BLM was hand drawing 6th code HU boundaries on 1:24,000 topographic maps and digitizing these lines. During our initial editing phase where we adjusted HUs that were too small or large, we used their linework for guidance. Then, we compared their lines with our draft 6th code lines and met to resolve areas of difference. The Eugene BLM participated in the meetings to create both a 6th and 7th code coverage. They provided us with hand drawn paper maps to further subdivide the draft 6th codes coverage into 7th code HU and to identify groups of 7th code HU to be combined into a 6th code HU. We digitized their lines and coded the 7th code HU groupings. SIUSLAW NATIONAL FOREST (SNF) The SNF had delineated 6th code HU for various purposes for their watersheds. They had specific areas where they wanted to keep their lines. The SNF reviewed our draft 6th code lines and we met to resolve areas of concern. As with the Eugene BLM, they participated in meetings to create both a 6th and 7th code HU coverage. COOSBAY and ROSEBURG BLM Both of these districts had existing 6th and 7th code HU coverages that had some inconsistencies. We used their 7th code lines to further subdivide our draft 6th code HU and their 6th code HU delineations for aggregating our draft HUs. In the process we tried to fix some of the inconsistencies and any errors we found. Our adjusted lines were shown to them for review. New basins and any adjustments were made taking several things into account: 1)maximize the number of true watersheds wherever possible, 2)make basin outlets at tributary junctions by matching the basin to the stream layer that the DE-DEM was enforced to (e.g. if the DE-DEM was enforced to the 1:24,000 hydrology Digital Line Graphs(DLG) then we would match the basin outlet to the DLG tributary junction.), 3)all streams flowing into a tributary junction should be contained within the basin, unless the tributary was a large enough to be a true watershed on its own, and 4)where possible, draw a HU across a stream to match the outlet of the HU on the opposite bank.

Each 7th code HU was coded with a 6th code HU number to identify which adjacent 7th code HUs to combine. To do this, the BLM and SNF contributed paper maps, concept lines, or 7th codes HUs coverage attributed with a 6th code HU number. On occasion a sixth code was small and further subdivision was inappropriate. So the 7th code polyon is the same as the 6th code polygon. A 6th code coverage can be created from the 7th code coverage by merging adjacent polygons with the same 6th code number using the Arc/Info command dissolve. Each polygon was attributed with 4th and 5th code HU name, complete 5th code HU number, 6th code number, 7th code number and watershed type-true/composite/frontal for both the 6th and 7th code HUs.

Process_Date: 200005

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\DOCUME~1\olsenk\LOCALS~1\Temp\xml28.tmp

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Complete chain

Point_and_Vector_Object_Count: 6787

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Label point

Point_and_Vector_Object_Count: 1662

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains

Point_and_Vector_Object_Count: 1662

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Point

Point_and_Vector_Object_Count: 138

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: Universal Transverse Mercator

Universal_Transverse_Mercator:

UTM_Zone_Number: 10

Transverse_Mercator:

Scale_Factor_at_Central_Meridian: 0.999600

Longitude_of_Central_Meridian: -123.000000

Latitude_of_Projection_Origin: 0.000000

False_Easting: 500000.000000

False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.003725

Ordinate_Resolution: 0.003725

Planar_Distance_Units: meters

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1927

Ellipsoid_Name: Clarke 1866

Semi-major_Axis: 6378206.400000

Denominator_of_Flattening_Ratio: 294.978698

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: basin67_po.aat

Entity_Type_Definition: Polygon Attribute Table

Entity_Type_Definition_Source: software generated

Attribute:

Attribute_Label: FID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 0

Range_Domain_Maximum: no limit

Attribute_Units_of_Measure: METERS^2

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: FNODE#

Attribute_Definition: Internal node number for the beginning of an arc (from-node).

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Whole numbers that are automatically generated.

Attribute:

Attribute_Label: TNODE#

Attribute_Definition: Internal node number for the end of an arc (to-node).

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 0

Range_Domain_Maximum: no limit

Attribute_Units_of_Measure: METERS

Unrepresentable_Domain: Whole numbers that are automatically generated.

Attribute:

Attribute_Label: LPOLY#

Attribute_Definition: Internal node number for the left polygon.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: c

Enumerated_Domain_Value_Definition: Composite watershed

Enumerated_Domain_Value_Definition_Source:

any watershed with an inlet and an outlet with the exception of Frontals (see below)

Enumerated_Domain:

Enumerated_Domain_Value: t

Enumerated_Domain_Value_Definition: True watershed

Enumerated_Domain_Value_Definition_Source: A watershed with only one outlet.

Enumerated_Domain:

Enumerated_Domain_Value: f

Enumerated_Domain_Value_Definition: Frontal watershed

Enumerated_Domain_Value_Definition_Source:

A watershed that has more then one outlet (e.g. a watershed along the ocean or the Columbia River)

Unrepresentable_Domain: Whole numbers that are automatically generated.

Attribute:

Attribute_Label: RPOLY#

Attribute_Definition: Internal node number for the right polygon.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: HU Code

Codeset_Source:

USGS/EPA <http://www.sscgis.state.or.us/data/themes.html>

Unrepresentable_Domain: Whole numbers that are automatically generated.

Attribute:

Attribute_Label: LENGTH

Attribute_Definition: Length of feature in internal units.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: c

Enumerated_Domain_Value_Definition: Composite watershed

Enumerated_Domain_Value_Definition_Source:

any watershed with an inlet and an outlet with the exception of Frontals (see below)

Enumerated_Domain:

Enumerated_Domain_Value: t

Enumerated_Domain_Value_Definition: True watershed

Enumerated_Domain_Value_Definition_Source: A watershed with only one outlet.

Enumerated_Domain:

Enumerated_Domain_Value: f

Enumerated_Domain_Value_Definition: Frontal watershed

Enumerated_Domain_Value_Definition_Source:

A watershed that has more then one outlet (e.g. a watershed along the ocean or the Columbia River)

Unrepresentable_Domain: Positive real numbers that are automatically generated.

Attribute:

Attribute_Label: BASIN67_PO#

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: HU Code

Codeset_Source: USGS/EPA <http://www.sscgis.state.or.us/data/themes.html>

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: BASIN67_PO-ID

Attribute_Definition: User-defined feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: HU Code

Codeset_Source: USGS/EPA <http://www.sscgis.state.or.us/data/themes.html>

Attribute:

Attribute_Label: Watershed

Attribute_Definition: The complete fifth field HUC number.

Attribute_Definition_Source: User Defined

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: HU Code

Codeset_Source:

USGS/EPA <http://www.sscgis.state.or.us/data/themes.html>

Attribute:

Attribute_Label: Watershed_name

Attribute_Definition: Fifth field HUC name

Attribute_Definition_Source: User Defined

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: HU code

Codeset_Source: USGS/EPA <http://www.sscgis.state.or.us/data/themes.html>

Detailed_Description:

Entity_Type:

Entity_Type_Label: basin67_po.pat

Attribute:

Attribute_Label: FID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: AREA

Attribute_Definition: Area of feature in internal units squared.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Positive real numbers that are automatically generated.

Attribute:

Attribute_Label: PERIMETER

Attribute_Definition: Perimeter of feature in internal units.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Positive real numbers that are automatically generated.

Attribute:

Attribute_Label: BASIN67_PO#

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: BASIN67_PO-ID

Attribute_Definition: User-defined feature number.

Attribute_Definition_Source: ESRI

Attribute:

Attribute_Label: SEVTYPE

Attribute:

Attribute_Label: WATERSHED

Attribute:

Attribute_Label: SIXTH_FIELD

Attribute:

Attribute_Label: SEVENTH_FIELD

Attribute:

Attribute_Label: SUBBASIN_NAME

Attribute:

Attribute_Label: WATERSHED_NAME

Attribute:

Attribute_Label: SIXTYPE

Attribute:

Attribute_Label: SUB_WATERSHED

Distribution_Information:

Distributor:

Contact_Information:

Contact_Person_Primary:

Contact_Person: CLAMS Webmaster

Contact_Organization: CLAMS

Contact_Address:

Address_Type: mailing address

Address: 3200 Jefferson Way

City: Corvallis

State_or_Province: OR

Postal_Code: 97331

Country: USA

Contact_Voice_Telephone: (541) 750-7279

Contact_Facsimile_Telephone: (541) 750-7760

Contact_Electronic_Mail_Address: clamsweb@fsl.orst.edu

Hours_of_Service: 8 am - 5 pm

Resource_Description: Downloadable Data

Distribution_Liability:

Although these data have been processed successfully at the U.S.D.A Forest Service (FS), no warranty expressed or implied is made regarding the accuracy or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use of the data. It is strongly recommended that these data be directly acquired from an FS server, and not directly through other sources, which may have changed the data in some other way. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. FS shall not be held liable for improper or incorrect use of the data described and/or contained herein.

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Format_Name: ARCE

Format_Version_Number: ArcInfo 7.2.1

File_Decompression_Technique: No compression applied

Transfer_Size: 28.159

Digital_Transfer_Option:

Online_Option:

Computer_Contact_Information:

Network_Address:

Network_Resource_Name: <http://www.fsl.orst.edu/clams/>

Access_Instructions: Anonymous FTP

Fees: none

Ordering_Instructions: Obtain data at <http://www.fsl.orst.edu/clams/>

Turnaround: Less than 1 hour

Metadata_Reference_Information:

Metadata_Date: 20060814

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: CLAMS

Contact_Person: CLAMS Webmaster

Contact_Address:

Address_Type: mailing address

Address: 3200 Jefferson Way

City: Corvallis

State_or_Province: OR

Postal_Code: 97331

Country: USA

Contact_Voice_Telephone: (541) 750-7279

Contact_Facsimile_Telephone: (541) 758-7760

Contact_Electronic_Mail_Address: clamsweb@fsl.orst.edu

Hours_of_Service: 8 am - 5 pm

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile