Rhode Island Natural Heritage Database

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

Title: Rhode Island Natural Heritage Database
Abstract:
Rhode Island, in collaboration with NatureServe, maintains a database of rare and imperiled species and plant communities. The data is maintained in a relational MS Access based geodatabase. Spatial data consists of polygon representations of rare plant, animal, and natural community locations in Rhode Island. This data was mapped by the Rhode Island Natural Heritage Program and Rhode Island Natural History Survey Staff between 1978 and 2004. The file enables the user to identify locations of rare and endangered species populations and occurrences of exemplary or unique natural ecosystems (terrestrial and palustrine) and special wildlife habitats. Due to its dynamic nature, this data becomes outdated very quickly. The RINHS MUST be contacted before each use of this data set to ensure its currency. The RINHS MUST be contacted in writing prior to distribution or hardcopy output of this data layer. This data is available statewide and is current to its release date.
Supplemental_Information:
The RINHS maintains an extensive relational database system in MS Access containing detailed information on the status of populations and species or natural communities. In addition, a wide range of literature related to the state's biota and hardcopy filed records are available.
  1. How should this data set be cited?

    REQUIRED: The name of an organization or individual that developed the data set., Rhode Island Natural Heritage Program, and Rhode Island Natural History Survey, Unknown, Rhode Island Natural Heritage Database: Rhode Island Natural History Survey, Kingston, Rhode Island.

    Online Links:

    • \\Odonata\rinhs_database\HeritageDbase\HeritageGDB.mdb

    This is part of the following larger work.

    Rhode Island Natural History Survey, Unknown, Biota of Rhode Island Project.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -71.900344
    East_Bounding_Coordinate: -71.008527
    North_Bounding_Coordinate: 42.664161
    South_Bounding_Coordinate: 41.090730

  3. What does it look like?

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

    Beginning_Date: 1978
    Ending_Date: 1912
    Currentness_Reference: publication date

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

      • G-polygon (1829)

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

      Grid_Coordinate_System_Name: State Plane Coordinate System 1983
      State_Plane_Coordinate_System:
      SPCS_Zone_Identifier: 3800
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999994
      Longitude_of_Central_Meridian: -71.500000
      Latitude_of_Projection_Origin: 41.083333
      False_Easting: 328083.333333
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000512
      Ordinates (y-coordinates) are specified to the nearest 0.000512
      Planar coordinates are specified in survey feet

      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.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: National Geodetic Vertical Datum of 1929
      Altitude_Resolution: 0.000010
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    HeritageEORep

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    ID

    EOCODE
    Unique record identifier for locational data (element occurrence code) used in Heritage methodology. The EOCODE is formed from: ELCODE*EONUM*SUBNATION. (Source: NatureServe - Heritage methodology)

    Alphanumeric code used as unique identifier (record key) for each Element Occurrence by NatureServe in Heritage methodology.

    NOTES
    Notes related to how polygon was digitized, etc.

    Notes field.

    BCD_PREC
    Precision BCD - A code for the precision used to map the Element Occurrence (EO) on a U.S. Geological Survey (USGS) 7.5? (or 15?) topographic quadrangle map, based on the previous Heritage methodology in which EOs were located on paper maps using dots. (Source: NatureServe - Heritage methodology)

    ValueDefinition
    SSeconds: accuracy of locality mappable within a three-second radius.
    MMinutes: accuracy within a one-minute radius, approximately 2 km or 1.5 miles from centriod of the EO.
    GGeneral: precision within 8 km or 5 miles, or to quad or place name.
    UUnmappable

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape_Length
    Length of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    Shape_Area
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    BufferDist

    RepAcc

    RecordAdded

    Confidence_extent

    Loc_uncert_dist

    Loc_uncert_units

    RepAcc_Comments


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?

    Locations in this dataset were mapped by staff of the Rhode Island Natural Heritage Program and the Rhode Island Natural History Survey.

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

    Rhode Island Natural History Survey
    c/o Erik Endrulat
    Data Manager
    Rm. 101, Coastal Institute in Kinston
    Kingston, RI 02881-0804
    USA

    401-874-5822 (voice)
    401-874-4561 (FAX)
    eendrulat@rinhs.org

    Hours_of_Service: 8-5 PM, EST


Why was the data set created?

This dataset is intended to provide a baseline dataset for element occurance locations in Rhode Island. species and ecological communities that are rare or otherwise imperiled. Uses of the data can include: natural resource management, conservation planning, environmental review, biological and ecological research, land acquisition, and economic development. Through aggregation of the EO data at regional, national, or range-wide scales, these data can be used to examine broad patterns and set priorities in a global context.


How was the data set created?

  1. From what previous works were the data drawn?

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

    (process 1 of 3)
    Dataset copied.

    Data sources used in this process:

    • D:\gis\Workspace\eo_poly_merge

    (process 2 of 3)
    Metadata imported.

    Data sources used in this process:

    • D:\projects\natureserve\2004DataExchange\Metadata\eo_poly_metadata.xml

    (process 3 of 3)
    Metadata imported.

    Data sources used in this process:

    • H:\HeritageDbase\data\gis_data\vector\eo_poly.shp.xml

  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?

    Approximately 75% of the element occurances tracked by the RINHP have been mapped and are contained in this dataset. Approximately 350 element occurence records are deemed 'unmappable' and thus are not reflected in the spatial dataset. These records often contain locality identifiers down to only the quad, county, or town level.

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

    Using ESRI's ARC/INFO GIS software, the data set was 'cleaned' for polygons using the "build" command. Topology has not been edited since the last build or clean.


How can someone get a copy of the data set?

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

Access_Constraints:
Use of data in the Rhode Island Natural Heritage Database is accessible under the terms of the Data Sharing Agreement between the Rhode Island Natural History Survey and Natureserve. Access constraints are considered on a case by case basis.
Use_Constraints:
Use of data in the Rhode Island Natural Heritage Database is accessible under the terms of the Data Sharing Agreement between the Rhode Island Natural History Survey and Natureserve. Due to the dynamic nature of the information, the data is only intended for use within a year of a data exchange, after which it is out-dated and its use should be discontinued. Data is intended for use at a scale of 1:24,000.

LIMITATIONS OF ABSENCE OF DATA Although numerous biological inventories have been conducted and as much of the secondary source data as possible has been assembled, the majority of the state has never been systematically surveyed for rare species or natural communities. In addition, negative surveys are seldom reported to the RINHS and are not recorded. The database reflects only locations where an element was once known to occur. It does not distinguish between areas known to have no elements and those that have not been checked. The absence of element location cannot be taken as an indication of absence of elements or of ecological concerns.

  1. Who distributes the data set?[Distributor contact information not provided.]

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 03-Apr-2006
Metadata author:
REQUIRED: The organization responsible for the metadata information.
c/o REQUIRED: The person responsible for the metadata information.
REQUIRED: The city of the address., REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address.

REQUIRED: The telephone number by which individuals can speak to the organization or individual. (voice)

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.8.6 on Mon Apr 03 13:28:06 2006