{
 "currentVersion": 10.61,
 "serviceDescription": "Abstract: \n        The Colorado Natural Heritage Program (CNHP) collects data on rare and \n        imperiled species, subspecies and unique natural communities in \n        Colorado. An element occurrence (EO) represents a location in which a \n        species, subspecies or natural community is, or was, present. An EO has \n        potential continued (or historic) presence and/or regular recurrence at \n        a given location and has practical conservation value. Due to the \n        sensitive nature of these data, EOs were used to generate a list of \n        elements by 7.5 minute USGS quadrangles. This file represents all tracked\n        species, subspecies and natural communities currently located on a \n        particular 7.5 minute USGS quadrangle, historically located on a \n        particular 7.5 minute USGS quadrangle and potentially located on a \n        particular 7.5 minute USGS quadrangle. Data are for non-commercial use\n        only.\n\n      Purpose: \n        CNHP provides information on the distribution of Colorado's rare and \n        imperiled species, subspecies and unique natural communities to public \n        and private agencies and individuals for environmental review, \n        proprietary land management, resource planning, biological and \n        ecological research and general scientific reference. \n\n      Supplemental_Information:\n        Data were derived from field surveys performed by CNHP and other \n        credible sources such as Forest Service personnel, Bureau of Land \n        Management staff, etc. Data are available in geodatabase format \n        or shapefile format; feature type is regions or multi-part shapes. \n\n        Lists of elements by quadrangle were generated by intersecting EO\n        data with a quadrangle coverage to generate a list of elements\n        per quad. Records with general mapping precision (imprecise locational\n        data) were converted to centroids prior to the intersection to avoid \n        grossly inflating the number of elements potentially located on a quad. \n        Polygon data were used during the intersection for all other records.  \n        \n        Mapping methodology for EOs used to generate the list of elements in this\n        file:\n\n        Old Method:\n        Data were compiled onto 7.5 minute U.S.G.S. topographic maps. Point \n        coordinates, representing the centrum of the occurrence, were measured \n        manually in degrees, minutes, and seconds of longitude and latitude. \n        Coordinates were converted to decimal degrees and used to generate a \n        GIS point coverage with single precision. \n\n        During the data conversion process, all point data had to be converted \n        to polygons. Points were buffered by mapping precision, the spatial \n        uncertainty of the element occurrence, in order to capture the maximum \n        extent of the occurrence (ex. EO with seconds mapping precision) OR to \n        represent the entire area in which an EO could fall (ex. EOs with minutes \n        or general mapping precision). Natural community polygons were created \n        differently. Least rectangles, the bounding box of an occurrence, were \n        generated using the northernmost, southernmost, westernmost and \n        easternmost coordinates of the community. Any natural community \n        without least rectangle coordinates was entered into the system as a \n        point and buffered by mapping precision.\n\n        The old method did not adequately represent the locations of large EOs\n        or EOs with high spatial uncertainty. In response to these concerns,\n        NatureServe, CNHP's parent organization, designed the Biodiversity \n        Tracking and Conservation System (BIOTICS) which integrates spatial\n        data using ArcView 3.3 (ESRI 1992-2002) with narrative and tabular\n        data using Oracle 10x (Oracle Corporation 1998-2004). To learn more\n        about the BIOTICS data model, refer to \n        http://www.natureserve.org/prodServices/biotics.jsp\n\n        New Method:\n        For EOs with seconds mapping precision: \n        1) any EO larger than 12.5 meters (CNHP's minimum mapping \n        unit) in length and width is digitized as a polygon, \n        2) any EO greater than 12.5 meters in length but less than 12.5 meters \n        in width is digitized as a line and buffered 6.25 meters for a total \n        width of 12.5 meters, and \n        3) any EO less than 12.5 meters in length and width is entered as a \n        point and buffered by 6.25 meters (for a diameter of 12.5 meters) if \n        the coordinates were captured via GPS and differentially corrected.\n        Points not captured via GPS are given larger buffer distances. These\n        distances are based on the information provided by the data source or \n        the best estimate of CNHP's information managers. \n        \n        EOs with minutes or general mapping precision cannot be accurately \n        mapped since the data source did not provide specific directions. CNHP \n        might know an EO is within a county, PLSS Township or a State Wildlife \n        Area. In these examples, CNHP would use GIS layers of counties, \n        Townships and managed areas to represent the possible location of the \n        occurrence. Hence, polygons of minutes and general EOs represent the \n        area in which the EO could occur.\n\n        CNHP is reviewing EO polygons as time and funding allows. Eventually,\n        all EOs will meet new methodology standards. Currently, 54% of \n        occurrences meet new methodology standards.",
 "mapName": "Layers",
 "description": "",
 "copyrightText": "Colorado Natural Heritage Program",
 "supportsDynamicLayers": false,
 "layers": [
  {
   "id": 0,
   "name": "Statewide Elements by Quad",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 1.8489297737236E7,
   "maxScale": 9027.977411
  }
 ],
 "tables": [],
 "spatialReference": {
  "wkid": 102100,
  "latestWkid": 3857
 },
 "singleFusedMapCache": false,
 "initialExtent": {
  "xmin": -1.2057967686142672E7,
  "ymin": 4670019.249827929,
  "xmax": -1.1446960656842317E7,
  "ymax": 4931250.437695334,
  "spatialReference": {
   "wkid": 102100,
   "latestWkid": 3857
  }
 },
 "fullExtent": {
  "xmin": -1.21478164779E7,
  "ymin": 4421697.9804000035,
  "xmax": -1.1354638944E7,
  "ymax": 5030795.9179000035,
  "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": "",
  "Subject": "",
  "Category": "",
  "AntialiasingMode": "None",
  "TextAntialiasingMode": "Force",
  "Keywords": "biodiversity"
 },
 "capabilities": "Map,Query,Data",
 "supportedQueryFormats": "JSON, AMF, geoJSON",
 "exportTilesAllowed": false,
 "supportsDatumTransformation": true,
 "maxRecordCount": 1000,
 "maxImageHeight": 4096,
 "maxImageWidth": 4096,
 "supportedExtensions": "KmlServer"
}