(COVERAGE SITESALL -- add descriptive title)

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: (your name or agency/company)

Publication_Date: (yyyymmdd [pub/release date] or unpublished)

Title: (COVERAGE SITESALL -- add descriptive title)

Edition: (Version x.x, December 31, 2002)

Geospatial_Data_Presentation_Form: (map)

Series_Information:

Series_Name: (example: Illinois State Geological Survey Circular)

Issue_Identification: (example: USGS OFR 98-999)

Publication_Information:

Publication_Place: (city,state)

Publisher: (publisher)

Online_Linkage:

(<URL:http://your.server.org/pathname/filename>)

Description:

Abstract:

(Please put an abstract describing the data set here.

This metadata template was created using fgdcmeta.aml. You can edit it using a text editor or a metadata editor such as xtme. You should check your edits using other metadata tools such as mp. Parentheses indicate where data are to be entered or contain suggested values for that field. Replace the statements in parentheses with your information. If you are not sure what to enter in a field, consult the FGDC Metadata Standard available at the URL below. You can also access this information using the xtme metadata editor menu choice Help->Element.

A text editor works well, but be careful to preserve indentation. Do not add text after a compound element heading. Any heading that is followed on the line below by an indented heading is a compound element heading, for example:

Compound_Element: This is a compound element heading. Simple_Element: This is a simple element heading.

Compound_Element: This is another compound element heading. Compound_Element: This is another compound element heading. Simple_Element: This is another simple element heading.

Add text only after a simple element heading. If the text will fit on the remainder of the line immediately after the heading, put it there, for example:

Compound_Element: This text is invalid and will be deleted by mp. Simple_Element: This single line of text is valid and will be kept.

If the text will require more than one line, place it on the line below the simple element heading, indented two spaces, for example:

Compound_Element: This text is invalid and will be deleted by mp. Simple_Element: This text is indented to go with the Simple_Element above. This entry requires more than one line.

When you use mp to generate an HTML document from your metadata file, most of the text will be re-formatted to paragraph style. Information such as tables or program code that you wish to preserve in its existing format should have a ">" symbol as the first character of the line, for example:

 This line will be tagged as preformatted text.

For more information on the FGDC standard, example metadata, and metadata tools, see: <URL:http://www.fgdc.gov/Metadata/Metadata.html>

Examining examples of existing metadata files is recommended!)

Purpose:

(Narrative describing the purpose of this data set, and perhaps a warning against inappropriate use of the data)

Supplemental_Information:

(Use this section to include information that does not have a place in the FGDC metadata standard.

This section should also be used to BRIEFLY summarize data sources and anything a user of the data should be aware of in a narrative form. This section, along with the "Abstract", "Purpose", and "Entity_and_Attribute_Overview" are probably the fields most accessible to humans [as opposed to search engines] so an overview is recommended.

However, details should be entered in the the metadata under the appropriate FGDC metadata elements, for example:

data sources "Lineage: -> Citation_Information" procedures "Lineage: -> Process_Step:" legal limitations "Purpose:, Use_Contraints:" Related Data Sets "Cross_References:" References "Lineage: -> Citation_Information" Review checks "Attribute_Accuracy:" "Completeness_Report:" "Positional_Accuracy:")

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: (yyyymmdd)

Currentness_Reference: (example: Not for use after December 1999.)

Status:

Progress: (Complete, In work, or Planned)

Maintenance_and_Update_Frequency: (As Needed, None Planned, Yearly, etc.)

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -122.39638084

East_Bounding_Coordinate: -121.12905265

North_Bounding_Coordinate: 48.45715951

South_Bounding_Coordinate: 47.35818039

Keywords:

Theme:

Theme_Keyword_Thesaurus: (your standard thesaurus or none)

Theme_Keyword: (keyword) (repeat this line for each keyword)

Place:

Place_Keyword_Thesaurus: (your standard thesaurus or none)

Place_Keyword: (keyword) (repeat this line for each keyword)

Access_Constraints:

(example: none or internal use only)

Use_Constraints:

(Any constraints on data use go here. For example, "Anyone who uses these data must cite [your organization]," or "These data are not to be used at scales greater than 1:500,000.")

Point_of_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: (your name here)

Contact_Organization: (your organization here)

Contact_Position: (your position here)

Contact_Address:

Address_Type: (mailing and physical address)

Address: (your address here)

City: (your city here)

State_or_Province: (your state here)

Postal_Code: (your zip here)

Country: (your country here)

Contact_Voice_Telephone: (phone)

Contact_Facsimile_Telephone: (fax)

Contact_Electronic_Mail_Address: (spwexm@spw38851.your.org)

Data_Set_Credit:

(This is an opportunity to acknowledge others who contributed to this work.)

Native_Data_Set_Environment:

Windows_NT, 5.0, Intel ARC/INFO version 8.1.2

Cross_Reference:

Citation_Information:

Originator: (example: agency that created related data set)

Publication_Date: (yyyymmdd)

Title: (example: related data set title)

Geospatial_Data_Presentation_Form: (map)

Series_Information:

Series_Name: (example: map series)

Issue_Identification: (publication ID)

Publication_Information:

Publication_Place: (city,state)

Publisher: (example: source map publisher)

Online_Linkage: (enter URL of related data set here)

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

(Description of accuracy of attribute information [example: elevation values] and methods used to measure the accuracy.)

Logical_Consistency_Report:

Point features present. (Description of logical consistency of data and how it was tested--for example, does every polygon have a label and are all polygons closed?)

Completeness_Report:

(Information about omissions, selection criteria, generalization, definitions used, and other rules used to derive the data set.)

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

(Description of the accuracy of the horizontal coordinates and methods used to test the accuracy. example: 95% of points plotted on mylar matched the source map within 1/50 inch.)

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: (example: agency that created source map)

Publication_Date: (yyyymmdd)

Title: (example: source map title)

Geospatial_Data_Presentation_Form: (map)

Series_Information:

Series_Name: (example: map series)

Issue_Identification: (publication ID)

Publication_Information:

Publication_Place: (city,state)

Publisher: (example: source map publisher)

Source_Scale_Denominator: (24000)

Type_of_Source_Media: (mylar separate)

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: (yyyymmdd)

Source_Currentness_Reference: (currentness text)

Source_Citation_Abbreviation: (none)

Source_Contribution: (example: contours from Fig. 4, page 25)

Process_Step:

Process_Description:

(free text describing processing step--the Process_Step field is to be repeated to describe each step. This example processing step description should be replaced with a real one.)

Process_Date: (yyyymmdd)

Process_Step:

Process_Description:

First draft of metadata created by spwexm using FGDCMETA.AML ver. 1.2 05/14/98 on ARC/INFO data set i:\pw\swm\proj\culvert\joined\sitesall

Process_Date: 20021231

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Point

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Point

Point_and_Vector_Object_Count: 3264

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: State Plane Coordinate System

State_Plane_Coordinate_System:

SPCS_Zone_Identifier: 5601

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 39.725503125

Ordinate_Resolution: 39.725503125

Planar_Distance_Units: Feet

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983

Ellipsoid_Name: GRS1980

Semi-major_Axis: 6378206.4

Denominator_of_Flattening_Ratio: 294.98

Entity_and_Attribute_Information:

Overview_Description:

Entity_and_Attribute_Overview:

(Please add free text below describing table columns: valid values, and data sources. If applicable, INFO table listings are included here for your convenience in generating this narrative. The leading ">" used below tells the "mp" program to treat the item listings as preformatted text.)

SITESALL.PAT:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  AREA                   4    12     F      3
    5  PERIMETER              4    12     F      3
    9  SITESALL#              4     5     B      -
   13  SITESALL-ID            4    10     B      -    SCSITEID
   17  SCCULCNT               4    10     I      -
   21  EASTING                8    16     F      3
   29  NORTHING               8    16     F      3
   37  CULDBID                4    10     I      -
   41  DBSITEID               4    10     B      -
   45  ESA_BASINS-ID          4     5     B      -
   49  WRIA                   2     2     I      -
   51  WTRSHDID               4     5     B      -
   55  CNTYID                 4    10     I      -
   59  TOWNSHIP               2     2     I      -
   61  RANGE                  2     2     I      -
   63  SECTION                2     2     I      -

Entity_and_Attribute_Detail_Citation: none

Distribution_Information:

Distributor:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: (your organization here)

Contact_Position: (distributor title here)

Contact_Address:

Address_Type: mailing and physical address

Address: (distributor address)

City: (distributor city)

State_or_Province: (your state here)

Postal_Code: (zip)

Country: (your country here)

Contact_Voice_Telephone: (phone #)

Contact_Instructions: (Contact via email)

Contact_Electronic_Mail_Address: (distributor email)

Distribution_Liability:

(include your standard disclaimer here)

Metadata_Reference_Information:

Metadata_Date: 20021231

Metadata_Review_Date: (yyyymmdd)

Metadata_Future_Review_Date: (yyyymmdd)

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: (your organization here)

Contact_Person: (your name here)

Contact_Position: (your position here)

Contact_Address:

Address_Type: mailing and physical address

Address: (your address here)

City: (your city here)

State_or_Province: (Your state here)

Postal_Code: (your zip here)

Country: (your country here)

Contact_Voice_Telephone: (phone)

Contact_Facsimile_Telephone: (fax)

Contact_Electronic_Mail_Address: (spwexm@spw38851.your.org)

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Access_Constraints: none

Metadata_Use_Constraints: none