<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Computer Terrain Mapping, Inc.</origin>
<pubdate>2005</pubdate>
<title>Alpine Loop Landscape-Based Conservation Priorities</title>
<geoform>map</geoform>
</citeinfo>
</citation>
<descript>
<abstract>
The Alpine Loop Landscape-Based Conservation Priorities (LBCP) data set
shows the combination of the resource value mapping and the development
potential mapping.

The conservation priorities are referred to as landscape-based
because they focus predominantly on the naturally occurring
systems - i.e., topographic, vegetative, geologic, etc
parameters - largely separate from the human imposed land
ownership pattern.

Resource value and development potential are combined to form
the landscape-based conservation priorities.  These are areas
of the landscape with high conservation value that are likely
to be developed without violating building constraints and local
government regulations.  Note that at this point, development
potential has not been restricted to private parcels.

The results of the landscape-based analysis are then combined
with the land ownership pattern to define the overall
conservation priorities.
</abstract>
<purpose>
The Alpine Loop Spatial Analysis and Mapping Project inventoried
natural and cultural resources and identified important areas where
overlapping resources occur.  The results from this project will
provide an opportunity for area stakeholders - landowners, outdoor
enthusiasts, surrounding communities, federal government agencies
and local and national preservation groups - to come together to
find solutions that maintain the Alpine Loop experience for future
visitors and residents, while working within the framework of
landowner objectives as well as local and federal government goals.

The Alpine Loop Spatial Analysis and Mapping Project analyzed the
Alpine Loop landscape, considering important natural and cultural
resources along with the likelihood of development based upon
building constraints.  The Project aims to provide a planning tool
for area stakeholders as they consider the variety of land
management options and the future of this magnificent region.  The
next logical step will be to craft solutions that work within the
framework of landowner desires, local and federal government land
management goals, and available financial and technical resources
to manage the area in a way that preserves the Alpine Loop
experience for future generations.

While the Alpine Loop lies within three counties - San Juan,
Hinsdale and Ouray - the analytical work extended into a portion
of San Miguel County.  The resulting mapping and analyses will:

1. Create a spatial foundation to aid future projects in the
Alpine Loop corridor;

2. Serve as a prioritization tool for evaluating the
conservation potential of individual private parcels;

3. Provide the necessary framework for pursuing future
funding opportunities.
</purpose>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>2003</begdate>
<enddate>2005</enddate>
</rngdates>
</timeinfo>
<current>
Data were retrieved from various sources and analyzed between 2003
and 2005.  See Data Quality Information for time information for
source data.
</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>None Planned</update>
</status>
<spdom>
<bounding>
<westbc>-107.8725478</westbc>
<eastbc>-107.2256611</eastbc>
<northbc>38.08819806</northbc>
<southbc>37.73515861</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Conservation</themekey>
<themekey>Resources</themekey>
<themekey>Development</themekey>
<themekey>Priorities</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>United States</placekey>
<placekey>North America</placekey>
<placekey>Colorado</placekey>
<placekey>San Juan Mountains</placekey>
<placekey>Ouray County</placekey>
<placekey>San Juan County</placekey>
<placekey>Hinsdale County</placekey>
<placekey>San Miguel County</placekey>
<placekey>Ouray</placekey>
<placekey>Silverton</placekey>
<placekey>Lake City</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>None.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Computer Terrain Mapping, Inc.</cntorg>
<cntper>Ed Russell</cntper>
</cntorgp>
<cntpos>President</cntpos>
<cntaddr>
<addrtype>mailing</addrtype>
<address>PO Box 4982</address>
<city>Boulder</city>
<state>CO</state>
<postal>80306</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303.444.1670</cntvoice>
<cntfax>303.443.4856</cntfax>
<cntemail>ctm@ctmap.com</cntemail>
<hours>8:00-5:00 MT</hours>
</cntinfo>
</ptcontac>
<datacred>
This data set is the product of a collaborative process between numerous
agencies, organizations and interested individuals from the beautiful
Alpine Loop region.
</datacred>
<native>GRASS version 5 on Red-Hat Linux version 8.0 exported to an ASCII Grid</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>
LBCP was determined from a variety of data sources
of unknown accuracy.
</attraccr>
</attracc>
<logic>
Data are calculated from a variety of data sources of unknown accuracy.
Only basic spot checking based on knowledge of terrain was performed.
</logic>
<complete>LBCP was calculated for the entire study area.</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Computer Terrain Mapping, Inc.</origin>
<pubdate>2005</pubdate>
<title>Alpine Loop Conservation Resource Value</title>
<geoform>Map</geoform>
</citeinfo>
</srccite>
<typesrc>digital</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>2003</begdate>
<enddate>2005</enddate>
</rngdates>
</timeinfo>
<srccurr>Data were retrieved from various sources and analyzed between 2003 and 2005.</srccurr>
</srctime>
<srccitea>Conservation Resource Value</srccitea>
<srccontr>Intrinsic conservation value of an area.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Computer Terrain Mapping, Inc.</origin>
<pubdate>2005</pubdate>
<title>Alpine Loop Development Potential</title>
<geoform>Map</geoform>
</citeinfo>
</srccite>
<typesrc>digital</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>2003</begdate>
<enddate>2005</enddate>
</rngdates>
</timeinfo>
<srccurr>Data were retrieved from various sources and analyzed between 2003 and 2005.</srccurr>
</srctime>
<srccitea>Development Potential</srccitea>
<srccontr>
Generalized development potential for an area, that is, suitability
for residential development.
</srccontr>
</srcinfo>
<procstep>
<procdesc>
After adjustments for differences in the total range of values for the
conservation resource value and development potential maps, these were
combined to form the landscape-based conservation priorities. To
emphasize management toward resource protection, we assigned the
resource value map twice the weight as the development potential map
(i.e., we multiplied the resource map by two before adding the
development potential map).  The result contained 81 categories, with
higher values representing higher priorities.
</procdesc>
<srcused>Conservation Resource Value</srcused>
<srcused>Development Potential</srcused>
<procdate>2004</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Raster</direct>
<rastinfo>
<rasttype>Grid Cell</rasttype>
<rowcount>1256</rowcount>
<colcount>1863</colcount>
</rastinfo>
</spdoinfo>
<spref>
<horizsys>
<planar>
<gridsys>
<gridsysn>Universal Transverse Mercator</gridsysn>
<utm>
<utmzone>13</utmzone>
<transmer>
<sfctrmer>.9996</sfctrmer>
<longcm>-105 00 00</longcm>
<latprjo>00 00 00</latprjo>
<feast>500000</feast>
<fnorth>0</fnorth>
</transmer>
</utm>
</gridsys>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>30.0</absres>
<ordres>30.0</ordres>
</coordrep>
<plandu>METERS</plandu>
</planci>
</planar>
<geodetic>
<horizdn>North American Datum of 1983 (NAD83)</horizdn>
<ellips>GRS 1980</ellips>
<semiaxis>6378137</semiaxis>
<denflat>298.257222101</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>LBCP grid cell</enttypl>
<enttypd>Any of the data elements in the LBCP map</enttypd>
<enttypds>author</enttypds>
</enttyp>
<attr>
<attrlabl>LBCP grid cell value</attrlabl>
<attrdef>
LBCP values varies between 0 and 81.  Higher values represent higher
conservation priority.
</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<rdom>
<rdommin>0</rdommin>
<rdommax>81</rdommax>
</rdom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Computer Terrain Mapping, Inc.</cntorg>
<cntper>Ed Russell</cntper>
</cntorgp>
<cntpos>President</cntpos>
<cntaddr>
<addrtype>mailing</addrtype>
<address>PO Box 4982</address>
<city>Boulder</city>
<state>CO</state>
<postal>80306</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303.444.1670</cntvoice>
<cntfax>303.443.4856</cntfax>
<cntemail>ctm@ctmap.com</cntemail>
</cntinfo>
</distrib>
<resdesc>Alpine Loop Spatial Analysis and Mapping Project</resdesc>
<distliab>
Computer Terrain Mapping, Inc. (CTM) provides this data set as is.  CTM makes
no guarantee or warranty concerning the accuracy of information contained
in the data.  CTM further makes no warranties, either expressed or implied
as to any other matter whatsoever, including, without limitation, the
condition of the product, or its fitness for any particular purpose. The
burden for determining fitness for use lies entirely with the user.
Although this data has been processed successfully on computers at CTM, no
warranty, expressed or implied, is made by the CTM regarding the use of
this  data on any other system, nor does the fact of distribution
constitute or imply any such warranty.
</distliab>
<custom>Contact distributor to receive additional copies.</custom>
</distinfo>
<metainfo>
<metd>200504</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Computer Terrain Mapping, Inc.</cntorg>
<cntper>Ed Russell</cntper>
</cntorgp>
<cntpos>President</cntpos>
<cntaddr>
<addrtype>mailing</addrtype>
<address>PO Box 4982</address>
<city>Boulder</city>
<state>CO</state>
<postal>80306</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303.444.1670</cntvoice>
<cntfax>303.443.4856</cntfax>
<cntemail>ctm@ctmap.com</cntemail>
<hours>8:00-5:00 MT</hours>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
</metainfo>
</metadata>

