{
 "currentVersion": 10.61,
 "serviceDescription": "Abstract: \n        The Colorado Natural Heritage Program (CNHP) collects data on rare\n        and imperiled species, subspecies and natural communities \n        (collectively known as Element Occurrences or EOs) in Colorado. \n        Potential Conservation Areas (PCAs) are derived from these data. A \n        PCA represents CNHP's best estimate of the primary area supporting \n        the long-term survival of targeted species, subspecies and natural \n        communities. \n          \n      Purpose: \n        CNHP provides information on the distribution of potential conservation \n        areas in Colorado to public and private agencies and individuals for \n        environmental review, proprietary land management, resource planning, \n        biological and ecological research and general scientific reference.\n  \n      Supplemental_Information:\n        Potential Conservation Areas are typically drawn on-screen (\"heads \n        up\" digitizing) using DOQs or 7.5 minute USGS topographical maps (DRGs) \n        as a reference. Source information is documented in the attribute table. \n        Data are available in geodatabase format or shapefile format. \n\n        PCAs are land units that have been identified as important to the \n        continued existence of ecological processes that support one or a suite \n        of rare or significant features. Also, a) they are often based on desk-\n        top scientific references and need ground-truthing; b) they are based\n        on biological and physical factors and do not account for land owner-\n        ship and political concerns; c) they are useful for land-use planning \n        and conservation strategies but DO NOT have legal meaning or in any \n        way represent an attempt to regulate or limit the use of private \n        property; and d) they do not automatically exclude any activity what-\n        so-ever. Instead, they constitute a hypothetical area required to ensure\n        the continued existence of the targeted elements of biodiversity.\n\n        The size and configuration of a PCA will be dictated by the conservation\n        targets (i.e. those species, communities or systems we seek to\n        conserve at a given location) and their sustaining ecological\n        processes. PCA refers to the ability of a conservation area to maintain\n        healthy, viable targets over the long term (100+ years), including \n        ability to respond to natural or human-caused environmental change.\n        PCAs do not necessarily preclude human activities, but their ability\n        to function naturally may be greatly influenced by them. PCAs at all\n        scales may require ecological management or restoration to maintain\n        their functionality. \n\n        CNHP manages data using the Biodiversity Tracking and Conservation \n        System (BIOTICS) which integrates spatial data using ArcView 3.3 \n        (ESRI 1992-2002) with narrative and tabular data using Oracle 10x \n        (Oracle Corporation 1998-2004). BIOTICS was designed by NatureServe,\n        CNHP's parent organization. To learn more about the BIOTICS data model, \n        refer to http://www.natureserve.org/prodServices/biotics.jsp",
 "mapName": "Layers",
 "description": "",
 "copyrightText": "Colorado Natural Heritage Program",
 "supportsDynamicLayers": false,
 "layers": [
  {
   "id": 0,
   "name": "CNHP Potential Conservation Areas",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 1.8489297737236E7,
   "maxScale": 9027.977411
  }
 ],
 "tables": [],
 "spatialReference": {
  "wkid": 102100,
  "latestWkid": 3857
 },
 "singleFusedMapCache": false,
 "initialExtent": {
  "xmin": -1.215505266403366E7,
  "ymin": 4633125.496305233,
  "xmax": -1.134983443326634E7,
  "ymax": 4967736.231326403,
  "spatialReference": {
   "wkid": 102100,
   "latestWkid": 3857
  }
 },
 "fullExtent": {
  "xmin": -1.21460611051E7,
  "ymin": 4437108.202600002,
  "xmax": -1.13588259922E7,
  "ymax": 5015037.642800003,
  "spatialReference": {
   "wkid": 102100,
   "latestWkid": 3857
  }
 },
 "minScale": 1.8489297737236E7,
 "maxScale": 9027.977411,
 "units": "esriMeters",
 "supportedImageFormatTypes": "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP",
 "documentInfo": {
  "Title": "",
  "Author": "",
  "Comments": "Abstract: \n        The Colorado Natural Heritage Program (CNHP) collects data on rare\n        and imperiled species, subspecies and natural communities \n        (collectively known as Element Occurrences or EOs) in Colorado. \n        Potential Conservation Areas (PCAs) are derived from these data. A \n        PCA represents CNHP's best estimate of the primary area supporting \n        the long-term survival of targeted species, subspecies and natural \n        communities. \n          \n      Purpose: \n        CNHP provides information on the distribution of potential conservation \n        areas in Colorado to public and private agencies and individuals for \n        environmental review, proprietary land management, resource planning, \n        biological and ecological research and general scientific reference.\n  \n      Supplemental_Information:\n        Potential Conservation Areas are typically drawn on-screen (\"heads \n        up\" digitizing) using DOQs or 7.5 minute USGS topographical maps (DRGs) \n        as a reference. Source information is documented in the attribute table. \n        Data are available in geodatabase format or shapefile format. \n\n        PCAs are land units that have been identified as important to the \n        continued existence of ecological processes that support one or a suite \n        of rare or significant features. Also, a) they are often based on desk-\n        top scientific references and need ground-truthing; b) they are based\n        on biological and physical factors and do not account for land owner-\n        ship and political concerns; c) they are useful for land-use planning \n        and conservation strategies but DO NOT have legal meaning or in any \n        way represent an attempt to regulate or limit the use of private \n        property; and d) they do not automatically exclude any activity what-\n        so-ever. Instead, they constitute a hypothetical area required to ensure\n        the continued existence of the targeted elements of biodiversity.\n\n        The size and configuration of a PCA will be dictated by the conservation\n        targets (i.e. those species, communities or systems we seek to\n        conserve at a given location) and their sustaining ecological\n        processes. PCA refers to the ability of a conservation area to maintain\n        healthy, viable targets over the long term (100+ years), including \n        ability to respond to natural or human-caused environmental change.\n        PCAs do not necessarily preclude human activities, but their ability\n        to function naturally may be greatly influenced by them. PCAs at all\n        scales may require ecological management or restoration to maintain\n        their functionality. \n\n        CNHP manages data using the Biodiversity Tracking and Conservation \n        System (BIOTICS) which integrates spatial data using ArcView 3.3 \n        (ESRI 1992-2002) with narrative and tabular data using Oracle 10x \n        (Oracle Corporation 1998-2004). BIOTICS was designed by NatureServe,\n        CNHP's parent organization. To learn more about the BIOTICS data model, \n        refer to http://www.natureserve.org/prodServices/biotics.jsp",
  "Subject": "Potential Conservation Areas (PCA) - A PCA represents CNHP's best estimate of the primary area supporting the long-term survival of targeted species, subspecies and natural communities.",
  "Category": "",
  "AntialiasingMode": "None",
  "TextAntialiasingMode": "Force",
  "Keywords": "Potential Conservation Area,biodiversity"
 },
 "capabilities": "Map,Query,Data",
 "supportedQueryFormats": "JSON, AMF, geoJSON",
 "exportTilesAllowed": false,
 "supportsDatumTransformation": true,
 "maxRecordCount": 1000,
 "maxImageHeight": 4096,
 "maxImageWidth": 4096,
 "supportedExtensions": "KmlServer"
}