1. Parks and Open Space
Sensitive GIS Data Policy
March 26, 2015
{FILE} Pg. 1 of 1 2012/05
Summary
This policy defines sensitive GIS data and describes the appropriate and legal use of such information.
The categories of sensitive data are described and the reasons for their designation as sensitive are
explained. In appropriate situations sensitive data can be conditionally released to certain groups of the
public with permission from the custodians of that particular data. The terms of these releases and the
processes for doing so are also contained in this policy. Finally, this policy also establishes the methods
for amending the policy and adding or changing sensitive data sets and designations.
Purpose of the Sensitive GIS Data Policy
Boulder County Parks and Open Space (“POS”) is the steward of public land and its associated natural
and cultural resources. As the custodian of these resources, POS has the responsibility to balance the
protection of these resources with the desire of the community to utilize and appreciate these resources.
This stewardship extends to both digital and hard‐copy information and records that represents those
resources. This policy is designed to provide POS staff and the public with an understanding of what
Boulder County’s legal rights and responsibilities are in terms of sensitive GIS data, how to define
sensitive GIS data, and when and how to release these data. It is important to note that although the
amount of sensitive data that BCPOS stewards is small, less than 5% of all of the BCPOS GIS data, the
proper use and management of these data is critical.
Sensitive GIS Data Policy Process
The sensitive GIS data policy process was initiated in September of 2011, with representatives from the
POS divisions of Resource Management, Administration, Recreation and Facilities, and Resource
Planning participating in the process. The Real Estate and Agricultural Resources Divisions participated
in an advisory capacity. In the initial memorandum to BCPOS Management Staff the goals of the policy
were to define what sensitive GIS data are, clarify how those data are managed, determine who we
release those data to and in what format that data is released, and create a strategy for educating POS
staff and the public on proper usage of sensitive data.
The initial target completion date was April 2012. This goal was not achieved due to two major events.
First, an update to the Environmental Resources Element of the Boulder County Comprehensive Plan
began in 2012. Part of this update process included identifying species and communities of special
concern in Boulder County. The sensitive GIS data policy group decided to use this list, in part, to
identify which data sets and records would be considered sensitive. Therefore, the sensitive GIS data
policy project was put on hold until the ERE update was completed. The final draft of the ERE update
was completed in September 2013, which then enabled the Sensitive Data Policy group to move forward
with the development of the Sensitive Data Policy. The second event to occur was the September 2013
flood event. For more than six months flood response and recovery became the primary focus for all of
the group members, so it was not until late spring 2014 that work resumed on the sensitive GIS data
policy.

2. Page | 2
The committee first met with the County Attorney’s Office to understand what the County’s legal rights and
responsibilities are concerning sensitive data management. We also discussed logistical items, such as how a
request should be received, how it should be handled, and at what point during the process it should be elevated to
the County Attorney’s Office for further legal assistance.
The next phase was to review sensitive data policies from other public agencies at the local, state and federal
levels. The group reviewed best practices in sensitive data management and examined the variety of frameworks
that agencies used to define sensitive data and to determine the format of data release.
Next, the group determined which sets of data POS staff stewards should be considered to be sensitive. Providing a
sound, scientifically based rationale for protecting sensitive data was a time consuming process and was by far the
most time intensive portion of the process. After the ERE process was completed, the publically adopted list of
species and habitat of special concern were used to determine what should be included on the sensitive data list.
There were some minor modifications made to the list, based on staff experience and expertise.
While determining which data sets should be considered sensitive, the group decided that data should be released
in different formats depending on the nature of the data request. A request from a member of the public should
not be treated the same as a request from another public agency with a mission similar to BCPOS. In one situation
releasing exact locations could be detrimental to the resource, while releasing exact locations in the other situation
may benefit the health and protection of the resource.
Finally the group addressed the logistics of creating policy update and data request processes.
County Sensitive Data Policies
The County has several existing policies that apply to the use, access, and release of data. Section I.10 in the
Boulder County Personnel and Policy Manual refers to the Colorado Open Records Act (CORA), CRS §§ 24‐72‐204
et seq., which generally states that the public has a right to access the public records of a governmental entity.
However, under CORA “procedures for such disclosure can be subject to rules and regulations made by the official
custodian or the custodian. C.R.S. § 24‐72‐203(1)(a). These rules and regulations are authorized, if they are
reasonably necessary for the protection of such records and for the prevention of unnecessary interference with
the regular discharge of the duties of the custodian or his/her office/department.”
In Policy Manual Section I.24.H, Computing Security, sensitive data is defined more broadly and instructs personnel
to use departmental procedures or contact the County Attorney’s office to determine what constitutes sensitive
data.
The Boulder County GIS Data Sharing and Purchasing Policy contains general guidelines but it does not include a
comprehensive list of sensitive data within the county. Some data sets are specifically mentioned, such as parcel
lines, but it specifies that the distribution of GIS data requires the permission of the Department or Office from
which the data originated.
(http://collaboration/sites/gisproject/Data%20Sharing%20and%20Public%20Requests/Forms/AllItems.aspx)
This POS policy, having been developed and approved by POS staff and reviewed by the County Attorney, defines
sensitive data for POS and describes management and use of sensitive data in a manner that meets not only legal
standards but also POS concerns for its appropriate use.
Note: Freedom of Information Act
The Freedom of Information Act (FOIA) is a federal law that provides the public access to federal government
information and documents. FOIA applies only to federal agencies; therefore Boulder County is not subject to
FOIA.
What is Sensitive Spatial Data?

3. Page | 3
An interdisciplinary team of POS staff was convened to create the policy as well as define which GIS data would be
considered sensitive. The group identified several categories of data that could include sensitive information.
From these types of GIS data the group selected discrete coverages and databases to designate as sensitive.
Boulder County Parks and Open Space defines sensitive data as any information that when released could result in
an adverse effect on a human, cultural, or natural resource. Sensitive cultural or natural resources are features,
species, habitats, geological formations, and all archaeological sites, features or isolated finds that are especially
vulnerable to damage by human disturbance, collection, or destruction. Other types of sensitive data include the
locations of expensive monitoring equipment such as trail counters and weather stations that could be put at risk
with the public knowledge of their whereabouts.
Categories of Sensitive Spatial Data
POS creates, maintains, and manages a variety of spatial data. Only a small amount of it is designated as sensitive.
Data sensitivity is governed by a number of factors and, in some cases, is determined by an internal,
interdepartmental staff team. The POS Director and Management Team ultimately approve the designation of
specific sensitive data sets.
1. Data Protected By Legislation
The only data that falls in the category of data protected by legislation is POS’s cultural resource data.
Providing exact locations of cultural resource information is exempted from CORA open records
request by CRS 24‐72203 (1), CRS 24‐80‐405(2), and the Archaeological Resource Protection Act
(ARPA) of 1979 16 U.S.C. §§ 470aa et seq.
2. Deliberative Process
Information collected, created, and prepared for internal POS work processes is not subject to
mandatory disclosure under CORA. An example could be conceptual trail alignments created as part of
the internal management planning process for a property. Some of these trail alignments would be
intended only for staff review and consideration and would not become official trail alignment
alternatives presented to the public. Their release to the public could lead to resource damage, off trail‐
use, and potential risk to public safety. Real estate negotiations and property acquisitions are also
exempt until the transaction is complete.
3. Information Injurious to the Public Good
Information considered by the custodian of the data to be injurious to the public good is not
automatically exempted from an open records request. CORA states:
“If, in the opinion of the official custodian of any public record, disclosure of the contents of said record
would do substantial injury to the public interest, notwithstanding the fact that said record might
otherwise be available to public” (CRS § 24‐72‐204(6)(a)) the public entity that holds the information is
not required to disclose it.
For example, the location of social trails is considered sensitive due to the environmental degradation
which can result from potential increased use if the mapped locations of social trails are released.
Social trails are generally located in areas that are unsustainable, which with increased use, can cause
soil erosion, loss of vegetation, and an increase of invasive species. Increased use of social trails may
also directly impact wildlife, causing displacement.
The Sensitive Data Team spent a considerable amount of time determining which plant and wildlife
species and communities would fall under this category. In order to be listed under this category a
species or community had to be listed on a state or federal protection list, such as the federal
Endangered Species Act, or there had to be compelling evidence that releasing the data could cause
harm to that resource. An example is that by releasing the exact location of a Northern Goshawk nest it

4. Page | 4
would expose the eggs and young to the risk of being taken by falconers. A more complete rationale for
not disclosing sensitive data about the location of wildlife and plant species, as well as plant
communities can be found in Appendix 1: Designating Wildlife Species of Special Concern and Appendix
2: Designating Plant Species of Special Concern and Significant Natural Communities.
See also Appendix 3 for a full listing of the current BCPOS Sensitive GIS Data.
Data Not Considered Sensitive
Some data that does not fall under the definition of sensitive data, but will still never be released by Boulder
County Parks and Open Space. There are two instances that fit within this category:
1. Third Party Data
This is data that is created and maintained by another entity and has been released to Boulder County
for county use. This data may not necessarily be sensitive and in some instances may be allowed to be
displayed on public maps by Boulder County. If the county receives a request to provide this data, the
requestor will be redirected to the originating agency.
2. Contractual Obligations
This is data that POS acquired subject to use and dissemination restrictions. This applies to data that
POS may have purchased with restrictions, as well as data that was shared free of charge with the
county under a data sharing agreement.
Staff Use of Sensitive Data
In order for POS staff to effectively accomplish their jobs, staff will not be restricted from accessing and utilizing
sensitive data in any way. To avoid unintended inappropriate data release, BCPOS staff will be thoroughly
educated as to the proper use of BCPOS sensitive data. Currently, two appropriate methods of sensitive data
education have been identified:
1. BCPOS Staff GIS Orientation
Every staff member using GIS is required to go through the POS Staff GIS Orientation process with one
of the GIS staff members. This process educates users on department GIS standards, best practices, and
requirements. During this process sensitive data location, use and limitations will be covered.
2. Creation of Sensitive Data Layer Files
A Sensitive Data directory will be created in v:gispaGIS_Layers to house layer files for all sensitive
data. This directory and the name of the layer files will very clearly indicate that these are sensitive
data layers and are not for use outside of BCPOS staff.
This process of educating staff about sensitive data usage will be ongoing and further opportunities for staff
education will be identified as appropriate.
Classification of Data Requestors
POS recognizes the need to protect significant resources and that doing so may require restricting access to
some types of information. While designating specific data as sensitive allows POS to prevent its release in
some circumstances, POS also understands that access to that information may be useful or necessary for some
professionals, researchers, or other entities to successfully protect those resources. An example would be
sharing the location of rare plant sites or raptor nest locations to a utility company so that these resources can
be avoided by a proposed pipeline or other development. In other cases, researchers on POS properties would

5. Page | 5
benefit from knowing the specific location of resources so that in the performance of their work they do not
disturb such resources or because their work can be improved by knowing the location of those resources.
To efficiently respond to data requests, POS recognizes four categories of data requestors. The classification of
these different individuals and organizations into similar groups allows POS to standardize its responses to
sensitive data requests. The Sensitive Data Team created these categories and has considered and approved
the release format of sensitive data for the purposes described for each group. The matrix illustrations below
depict which sensitive data formats are allowed for release to which group. In most cases, the release of
sensitive data will be on a case‐by‐case basis after accounting for the expressed need for the data, the details of
its use and management, and the law. In these situations, the custodian of the data’s originating division shall
have the final decision on sensitive data releases.
1. General Public
The general public is any person or group of persons that do not fall under any of the below categories.
An example would include a request for social trail locations by a local biking association.
In most cases, these data will be released denatured to the quarter section due in order to protect the
exact location of the resource. Data denatured in this way will not include specific point, line, or
polygon features but rather just the outline of the quarter square mile (160‐acre block) of the public
land survey system where the resource occurs. Cases in which the data will not be released include
when the data is part of the deliberative process, when the data is protected by other laws or in cases
where releasing the data, even in a denatured format, will not sufficiently protect the resource or public
interest.
2. Educators
This policy considers educators as people or organizations that provide information to others. This
includes teachers, independent educators, and students not associated with a qualified researcher or
professional. Past examples of these types of requests are local community colleges requesting raptor
nest locations to use within a class exercise on site analysis and high school teachers integrating GIS
locations of historic cultural sites into an archaeological curriculum.
In most cases, these data will be released denatured to the quarter section in order to protect the exact
location of the resource. Some data may be released in its original format, upon review and approval of
the data custodian. In cases where the data is released in its original format, a data sharing agreement
will be required to be signed by both the requesting/contracting party and POS. This contract releases
the data to the signing party or person for the specified use only; it prohibits redistribution or
publishing of the raw data in any format.
Cases in which the data will not be released include when the data is part of the deliberative process,
when the data is protected by other legislation or in cases where releasing the data, even in a denatured
format, will not sufficiently protect the resource or public interest.
3. Researchers, Peer Agencies, and Contracting Entities
In this policy, a researcher is defined as a person or organization who is conducting scientific research
permitted by Boulder County that may or may not be affiliated with a research institution. This
includes college, university and other institutional professors and their graduate students. Peer
agencies are defined as governmental or non‐governmental entities that perform similar services and
share the mission and values of POS. A contractor is a person or organization that is not an employee of
Boulder County, but has been hired to perform a specific service in a specific time frame.
In most cases, the data will be released in its original format, pending review and approval of the data
custodian. A data sharing agreement will be required to be signed by both the requesting/contracting
party and BCPOS. This contract releases the data to the signing party or person for the specified use

6. Page | 6
only; it prohibits redistribution or publishing of the raw data in any format. It is necessary to allow
these parties full access to the data to promote public research, provide contractors all information
necessary to fulfill their contractual obligations to POS, and to protect the resource from harmful
activities, such as infrastructure development.
Cases in which the data will not be released to this type of requestor include when the data is part of
the deliberative process, when the data is protected by other legislation or in cases where releasing the
data, even in a denatured format, will not protect the resource or public interest.
4. Emergency Services
An emergency service provider is an organization or agency that responds to public health and safety in
emergency situations.
In most cases, the data will be released in its original format, pending review and approval of the data
custodian. A data sharing agreement will be required to be signed by both the requesting/contracting
party and POS. This contract releases the data to the signing party or person for the specified use only;
it prohibits redistribution or publishing of the raw data in any format. Data will be released to
emergency services to assist in protecting resources on POS property in the event of an incident.
Cases in which the data will not be released include when the data is not crucial to protecting public
health and safety, and that data is either part of the deliberative process, protected by other laws or in
cases where releasing the data, even in a denatured format will not protect the resource or public
interest.

7. Page | 7

8. Page | 8
Process for Handling GIS Data Requests
POS is the steward of a large amount of data, and many of these datasets have use and release restrictions that may
be imposed from internal policy or from the entities from which we obtained the data, by data sharing agreement
or by contractual obligation. Any GIS data that is being requested from outside of POS, both for sensitive data and
for non‐sensitive data, will be released by the GIS staff only. The intent is to ensure that we abide by any and all
policy restrictions and legal obligations concerning the GIS data and the GIS staff is knowledgeable in each datasets
use and dissemination limitations and allowances.
This is to be submitted on behalf of a requestor by a POS staff member. All GIS data requests will be submitted via
the InsideBC GIS page Data Request form.
1. An email will be sent to the data custodian indicating that a data request was made and review and approve
or deny the data request.
2. If approved, a data sharing agreement or contract specifying data use limitation must be signed by the
requestor and a POS staff (generally a GIS staff member) prior to the release of the data.
a. For all data requestors which fall under Class 2 Educators, use this form: V:gisBASICData
AgreementsCounty Data Sharing Agreement STUDENT EDUC 2010.doc
b. For Class 3 Researchers and Peer Agencies, use this form: V:gisBASICData AgreementsCounty
Data Sharing Agreement STUDENT EDUC 2010.doc
c. For Class 3 Contractors, use this form: V:gisBASICData AgreementsCounty Data Sharing
Agreement CONTRACTOR 2010.doc
d. For all data requestors which fall under Class 4, outside of emergency incidents, use this form:
V:gisBASICData AgreementsCounty Data Sharing Agreement CONTRACTOR 2010.doc
3. The GIS staff will then package the data and make it available to the requestor in an appropriate manner,
including email, hard copies, the county ftp site, or some other manner. See Appendix 3 for data storage
locations.
4. In a case where a data requestor is unsatisfied with the data release policy as laid out above, the data
request will be referred to the work group Division Manager, the Resource Planning Manager, the
Department Director, and the County Attorney’s office before any further data is released.
Process for Updating Sensitive GIS Data Policy
Any changes to the Sensitive GIS Data Policy need to be presented to the Sensitive GIS Data Policy Team for
approval by the work group supervisor. This includes, but is not limited to, any changes to the list of sensitive data
sets, the format in which data is delivered, or the method by which requests are filled. The request for policy
updates will be reviewed by the committee. If the request is approved by the committee it will be submitted to
POS Management Staff for final approval.

9. Appendix 1: Criteria for Designating Wildlife Species of Special Concern
Criteria #1. Authoritative Listing
This criterion lists those species based on the Boulder County Comprehensive Plan, Environmental Resource
Element, Species of Special Concern, listing Criteria 1 & 2. These criteria list those species on Federal, State or
Recognized Authority status lists in the following categories:
1. Species with Federal status (listed or proposed threatened or endangered, candidates for listing, or under
review for listing) or State status (threatened, endangered or State concern).
2. Species considered to be sensitive that appear on the following lists: Colorado Parks & Wildlife − Species of
State Special Concern, U.S. Forest Service Region 2 − Sensitive Species, U.S. Bureau of Land Management −
Sensitive Species, U.S Fish & Wildlife Service − Birds of Conservation Concern.
Criteria #2. Rare and Declining
This criterion lists those species based on the Boulder County Comprehensive Plan, Environmental Resource
Element, Species of Special Concern, listing Criteria 3. This criterion lists those species that have undergone a
documented long‐term noncyclical population decline, or whose abundance is critically low relative to their
expected abundance in a given habitat type or quality. These species are identified in the BCCP ERE SSC List.
Criteria #3. Collection
This criterion lists those species whose population is at risk due to Collection for recreation, pet collection or other
intent. Many animals and plants, such as lizards and snakes, have been collected from the wild beyond sustainable
levels to be sold through the pet trade or be kept in private collections. Species which have an existing population
threat are in greater danger of extirpation when subjected to even low level of collection pressure.
Criteria #4. Persecuted
This criterion lists those beneficial species whose population is at risk due to active control or elimination. The
persecution of wildlife may be deliberate, reckless, due to the lack of awareness of a species presence (ignorance),
or due to a cultural/personal intolerance resulting from beliefs, traditions or practices. Persecutions are
considered actions which lead to the direct or indirect injury or death of individuals of a species type, the
destruction of breeding or other habitat based on the persecution, and harassment or manmade disturbance which
leads to habitat abandonment. Generally, the most harmful form of persecution is the targeted elimination of a
species which perform essential roles in local ecosystem health but are considered a pest.
Criteria #5. BCPOS Selected Species
This criterion lists those species which are not identified by the above criteria, but warrant data protection due to
expert knowledge of local species status. These species are selected based on such factors as local knowledge of
animal behavior or sensitivity to disturbance, or regional or national trends in a species population decline due to
i.e. diseases. Other factors, as determined by BCPOS staff biologists, may also contribute to the selection of a
species as sensitive to data sharing.

10. Data Sensitive Wildlife Species
Count Common Name Class
SSC Criteria
(1/2)
Rare &
Declining Collectable Persecuted
1 Frog, Northern Leopard Amphibian 2 *
2 Toad, Boreal Amphibian 1,2 *
3 Bittern, American Bird 2,5
4 Bunting, Lark Bird 2,3
5 Eagle, Bald Bird 1,2,5
6 Eagle, Golden Bird 2,5
7 Falcon, Peregrine Bird 2,4,5
8 Falcon, Prairie Bird 2,5
9 Flycatcher, Olive‐sided Bird 2,5
10 Flycatcher, Willow Bird 1,2,3,5 *
11 Goshawk, Northern Bird 2,5
12 Harrier, Northern Bird 2,3,4,5 *
13 Hawk, Ferruginous Bird 2,3,5
14 Kingfisher, Belted Bird 3
15 Ovenbird Bird 4
16 Owl, Boreal Bird 2,5,10
17 Owl, Burrowing Bird 1,2,3,5 *
18 Owl, Flammulated Bird 2,5
19 Owl, Long‐eared Bird 3
20 Owl, Short‐eared Bird 2,4,5
21 Ptarmigan, White‐tailed Bird 2,5,9
22 Rosy‐Finch, Brown‐capped Bird 2,5
23 Shrike, Loggerhead Bird 2,3,5 *
24 Sparrow, Brewer's Bird 2,3,5
25 Sparrow, Cassin's Bird 2,3
26 Sparrow, Grasshopper Bird 2,3,5
27 Swift, Black Bird 2,4,5
28 Veery Bird 2,4,5
29 Woodpecker, American Three‐toed Bird 2,5
30 Woodpecker, Lewis's Bird 2,3,5
31 Woodpecker, Red‐headed Bird 3,5,10
32 Chub, Lake Fish 1,5 *
33 Darter, Iowa Fish 2,4,5
34 Minnow, Brassy Fish 1,5 *
35 Shiner, Common Fish 1,5 *
36 Stonecat Fish 2,4,5 *
37 Topminnow, Plains Fish 3 *
38 Trout, Greenback Cutthroat Fish 1,3,9 *
39 Capshell, Rocky Mountain Gastropod 2,3 *
40 Floater, Giant Gastropod 3 *
41 Papershell, Cylindrical Gastropod 2,3 *
42 Physa, Banded Gastropod 3 *
43 Sprite, Umbilicate Gastropod 3 *
44 Bee, Western Bumble Insect 3,6 *
45 Darner, Lake Insect 5,10 *
46 Dragonfly, Hudsonian Emerald Insect 2,5,10
47 Elfin, Moss's Insect 4,5
48 Fritillary, Regal Insect 2,3,5 *
49 Skipper, Ottoe Insect 2,4,5
50 Bat, Big Brown Mammal 9
51 Bat, Brazilian Free‐tailed Mammal 4,8,9

11. 52 Bat, Eastern Red Mammal 4,8
53 Bat, Hoary Mammal 4,8
54 Bat, Silver‐haired Mammal 5
55 Bat, Townsend's Big‐eared Mammal 2,3,4,9
56 Bat, Tricolored Mammal 9
57 Beaver, North American Mammal 5,6 *
58 Jackrabbit, White‐tailed Mammal 3,10 *
59 Lynx, Canada Mammal 1,2,3
60 Marten, American Mammal 2,5
61 Mouse, Prebles Meadow Jumping Mammal 1,2,5
62 Myotis, Fringed Mammal 2,4,5,8,9
63 Otter, River Mammal 1,2,4
64 Sheep, Rocky Mountain Bighorn Mammal 2,9
65 Lizard, Short‐Horned Reptile 4,5,10 *
66 Snake, Common Garter Reptile 2,3
67 Snake, Milk Reptile 4,9 *
68 Turtle, Spiny Softshell Reptile 4,10 *
Extirpated Species
Species Name Class
SSC Criteria
(1/2)
Rare &
Declining Collectable Persecuted
69 Toad, Great Plains Amphibian 7
70 Curlew, Long‐billed Bird 2,7
71 Goldeneye, Barrow's Bird 7
72 Grouse, Plains Sharp‐tailed Bird 7
73 Plover, Mountain Bird 2,7
74 Chub, Hornyhead Fish 1,7
75 Dace, Northern Redbelly Fish 1
76 Shiner, Blacknose Fish 7
77 Jewelwing, River Insect 3
78 Moth, Lost Ethmiid Insect 7,10
79 Bear, Grizzly Mammal 1,2,7
80 Bison Mammal 7
81 Ferret, Black‐footed Mammal 7
82 Fox, Swift Mammal 7
83 Pronghorn Mammal 7
84 Wolf, Gray Mammal 1,7
85 Wolverine Mammal 1,2,7
Species of Undetermined Status
Species Name
Class
SSC Criteria
(1/2)
Rare &
Declining Collectable Persecuted
86 Owl, Mexican Spotted Bird 1,10
87 Owl, Northern Pygmy Bird 10
88 Sprite, Sharp Gastropod 2,3,10 *
89 (an Ant) Insect 10 *
90 Snake, Lined Reptile 9,10 *

12.
Appendix 2: Criteria for Designating Plant Species of Special Concern and Significant Natural Communities
Species of Special Concern include the flora and fauna in the county whose populations may be threatened or
endangered, locally rare, experiencing long‐term non‐cyclical population declines, isolated or restricted to distinct
local habitat types, or native species which have ceased to exist within Boulder County (ERE Goals and Policies 2013,
Overview).
The Boulder County Species of Special Concern List (SSC List) is a compilation of rare plants and significant natural
communities of special status that warrant protection in order to prevent population or habitat loss. The list was
developed through consultation with botany and plant ecology professionals in federal, state, and local
governmental agencies, non‐governmental conservation organizations, local universities, and private consultants,
as well as Boulder County conservation experts. The majority of species and communities appearing on the SSC list
are recognized as imperiled or critically imperiled by the Colorado Natural Heritage Program (CNHP). CNHP is a
nonprofit organization sponsored by Colorado State University that tracks and ranks Colorado’s rare and imperiled
species and habitats. The list comprises species CNHP ranks as critically imperiled, imperiled, or vulnerable to
extirpation globally (G1‐G3) or statewide (S1‐S3). Species ranked as more secure or secure (G4‐G5, S4‐S5) are
excluded from the list.
The SSC List is intended to comprehensively document Boulder County species and communities as they exist
today. To be listed on the SSC List, a species/community must meet at least one of the required, or two or more of
the conditional, criteria listed below. In some instances, a species has been included on the SSC List even though it
does not meet the SSC List criteria. This is based on professional judgment and only occurs with species for which
there is presently incomplete or uncertain information available. The SSC List will be updated as more information
is learned about individual species or communities, including changes to their status.
Required
1. Species/Communities with Federal Status (listed or proposed threatened or endangered ‐‐ LT, LE, PT),
candidates for listing ‐‐ C or under review for listing), e.g, Colorado butterfly plant (Gaura neomexicana ssp.
coloradensis) – LT, G3T2/S1 (U.S. Fish and Wildlife Service 2013, CNHP 2013);
2. All G1‐G2 and S1‐S2 species that are not also federally listed;
3. Collectable/Harvestable: Species threatened by collection or harvest including showy varieties of orchids,
lilies, penstemon, and cacti.
Conditional
4. Species/communities with U.S. Forest Service Region 2 (USFS R2) sensitive species1, National Park Service
(NPS) sensitive species within Rocky Mountain National Park (RMNP)2, or City of Boulder Open Space and
Mountain Parks sensitive status;
1
This criterion acknowledges that USFS R2 boundaries extend beyond Boulder County and encompass habitats that do not occur
within the county, thus not all USFS R2 sensitive species appear on the SSC List.
2
This criterion acknowledges that that NPS RMNP boundaries extend beyond Boulder County and encompass habitats that do not
occur within the county, thus not all NPS RMNP sensitive species appear on the SSC List.

13.
5. Species/communities that could occur within Boulder County and that CNHP ranks as critically imperiled,
imperiled, or vulnerable to extirpation either globally (G1 – G3) or statewide (S1 – S3), e.g., autumn willow
(Salix serissima) – G4/S1 and narrowleaf grapefern (Botrychium neolunaria) – G5/S3;
6. Relictual species/communities having undergone a documented long‐term decline or having a critically
low population size relative to their historic presence and/or relative abundance in a given ecosystem, e.g.,
American groundnut (Apios americana) – G5/S1 and big bluestem – prairie dropseed (Andropogon gerardii
– Sporobolus heterolepis) – G2/S1S2;
7. Species/communities endemic to Boulder County or region3, e.g., Colorado aletes (Aletes humilis) –
G2G3/S2S3;
8. Species/communities known or thought to be extinct or extirpated in Boulder County, i.e., species that
historically occupied and are native to Boulder County, that may exist in surrounding regions, and that may
be able to repopulate Boulder County, e.g., pale moonwort (Botrychium pallidum).
9. Species/communities whose populations in the County that are vulnerable to threats4 affecting their
populations either directly or indirectly, e.g. limber pine (Pinus flexilis);
10. Species/communities that have a disproportionately large effect on the diversity within the ecosystem(s)
they inhabit e.g., montane riparian forests such as quaking aspen/thinleaf alder (Populus tremuloides /
Alnus incana) forest – G3/S3;
11. Species/communities that are either naturally rare5, at the edge of their range in Boulder County, or are
isolated or imperiled, e.g., black spleenwort (Asplenium adiantum‐nigrum) – G5/S1, montane willow carrs
such as Salix bebbiana shrubland – G3?/S2, and alkali wetlands such as Suaeda calceoliformis herbaceous
vegetation – GU/S2;
12. Species/communities that support sensitive wildlife, e.g., Western Great Plains herbaceous vegetation
(Andropogon gerardii – Schizachyrium scoparium) dominated by big and little bluestem, two native host
plants for Arogos skipper (Atrytone arogos) – G3G4/S2.
3
Species/communities endemic to Boulder County region indicates a species occurring only in Boulder County and in an adjacent
county or counties.
4
Direct or indirect threats to the stability of species populations or communities include disturbances such as climate change, disease,
residential or commercial development, fire suppression, mechanical forest thinning, prescribed fire, etc.
5
Species or communities that are “naturally rare” normally occur in low abundance throughout their range. While their populations
may be stable, species that are rare on the landscape are more vulnerable to extirpation compared to species with large populations.

14. #
State Scientific
Name
State
Common
Name
CNHP
Global
Rank
CNHP State
Rank
Federal
Status
(ESA)
Family
USFS
Sensitive
Status
NPS
(RMNP)
Sensitive
Status
BCCP
Sensitive
Status
City of
Boulder
OSMP
Sensitive
Status
Criteria (#)
PJ = Prof.
judgement
2
Asplenium adiantum‐
nigrum (A.
andrewsii )
black
spleenwort
G5 S1 Aspleniaceae
Sensitive,
Map #4
(30) (BCCP
1986)
Map #6
(BCCP 1995,
1999)
5, 11, PJ
3
Botrychium
campestre
prairie
moonwort
G3G4 S1 Ophioglossaceae Sensitive 4, 5
4 Botrychium echo
reflected
moonwort
G3 S3 Ophioglossaceae Sensitive
Sensitive,
Map #19
(BCCP 1995,
1999)
3, 4
5
Botrychium
furcatum
forkleaved
moonwort
G1G2 S1S2 Ophioglossaceae Sensitive Sensitive 2, 3, 4, 7
6
Botrychium
furculatum
redbank
moonwort
G2G3 S3 Ophioglossaceae Sensitive 4, 5
7
Botrychium
hesperium
western
moonwort
G4 S2 Ophioglossaceae Sensitive
Sensitive,
Map #19
(BCCP 1995,
1999)
4, 5
8
Botrychium
lanceolatum var.
lanceolatum
lanceleaf
moonwort
G5T4 S3 Ophioglossaceae Sensitive
Sensitive,
Map #19
(BCCP 1995,
1999)
4, 5
9 Botrychium lineare
narrowleaf
moonwort
G2? S1 Ophioglossaceae Sensitive 2, 3, 7
10
Botrychium
neolunaria
common
moonwort
G5 S3 Ophioglossaceae Sensitive 4, 5
FERNS & FERN ALLIES

15. 11
Botrychium
minganense
Mingan
moonwort
G4 S2 Ophioglossaceae Sensitive
Sensitive,
Map #19
(BCCP 1995,
1999)
4, 5
12
Botrychium
pallidum
pale
moonwort
G3 S2 Ophioglossaceae
Sensitive,
Map #19
(BCCP 1995,
1999)
5, 8
13
Botrychium
pinnatum
northern
moonwort
G4? S1 Ophioglossaceae Sensitive 4, 5
14 Botrychium simplex
least
moonwort
G5 S2 Ophioglossaceae 5, PJ
15
Botrychium
virginianum
(Botrypus
virginianus ssp.
europaeus )
rattlesnake
fern
G5 S1 Ophioglossaceae 5, PJ
16 Dryopteris expansa
spreading
woodfern
G5 S1 Dryopteridaceae Sensitive 4, 5
17
Equisetum
variegatum
(Hippochaete
variegata)
variegated
scouringrus
h
G5 S1 Equisetaceae Sensitive 4, 5
18
Gymnocarpium
dryopteris
western
oakfern
G5 S2S3 Dryopteridaceae 5, 11, PJ
19 Isoëtes occidentalis
western
quillwort
G4G5 S1S2 Isoetaceae 5, 9
20
Isoëtes tenella
(I.echiniospora)
spiny‐spore
quillwort
G5?T5? S2 Isoetaceae 5,9
19 Isoëtes occidentalis
western
quillwort
G4G5 S1S2 Isoetaceae 5, 9
20
Isoëtes tenella
(I.echiniospora)
spiny‐spore
quillwort
G5?T5? S2 Isoetaceae 5,9
21 Pellaea wrightiana
Wright's
cliffbrake
G5 S2 Pteridaceae 5, 9
22
Polypodium
saximontanum
Rocky
Mountain
polypody
G3? S2 Polypodiaceae Sensitive 4, 5

16. 23
Selaginella
weatherbiana
Weatherby'
s Spike‐
moss
G3G4 S3S4
Sensitive,
Map #s 15,
16, 20
(BCCP 1995,
1999)
Sensitive 4, 5, 7
1
Anacolia
laevisphaera
anacolia
moss
G5? S1S3 Bartramiaceae
PJ, vetted by
Dr.
Wittmann
2 Anacolia menziesii
Menzies'
anacolia
moss
G4 S1S3 Bartramiaceae
PJ, vetted by
Dr.
Wittmann
3 Andreaea rupestris
andreaea
moss
G5 S1S3 Andreaeaceae Sensitive
PJ, vetted by
Dr.
Wittmann
4 Anoectangium hallii Pottiaceae
PJ, vetted by
Dr.
Wittmann
5
Aulacomnium
palustre var.
imbricatum
aulacomniu
m moss
G5TNR S1S3 Aulacomniaceae Sensitive
PJ, vetted by
Dr.
Wittmann
6
Brachythecium
hyalotapetum
brachytheci
um moss
Brachytheciaceae
PJ, vetted by
Dr.
Wittmann
7
Bryoerythrophyllum
ferruginascens
bryoerythro
phyllum
moss
G3G4 S1S3 Pottiaceae Sensitive
PJ, vetted by
Dr.
Wittmann
8
Bryum alpinum
(Imbribryum
alpinum )
alpine
bryum moss
G4G5 S1S3 Bryaceae Sensitive
PJ, vetted by
Dr.
Wittmann
9
Campylopus
schimperi
Schimper's
campylopus
moss
G3G4 S1S3 Dicranaceae Sensitive
PJ, vetted by
Dr.
Wittmann
10
Didymodon
anserinocapitatus
G1 S1 Pottiaceae
PJ, vetted by
Dr.
Wittmann
11
Grimmia mollis
(Hydrogrimmia
mollis)
grimmia dry
rock moss
G3G5 S1S3 Grimmiaceae Sensitive
PJ, vetted by
Dr.
Wittmann
12 Grimmia teretinervis
grimmia dry
rock moss
G3G5 S1S3 Grimmiaceae Sensitive
PJ, vetted by
Dr.
Wittmann
13
Gymnomitrion
corallioides
G4G5 S1S3 Gymnomitriaceae Sensitive
PJ, vetted by
Dr.
Wittmann
NONVASCULAR

17. 14
Hylocomiastrum
pyrenaicum
hylocomiast
rum moss
G4G5 S1S3 Hylocomiaceae Sensitive
PJ, vetted by
Dr.
Wittmann
15
Hylocomium
alaskanum
splendid
feather
moss
G5 S1S3 Hylocomiaceae Sensitive
PJ, vetted by
Dr.
Wittmann
16
Leptopterigynandru
m austro‐alpinum
alpine
leptopterigy
nandrum
moss
G3G5 S1S3 Leskeaceae Sensitive
PJ, vetted by
Dr.
Wittmann
17 Mnium blyttii
Blytt's
calcareous
moss
G5 S1S3 Mniaceae Sensitive
PJ, vetted by
Dr.
Wittmann
18 Nardia geoscyphus G5 S1S3 Jungermanniaceae Sensitive
PJ, vetted by
Dr.
Wittmann
19 Oreas martiana oreas moss G5? S1S3 Dicranaceae Sensitive
PJ, vetted by
Dr.
Wittmann
20
Plagiothecium
cavifolium
plagiotheciu
m moss
G5 S1S3 Plagiotheciaceae Sensitive
PJ, vetted by
Dr.
Wittmann
21
Pleurozium
schreberi
Schreber's
big red stem
moss,
feathermoss
G5 S1S3 Hylocomiaceae Sensitive
PJ, vetted by
Dr.
Wittmann
22 Pohila tundrae
Tundra
pohlia moss
G2G3 S1S3 Dryaceae Sensitive
PJ, vetted by
Dr.
Wittmann
23
Ptilium crista‐
castrensis
knights
plume moss
G5 S1S3 Hypnaceae
PJ, vetted by
Dr.
Wittmann
24 Rhytidiopsis robusta
robust
rhytidiopsis
moss
Hylocomiaceae
PJ, vetted by
Dr.
Wittmann
25
Rhytidiadelpus
triqetrus
rough goose
neck moss
Hylocomiaceae
PJ, vetted by
Dr.
Wittmann
26 Roellia roellii Roell's moss G4 S1S3 Bryaceae Sensitive
PJ, vetted by
Dr.
Wittmann
27
Sphagnum
angustifolium
sphagnum G5 S2 Sphagnaceae Sensitive Sensitive
PJ, vetted by
Dr.
Wittmann

18. 28
Sphagnum
contortum
contorted
sphagnum
G5 S1S3 Sphagnaceae Sensitive
PJ, vetted by
Dr.
Wittmann
1 Aristida basiramea
forked
threeawn
G5 S1 Poaceae
Sensitive,
Map # 6
(32) (BCCP
1986); Map
#4 (BCCP
1995, 1999)
4, 11
2 Calypso bulbosa
fairy slipper
orchid
G5 Orchidaceae 3
3
Carex capitata ssp.
arctogena
capitate
sedge
G5T4? S1 Cyperaceae 5, 12, PJ
4 Carex conoidea
openfield
sedge
G5 S1 Cyperaceae 5, 11, PJ
5 Carex crawei
Crawe's
sedge
G5 S1 Cyperaceae 5, 6
6 Carex diandra
lesser
panicled
sedge
G5 S1 Cyperaceae Sensitive Sensitive 4, 5
7 Carex lasiocarpa
whollyfruit
sedge
G5 S1 Cyperaceae 5, 11, PJ
8 Carex limosa mud sedge G5 S2 Cyperaceae Sensitive 5, 11
9 Carex livida livid sedge G5 S1 Cyperaceae Sensitive 4, 5, 11
10 Carex sartwellii
Sartwell's
sedge
G4G5 S1 Cyperaceae 5, 11
11 Carex saximontana
Rocky
Mountain
sedge
G5 S1 Cyperaceae
Sensitive,
Map #16
(BCCP 1995,
1999)
5, PJ
12 Carex sprengelii
Sprengel's
sedge
G5? S2 Cyperaceae 5, 6
13 Carex torreyi
Torrey
sedge
G4 S1 5, PJ
14
Cypripedium
parviflorum (C.
calceolus ssp.
parviflorum)
lesser
yellow
lady's
slipper
G5 S2 Orchidaceae 3, 5
MONOCOTS

19. 15
Cypripedium
fasciculatum
clustered
lady's
slipper
G4 S3S4 Orchidaceae Sensitive 3
16
Cypripedium
parviflorum var.
pubescens
greater
yellow
lady's
slipper
G5 S2 Orchidaceae Sensitive 3
17
Dichanthelium
acuminatum var.
sericeum
Pacific
panicgrass
G5TNR S1 Poaceae 5, 11
18 Eriophorum gracile
slender
cottongrass
G5 S1 Cyperaceae Sensitive 4, 5, 11, PJ
20
Juncus
brachycephalus
smallhead
rush
G5 S1 Juncaceae 5, 6?, PJ
21
Juncus tweedyi (J.
brevicaudatus )
Tweedy's
rush
G3Q S1 Juncaceae Sensitive 4, 5
22 Juncus vaseyi Vasey's rush G5? S1 Juncaceae Sensitive 4, 5, PJ
23
Kobresia
simpliciuscula
simple bog
sedge
G5 S2 Cyperaceae Sensitive 4, 5, PJ
24
Lilium
philadelphicum
wood lily G5 S3S4 Liliaceae Sensitive 3
25 Listera borealis
northern
twayblade
G4 S2 Orchidaceae Sensitive 4, 5, PJ
26
Listera
convallarioides
broadlipped
twayblade
G5 S2 Orchidaceae Sensitive
Sensitive,
Map # 11,
16, 19
(BCCP 1995,
1999)
4, 5, PJ
28
Malaxis brachypoda
(M. monophyllos
ssp. brachypoda )
white
adder's‐
mouth
orchid
G4Q S1 Orchidaceae Sensitive
Sensitive,
Map #16
(BCCP 1995,
1999)
4, 5, 11
29 Phippsia algida icegrass G5 S2 Poaceae
Sensitive,
Map #9
(BCCP 1995,
1999)
5, 8, 9, 11,
PJ
33
Sisyrinchium
pallidum
pale blue‐
eyed grass
G2G3 S2 Iridaceae Sensitive 5, 11, PJ

20. 35 Spiranthes diluvialis
Ute ladies'‐
tresses
G2G3 S2 LT Orchidaceae
Sensitive,
Map #17
(BCCP
1999)
1
1 Aletes humilis
Colorado
aletes
G2G3 S2S3 Apiaceae Sensitive 2, 4, 7
2 Amorpha nana
dwarf
leadplant
G5 S1S2 Fabaceae
Sensitive,
Map #16,
21, 22
(BCCP 1995,
1999)
5, 9
3 Apios americana
American
groundnut
G5 S1 Fabaceae
Sensitive,
Map # 5
(31) (BCCP
1986)
Map #5
(BCCP 1995,
1999)
4, 5, 6, 11
4
Aquilegia
saximontana
Rocky
Mountain
blue
columbine
G3 S3 Ranunculaceae Sensitive 3, 4, 5
5
Artemisia
pattersonii
Patterson's
wormwood
G3G4 S1S2 Asteraceae Sensitive 4, 5
7
Asclepias
stenophylla
narrow‐
leaved
milkweed
G4G5 S2 Asclepiadaceae 5, 9, PJ
9 Castilleja puberula
shortflower
Indian
paintbrush,
downy
indian‐
paintbrush
G2G3 S2S3 Schrophulariaceae Sensitive 4, 5, 7
10
Crataegus
chrysocarpa
fireberry,
yellow
hawthorn
G5 S1 Rosaceae 5, PJ
11 Draba crassa
thickleaf
draba
G3 S3 Brassicaceae Sensitve 4, 5, 9
DICOTS

21. 12
Draba
exunguiculata
clawless
draba
G2 S2 Brassicaceae Sensitive 2, 9
13 Draba fladnizensis
Austrian
draba, arctic
draba
G4 S2S3 Brassicaceae Sensitive
14 Draba grayanax
Gray's
draba
G2 S2 Brassicaceae Sensitive Sensitive 2, 4
15 Draba porsildii
Porsild's
draba
G3G4 S1 Brassicaceae Sensitive 4, 5, 9
16
Draba
streptobrachia
alpine
tundra
draba
G3 S3 Brassicaceae Sensitive 4, 5, 9
17
Drymaria effusa var.
depressa
pinewoods
drymary,
spreading
drymaria
G4T4 S1 Caryophyllaceae 5, 11
18
Eustoma exaltatum
ssp. russellianum
(Eustoma
grandiflorum)
showy
prairie
gentian
G5 S3S4 Gentianaceae
Sensitive,
Map #12,
18 (BCCP
1995, 1999)
Sensitive 4, 5, 6
19
Gaura neomexicana
ssp. coloradensis
Colorado
butterfly
plant
G3T2 S1 LT Onagraceae 1
20 Liatris ligulistylis
Rocky
Mountain
blazing star,
gay‐feather
G5? S1 Asteraceae Sensitive 4, 5, 8
21
Machaeranthera
coloradoensis
Colorado
tansyaster
G3 S3 Asteraceae Sensitive 4, 5
22
Mentzelia sinuata
(Nuttallia sinuata ),
(Nuttallia
multiflora )
leechleaf
blazingstar,
wavy‐leaf
stickleaf
G3 S3 Loasaceae Sensitive 4, 5, 7
23
Mimulus
gemmiparus
Rocky
Mountain
monkeyflow
er, budding
monkeyflow
er
G1 S1 C Schrophulariaceae Sensitive Sensitive 1, 2

22. 24 Packera debilis
weak
groundsel
G4 S1 Asteraceae 5, 9
25
Papaver radicatum
ssp. kluanense (P.
kluanense, P.
lapponicum ssp.
occidentale )
rooted
poppy,
alpine
poppy
G5T3T4 S3S4 Papaveraceae Sensitive 4, 5, 9
26 Parnassia kotzebuei
Kotzebue's
grass of
parnassus
G5 S2 Saxifragaceae Sensitive Sensitive 4, 5, 9
27
Pediocactus
simpsonii
mountain
ball cactus
G4 Cactaceae Sensitive 3, 4
28
Penstemon
harbourii
Harbour's
beardtongu
e
G3G4 S3S4 Schrophulariaceae Sensitive 4, 5, 9
30 Physaria bellii
Bell's
twinpod
G2G3 S2S3 Brassicaceae
Sensitive,
Map #s 1
(25), 2 (26),
3 (27), 7
(28), 8 (29)
(BCCP
1986), Map
# 1, 2, 3, 7,
8, 10, 13, 14
(BCCP 1995,
1999)
2, 9
31
Physaria bellii x
vitulifera
twinpod
hybrid
G1Q S1 Brassicaceae 2, 9
32 Potentilla ambigens
silkyleaf
cinquefoil
G3 S1S2 Rosaceae Sensitive 4, 5
33
Potentilla rupincola
(P. effusa var.
rupincola )
rock
cinquefoil
G2 S2 Rosaceae Sensitive Sensitive 2, 4, 7, 9
34 Pyrola picta
whiteveined
wintergreen
, pictureleaf
wintergreen
G4G5 S3S4 Pyrolaceae Sensitive
Sensitive,
Map #16
(BCCP 1995,
1999)
4, 5, 9

23. 35
Ranunculus gelidus
ssp. grayi (R.
karelinii)
ice cold
buttercup,
tundra
buttercup
G4G5 S2 Ranunculaceae Sensitive 4, 9
36 Salix candida
sageleaf
willow
G5 S2 Salicaceae Sensitive 4, 5, 11
37 Salix serissima
autumn
willow
G4 S1 Salicaceae Sensitive Sensitive 4, 5, 11
38 Telesonix jamesii
James'
telesonix
G2 S2 Saxifragaceae Sensitive 2, 4
39
Thelypodium
sagittatum
arrow
thelypody
G4 S1 Brassicaceae 5, 11
40 Tonestus lyallii
Lyall's
goldenweed
G5 S1? Asteraceae Sensitive 4, 5, 9
41 Utricularia minor
lesser
bladderwor
t
G5 S2 Lentibulariaceae Sensitive 4, 5
42
Utricularia
ochroleuca
yellowishw
hite
bladderwor
t
G4? S1? Lentibulariaceae 5, 11
43 Viola pedatifida
prairie
violet
G5 S1 Violaceae 5, 12
44 Viola selkirkii
Selkirk's
violet
G5? S1 Violaceae Sensitive Sensitive 4, 5, 9
DEFINITIONS
Federal Status
ESA, United States Endangered Species Act
LE, Listed Endangered
LT, Listed Threatened
C, Candidate for listing
Colorado Natural Heritage Program (CNHP)/NatureServe Imperilment Ranks*
G‐Rank: Global Rank, S‐Rank: Colorado Rank
G/S1, Critically Imperiled
G/S2, Imperiled
G/S3, Vulnerable to extirpation, typically between 21‐100 occurrences.

24. G#T#, Trinomial rank (T) is used for subspecies or varieties. These species or
subspecies are ranked on the same criteria as G1‐ G5.
SNR, State not ranked. CNHP has not yet looked at this species.
TNR, Not yet ranked globally due to lack of information.
*Notes: Where two numbers appear in a global or state rank, e.g., S2S3, the actual rank of
the element falls between the two numbers. CNHP experts tend to round up to the more
conservative number, e.g., if S2S3, consider the species a ‘S2’ until further information is
available (Jill Handwerk, personal communication).
G/S?, Unranked. Some evidence that species may be imperiled, but awaiting formal
rarity ranking.
G/SU, Unrankable due to lack of information or substatially conflicting information.
GQ, Indicates uncertainty about taxonomic status.
G#?, Indicates uncertainty about an assigned global rank.

25. Appendix 3: POS Sensitive GIS Data
March 26, 2015
Dataset Location
Bats
Breed Bird Points V:gispawildlifeWILDLIFE.gdbbirdsBCPOS_BBS
Bristlecone pine V:gispaForestryGeodatabasesForestry_Fire.gdbForestryDataOldGrowth
CNHP Data V:gispacnhp
Conceptual Trails V:gispatrailsTrails.gdbTrailsConceptual_Trails
Historic Sites V:gispaHistoric PreservationHistoric.gdbBCPOS_Sites
Historic Surveys V:gispaHistoric PreservationHistoric.gdbBCPOS_Sites_Polygons
Northern Leopard Frog
Open Space Under Negotiation EDITGIS1PARKSOPENSPACE.POS.OPEN_SPACE
Raptor nests V:gispawildlifeWILDLIFE.gdbbirdsRaptorNests
Raptor/Owl Surveys V:gispawildlifeWILDLIFE.gdbbirdsAcousticalSurveys
Raptor/Owl Surveys V:gispawildlifeWILDLIFE.gdbbirdsBroadcastSurveys
Rare Plant Points V:gispaplantsPlant_Ecology.gdbRare_PlantsRare_Plants_points
Rare Plant Polygons V:gispaplantsPlant_Ecology.gdbRare_PlantsRare_Plants_poly
Social Trails V:gispatrailsTrails.gdbTrailsSocial_Trails
Steamboat Mtn Sweatlodge
Trail counters V:gispatrailsTrails.gdbTrailFeaturesTrail_Counters
Veg Mapping (sens species only) EDITGIS1PARKSOPENSPACE.POS.VEGMAPPING_POLYGONS
Weather stations
Weather stations
Wetlands V:gispaplantsPlant_Ecology.gdbWetlands
Wetlands EDITGIS1ParksOpenSpace.POS.PLANTS_WETLANDS_*
Wetlands REGIS BOCO.sdeBOCO.PARKSOPENSPACE.PA_WETLANDS_OS
Wetlands REGIS BOCO.sdeBOCO.PARKSOPENSPACE.PA_WETLANDS_WWE