Colorado Ownership Management and Protection
~ Mapping the Status and Trends of Colorado's Protected Places ~
Home
Open Space Inventory
Google Earth KML Files
Current COMaP Status
Project Overview
Technical Documents
PDF Maps, Summary Tables and NDIS Links
Collaborators
Contact Info
Links
This page provides various technical documents including a technical summary report, descriptions of attribute values, summary tables, a list of current data inputs, metadata, and the data disclaimer
Technical ReportData Model
Data Inputs
Management Codes
Metadata
Data Disclaimer
Technical Report
A detailed report of our methods including processing steps, data model, attribute information, and data inputs is available here for your review.
Technical Report
We also highlight elements from the report below for quick viewing.
Top of page
Data Model
The attributes used in COMaP to track land stewardship have evolved with the life of the project. While the core attributes have remained constant, we have added a few to more clearly describe features.
| COMaP Attributes | |
|---|---|
| NAME | Recognized name of feature |
| OWNER | Primary owner of feature. Valuable attribute for display and quick queries |
| MANAGER | Primary manager of feature. Valuable attribute for display and quick queries |
| OWNER_DETAIL | Detailed name of owner |
| MANAGER_DETAIL | Detailed name of manager |
| MGMT_CODE | Five digit hierarchical code identifying primary management prescription/use |
| MGMT_DESCRIPTION | Description of MNGT_CODE |
| PUBLIC_ACCESS | Level of public access |
| PROTECTION_MECHANISM | Type of ownership as a proxy for level of protection |
| PROTECTION_TERM | Length of the protection through indicated mechanism |
| PROTECTION_PROCESS | Any specific process applied to achieve the indicated protection (e.g. Wetlands Reserve Program) |
| EASEMENT_HOLDER | Entity holding any easement on the feature |
| DATE_ESTABLISHED | Date feature was established (YYYYMMDD format) |
| FUNDING_PARTNERS | Any organizations that contributed towards the protection of the property |
| GOCO_FUNDING | Did Great Outdoors Colorado (GOCO) funding assist in the property protection |
| GOCO_OS_TYPE | Type of open space feature represented in the database (See technical document for details) |
| HOTLINK | URL website address related to feature |
| SOURCE_DATA | Name of group that provided data and the name of the dataset |
| SOURCE_DATE | Date of the source data for the feature |
| SOURCE_SCALE | Scale of the source data |
| GOCO_LOG | GOCO log number for the project |
| RECEPTION_NO | Reception number at the County Clerk & Recorder's Office of the document bestowing protection upon the parcel |
| ALT_GOCO_LOG | Any other log number assigned by GOCO for the project (often more than one) |
| GOCO_PROJECT_NAME | The name of the project in the GOCO database |
| NOTES | Any notes concerning transfers of CEs or sales of the parcel |
| ACRES | Calculated area of feature, in acres |
| HECTARES | Calculated area of feature, in hectares |
Top of page
Data Inputs
The data input list is available as a PDF document:Source Data List PDF
Top of page
Management Codes
The Management Code is a key attribute in COMaP. This five digit hierarchical code identifies the management prescription or land use for all features. These values are derived from the original source data inputs. The list has grown to a five page spreadsheet! It is best viewed as a PDF and is available here: COMaP v7 Management Code PDF
Top of page
Metadata
The following links provide metadata for COMaP. Complete metadata documentation is also provided with COMaP v6 data.
COMaP v6 Private
COMaP v6 Public
Top of page
Data Disclaimer
While we recognize that COMaP is built from a variety of primary data sources, we believe it is important to have potential users of COMaP explicitly agree to our Data Disclaimer.
The three key points of the Data Disclaimer are:
1. COMaP datasets are not re-distributable. Distribution of COMaP is maintained through the Natural Resource Ecology Lab.
2. The public and private designation on the datasets does not infer distribution rights
3. Any maps or derived products need to designate the various levels of public access. This can be done with map symbology and/or with a printed statement on the map product stating that public access cannot be inferred from the product.
The Data Disclaimer is available here: COMaP Data Disclaimer
Top of page