|
|
Boundary FAQ Metadata
Frequently-anticipated questions:
What does this data set describe?
- Title:
-
Approved Acquisition Boundary for Ouray National Wildlife Refuge
- Abstract:
-
National Wildlife Refuges are federal lands managed by the U.S. Fish and Wildlife Service (USFWS). Data used to locate this boundary was obtained from the USFWS Realty program.
- Supplemental_Information: NA
- How should this data set be cited?
U.S. Fish & Wildlife Service, Refuges & Wildlife, Region 6, Division , 200302, Approved Acquisition Boundary for Ouray National Wildlife Refuge.
Online Links:
- What geographic area does the data set cover?
- West_Bounding_Coordinate: -109.678
- East_Bounding_Coordinate: -109.565
- North_Bounding_Coordinate: 40.204
- South_Bounding_Coordinate: 40.093
- Description_of_Geographic_Extent: Ouray National Wildlife Refuge and environs
- What does it look like?
- Does the data set describe conditions during a particular time period?
- Calendar_Date: Feb-2003
- Currentness_Reference: Research of Region 6 Realty files
- What is the general form of this data set?
- Geospatial_Data_Presentation_Form: Map
- How does the data set represent geographic features?
- How are geographic features stored in the data set?
This is a Vector data set.
- What coordinate system is used to represent geographic features?
- Grid_Coordinate_System_Name: Universal Transverse Mercator
- Universal_Transverse_Mercator:
-
- UTM_Zone_Number: 12
- Transverse_Mercator:
-
- Scale_Factor_at_Central_Meridian: .9996
- Longitude_of_Central_Meridian: -111
- 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 .001
Ordinates (y-coordinates) are specified to the nearest .001
Planar coordinates are specified in meters
The horizontal datum used is NAD27.
The ellipsoid used is Clarke 1866.
The semi-major axis of the ellipsoid used is 6,378,206.4.
The flattening of the ellipsoid used is 1/294.98.
- How does the data set describe geographic features?
- Entity_and_Attribute_Overview: USFWS National Wildlife Refuge Approved Acquisition Boundary
- Entity_and_Attribute_Detail_Citation:
-
An approved acquisition boundary as it applies to Region 6 and to the digital legislative boundary set forth in 97-01, U.S. Fish and Wildlife Service Lands Boundary Data Standard Operating Procedure (SOP) is defined as an area that is approved for acquisition into a National Wildlife Refuge; it may also include lands that have been acquired by fee, lease, easement, agreement, and permit, etc.. See SOP under "Labeling Files and Geographic Features - Legislative Boundary" (in process 1) for information on arc and polygon items and item values. Polygon items in addition to those referenced in the SOP include: ARC_ACRES (replaces SOP ACREAGE item), REC_ACRES and METHOD (these two items are no longer considered applicable, and therefore are not populated; however, the items are being retained to maintain consistency with coverages created previously that contain these items). There is an aat-item named METHOD which contains a code for the method of arc creation; a code Dig-DRG indicates an arc digitized from the DRG or created using ArcEdit construction methods on DRG-digitized lines; a code of e indicates an arc that was extrapolated (using the DRG as a reference) to match the Realty Status Map.
Who produced the data set?
- Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
- U.S. Fish & Wildlife Service, Refuges & Wildlife, Region 6, Division of Realty
- Who also contributed to the data set?
- To whom should users address questions about the data?
USGS-NPS Vegetation Mapping Program Coordinator
U.S. Geological Survey, Center for Biological Informatics, MS 302, Room 8000, Building 810, Denver Federal Center
Denver, Colorado 80225
USA
(303) 202-4220 (voice)
(303) 202-4219 (FAX)
gs-b-npsveg@usgs.gov
Why was the data set created?
The intended application of the data is to serve as a spatial reference of refuge boundaries for other data layers in GIS and mapping applications. It is specifically not intended to be used as a land survey or representation of land for conveyance or tax purposes.
How was the data set created?
- From what previous works were the data drawn?
- None (source 1 of 2)
-
U.S. Fish & Wildlife Service, Refuges and Wildlife, Region 6, Divisio, unknown, Various information from Division of Realty.
- Type_of_Source_Media: Paper
- Source_Contribution:
-
Used to determine the current location and extent of the approved acquisition boundary. A document summarizing the specific information used to determine the extent of the approved acquisition boundary is on file in Region 6 Realty (document location: Refuges/RE, LA-Utah, Ouray NWR, General folder 1993 - ).
- DRG (source 2 of 2)
-
U.S. Geological Survey, unknown, 7.5 Minute Topographical Quadrangle(s) for the area covered by Ouray National Wildlife Refuge approved acquisition boundary..
- Type_of_Source_Media: Digital Raster Graphics (DRGs)
- Source_Contribution: Features on the DRG were digitized to create the boundary.
- How were the data generated, processed, and modified?
- Date: Feb-2003 (process 1 of 1)
-
An empty ArcInfo coverage was created; the fuzzy tolerance was set to .001, and the coverage was built for network topology; arc and polygon items required by the project were added; features were screen-digitized from the DRG, and arc and polygon items were populated; the projection was defined, and the coverage was rebuilt and run through quality control steps. Even though the Green River is included in the area delineated by the approved acquisition boundary, it has not been determined whether this should be the case.
- What similar or related data should the user be aware of?
How reliable are the data; what problems remain in the data set?
- How well have the observations been checked?
Arc and polygon item values are rechecked by data entry staff for omissions and against the original data for accuracy.
- How accurate are the geographic locations?
Digital boundary was overlain on USGS 7.5 minute topo. quad(s) (DRG). Data are stored in ArcInfo double precision.
- How accurate are the heights or depths?
- Where are the gaps in the data? What is missing?
Arcs that represent the entire approved acquisition boundary were included. Line work was checked for omissions.
- How consistent are the relationships among the observations, including topology?
The digital boundary was compared to source material for completeness. Software capabilities were used to ensure arcs have no dangling nodes and intersection errors and to check polygons for label errors.
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:
-
Refuge boundary data were compiled for resource applications. It is inappropriate to use this data in legal situations, or other applications where spatial error cannot exceed the USGS 7.5' mapping standards. This data is specifically not intended to be used as a land survey or representation of land for conveyance or tax purposes. An approved acquisition boundary delineates an area that has been approved for inclusion into a National Wildlife Refuge. However, approval does not necessarily indicate that the entire area inside this boundary has been (or ever will be) acquired by U.S. Fish and Wildlife Service.
- Who distributes the data set? (Distributor 1 of 1)
USGS Center for Biological Informatics
USGS-NPS Vegetation Mapping Program Coordinator
United States Geological Survey, Center for Biological Informatics
Denver, Colorado 80225
USA
303 202-4220 (voice)
303 202-4219 (FAX)
gs-b-npsveg@usgs.gov
- What's the catalog number I need to order this data set?
Digital data were compiled for use in NPS decision making.
- What legal disclaimers am I supposed to read?
The U.S. Geological Survey and the National Park Service shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics (i.e., GIF or JPG format files) are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data.
The U.S. Geological Survey and the National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on computer systems at the U.S. Geological Survey and the National Park Service, no warranty expressed or implied is made regarding the utility of the data on other systems for general or scientific purposes, nor shall the act of distribution constitute any such warranty. this disclaimer applies both to individual use of the data and aggregate use with other data.
- How can I download or order the data?
- Availability in digital form:
- Cost to order the data: None
Who wrote the metadata?
- Dates:
- Last modified: Feb-2003
Last Reviewed: 06-Nov-2007
- Metadata author:
-
USGS-NPS Vegetation Mapping Program Coordinator
U.S. Geological Survey, Center for Biological Informatics, MS 302,
Room 8000, Building 810, Denver Federal Center
Denver, Colorado 80225
USA
(303) 202-4220 (voice)
(303) 202-4219 (FAX)
gs-b-npsveg@usgs.gov
- Metadata standard:
- FGDC-STD-001.1-1999 Content Standard for Digital Geospatial Metadata, 1998 Part 1: Biological Data Profile, 1999 (FGDC-STD-001-1998)
- Metadata extensions used:
-
Generated by mp version 2.7.24 on Tue Nov 06 13:18:24 2007
|