(COVERAGE SITESALL -- add descriptive title)

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

Title: (COVERAGE SITESALL -- add descriptive title)

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!)

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:")

1. How should this data set be cited?

   (your name or agency/company), (yyyymmdd [pub/release date] or unpublished), (COVERAGE SITESALL -- add descriptive title): (example: Illinois State Geological Survey Circular) (example: USGS OFR 98-999), (publisher), (city,state).

   Online Links:

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

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -122.39638084

   East_Bounding_Coordinate: -121.12905265

   North_Bounding_Coordinate: 48.45715951

   South_Bounding_Coordinate: 47.35818039

3. What does it look like?

4. Does the data set describe conditions during a particular time period?

   Calendar_Date: (yyyymmdd)

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

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: (map)

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?

      This is a Point data set. It contains the following vector data types (SDTS terminology):

      • Point (3264)

   2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: State Plane Coordinate System

      State_Plane_Coordinate_System:

      SPCS_Zone_Identifier: 5601

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 39.725503125
      Ordinates (y-coordinates) are specified to the nearest 39.725503125
      Planar coordinates are specified in Feet

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is GRS1980.
      The semi-major axis of the ellipsoid used is 6378206.4.
      The flattening of the ellipsoid used is 1/294.98.
      

7. How does the data set describe geographic features?

   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

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • (your name or agency/company)

2. Who also contributed to the data set?

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

3. To whom should users address questions about the data?

   (your name here)
   (your organization here)
   (your position here)
   (your address here)
   (your city here), (your state here) (your zip here)
   (your country here)
   

   (phone) (voice)
   (fax) (FAX)
   (spwexm@spw38851.your.org)
   

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

1. From what previous works were the data drawn?

   (none) (source 1 of 1)

   (example: agency that created source map), (yyyymmdd), (example: source map title): (example: map series) (publication ID), (example: source map publisher), (city,state).

   Type_of_Source_Media: (mylar separate)

   Source_Scale_Denominator: (24000)

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

2. How were the data generated, processed, and modified?

   Date: (yyyymmdd) (process 1 of 2)

   (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.)

   Date: 31-Dec-2002 (process 2 of 2)

   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

3. What similar or related data should the user be aware of?

   (example: agency that created related data set), (yyyymmdd), (example: related data set title): (example: map series) (publication ID), (example: source map publisher), (city,state).

   Online Links:

   • (enter URL of related data set here)

1. How well have the observations been checked?

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

2. How accurate are the geographic locations?

   (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.)

3. How accurate are the heights or depths?

4. Where are the gaps in the data? What is missing?

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

5. How consistent are the relationships among the observations, including topology?

   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?)

Are there legal restrictions on access or use of the data?

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.")

1. Who distributes the data set? (Distributor 1 of 1)

   (your organization here)
   (distributor title here)
   (distributor address)
   (distributor city), (your state here) (zip)
   (your country here)
   

   (phone #) (voice)
   (distributor email)
   

   Contact_Instructions: (Contact via email)

2. What's the catalog number I need to order this data set?

3. What legal disclaimers am I supposed to read?

   (include your standard disclaimer here)

4. How can I download or order the data?

Dates:

Last modified: 31-Dec-2002
Last Reviewed: (yyyymmdd)
To be reviewed: (yyyymmdd)

Metadata author:

(your organization here)
c/o (your name here)
(your position here)
(your address here)
(your city here), (Your state here) (your zip here)
(your country here)

(phone) (voice)
(fax) (FAX)
(spwexm@spw38851.your.org)

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)