Recommended contiguous band of natural lands and wildlife-compatible farmlands

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. Where did the data come from?
  2. What changes have been made?
• 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:

Recommended contiguous band of natural lands and wildlife-compatible farmlands

Abstract:

Areas along the San Joaquin Valley's edges within which a contiguous band of natural lands and wildlife-compatible farmlands should be maintained.

1. How should this data set be cited?

   Endangered Species Recovery Program, 1999, Recommended contiguous band of natural lands and wildlife-compatible farmlands: Endangered Species Recovery Program, Fresno, CA, US.

   Online Links:

   • <http://arnica.csustan.edu/esrpp>

   Other_Citation_Details:

   U.S. FWS, 1998 Recovery Plan for Upland Species of the San Joaquin Valley, California.

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -122.151

   East_Bounding_Coordinate: -118.497

   North_Bounding_Coordinate: 38.1722

   South_Bounding_Coordinate: 34.7784

3. What does it look like?

   cont_band.jpg (JPEG)

   Graphic of theme cont_band

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

   Calendar_Date: 1994

   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.

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

      Grid_Coordinate_System_Name: Universal Transverse Mercator

      Universal_Transverse_Mercator:

      UTM_Zone_Number: 10

      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.9996

      Longitude_of_Central_Meridian: -123

      Latitude_of_Projection_Origin: 0

      False_Easting: 500000

      False_Northing: 0

      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 1927.
      The ellipsoid used is Clark 1866.
      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:

   All closed polygon features are attributed as being within the contiguous band. Polygon features contain an attribute cont_band that is a single digit integer with valid values of 0 and 1. Those lands that make up the band are attributed as 1.

   Entity_and_Attribute_Detail_Citation: Endangered Species Recovery Program, 1996

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

2. Who also contributed to the data set?

   Daniel F. Williams Ellen A. Cypher Patrick A. Kelly Nancy Norvell Scott E. Phillips

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

   Endangered Species Recovery Program
   GIS Analyst
   
   
   US
   

   (voice)
   559 453 1227 (FAX)
   gis@esrp.org
   

   Contact_Instructions: Contact by electronic or postal mail

Created for Figure 73. San Joaquin Valley conservation and recovery planning overview of the Recovery Plan for Upland Species of the San Joaquin Valley.

1. Where did the data come from?

   GAPVEG (source 1 of 1)

   University of California, Santa Barbara Biogeography Lab, 1996, California Gap Analysis Land Cover Map, draft version, 1996.: University of California, Santa Barbara Biogeography Lab, Santa Barbara, CA, US.

   Online Links:

   • <http://www.biogeog.ucsb.edu>

   Type_of_Source_Media: online

   Source_Scale_Denominator: 250000

   Source_Contribution:

   The locations of non-native grassland and scrub communities outside the areas of irrigated agriculture, but within the San Joaquin Valley, Carrizo Plain, and upper Cuyama Valley

2. What changes have been made?

   Date: 1996 (change 1 of 1)

   Dan Williams of ESRP choose the locations for the coverage features based on the vegetation and land use types. Nancy Norvell of ESRP created the polygon features in ARC/INFO based on the locations selected by Dan Williams.

   Person responsible for change:
   

   Endangered Species Recovery Program
   GIS Analyst
   
   
   US
   

   (voice)
   559 453 1227 (FAX)
   gis@esrp.org
   

   Contact_Instructions: Contact by electronic or postal mail

1. How well have the observations been checked?

   All polygon features are attributed as being within the band.

2. How accurate are the geographic locations?

   The locations of polygon features are generalized based on a regional view of the source information. The accuracy of this theme is not suitable for parcel level mapping.

3. How accurate are the heights or depths?

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

   The locations of lands are generized and are not based on real property locations.

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

   Arcs connect to each other at nodes. Arcs have direction and left and right sides. Arcs that connect to surround an area define a polygon.

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

Access_Constraints: none

Use_Constraints:

None. Acknowledgement of the Endangered Species Recovery Program would be appreciated in products derived from this data.

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

   Endangered Species Recovery Program
   GIS Analyst
   
   
   US
   

   (voice)
   559 453 1227 (FAX)
   gis@esrp.org
   

   Contact_Instructions: Contact by electronic or postal mail

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

   ARC Export file of cont_band

3. What legal disclaimers am I supposed to read?

   No warranty, expressed or implied is made by the ESRP regarding the utility of the data, nor shall the act of distribution constitute any such warranty. These data are geographic illustrations and do not represent legal boundaries.

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	ARCE (version 7.2.1) no compression
     Network links:	<http://www.esrp.org/gis/>

   • Cost to order the data: Data may be accessed online without charge.

5. What hardware or software do I need in order to use the data set?

   computer with software to import ARC/INFO GIS data

Dates:

Last modified: 30-Jun-1999

Metadata author:

Endangered Species Recovery Program
GIS Analyst


US

(voice)
559 453 1227 (FAX)
gis@esrp.org

Contact_Instructions: Contact by electronic or postal mail

Metadata standard:

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