Polygon for Metadata

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title: Polygon for Metadata
This is a simple shapefile covering the Eastern CONUS. The file was created for ArcGIS 10(.1 Beta) Metadata testing. The fields are minimal (SHP_NAME, XMax, XMin, YMax, YMin) but the data underwent a simple transformation in order to see when ArcGIS incorporates the Geoprocessing information into its metadata. A shapefile is made up of at least four files: DBF, PRJ, SHP and SHX. Anything else is extra (SBN, SBX, XML).
  1. How should this data set be cited?

    Metadata, Geospatial, Unpublished material, Polygon for Metadata: Geospatial Metadata, Lexington, KY.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -98.782839
    East_Bounding_Coordinate: -63.931972
    North_Bounding_Coordinate: 51.274347
    South_Bounding_Coordinate: 23.261830

  3. What does it look like?

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

    Calendar_Date: 11-Oct-2011
    Currentness_Reference: ground condition

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

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

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

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

      • Area Chain (1)

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

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      UTM_Zone_Number: 16
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -87.0000
      Latitude_of_Projection_Origin: 0.0000
      False_Easting: 500000
      False_Northing: 0.0000

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

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.2572221.

  7. How does the data set describe geographic features?

    A four-cornered polygon with SHP_NAME, XMax, XMin, YMax, YMin and typical Esri fields.
    None, although Esri has standards which can be researched through support.esri.com.
    shapefile attributes
    Combination of user created and software created attribution (Source: ESRI and user)

    Name of the shapefile (Source: User)

    User has a large amount of freedom in creating shapefile name. Obvious exceptions of special characters apply.

    Easternmost bounding coordinate (Source: Shapefile geography.)

    Range of values
    Units:decimal degrees

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Geospatial Metadata

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

Why was the data set created?

This shapefile was created solely for testing ArcGIS Metadata creation and editing.

How was the data set created?

  1. From what previous works were the data drawn?

    US_DD (source 1 of 1)
    Photo Science, Inc., 2000, Shapefiles_DD.

    Type_of_Source_Media: stable-base material
    This shapefile was used to locate the eastern US so as not to have a realistic polygon instead of a polygon in the middle of nowhere.

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

    Date: 11-Oct-2011 (process 1 of 1)
    A polygon shapefile was created within ArcCatalog with a projection of UTM16. The file was added to a new ArcMap session. An edit session was started. US_DD was added. The projection of the map document was checked to make sure it was UTM16. A polygon was drawn over the eastern US. The edit session was closed. ArcMap was closed. Fields were added for the bounding coordinates and shapefile name. The shapefile name was automatically populated. The bounding coordinates were populated by taking the shapefile into FME. The resulting shapefile was reprojected from LL83 back to UTM16.

  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?

    This is just a test dataset. There are no omissions.

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

    Bounding coordinates were populated by reprojecting the data within FME and then reprojected within ArcCatalog. This is just a test!!!

How can someone get a copy of the data set?

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

Access_Constraints: None
Use_Constraints: None

Who wrote the metadata?

Last modified: 11-Oct-2011
Metadata author:
Geospatial Metadata
2151 Mackey Pike
Nicholasville, KY 40356

859-533-1872 (voice)

Monday through Friday 9:00 AM to 5:00 PM (Eastern Time) preferred.
Contact_Instructions: Please visit geospatialmetadata.com for more contact info.
Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

Generated by mp version 2.9.14 on Fri Jan 13 16:18:57 2012