The documents in this section contain recommendations but not requirements. They are “living documents” that may be modified or retired according to changes in technology and the standard itself.
Proposed CMECS Data Structure – A short outline of how CMECS data could be organized in an ESRI file geodatabase structure.
Classifiers Document – Document that presents the physical, chemical, and biological characteristics necessary to assign CMECS unit labels to data. This is of value to those collecting source data that will later be used to develop CMECS habitat maps.
Nomenclature Document – Several examples of how CMECS unit names from several components can be compiled into terminology for CMECS-derived units.
CMECS Concept Map – A graphical representation of the CMECS component framework and hierarchical structure. Useful for understanding how the components relate to each other and which ones might be appropriate for specific projects.
Oregon Estuary Inventory
Crosswalking to CMECS
Crosswalking is the process of converting attributes or data from one classification scheme to another. This may be necessary when integrating legacy data into a new system, or when assembling disparate data sets into a larger framework. There are two types of crosswalks; Conceptual crosswalks which describe the definitional relationships between units in two classification systems, and Data crosswalks which involve re-attribution of digital spatial data. Data crosswalks build on the conceptual relationships but also are influenced by spatial scale and observation methods. Appendix H of the CMECS 2012 document describes best practices for crosswalking data to CMECS. The Implementation Group has prepared conceptual crosswalks to CMECS from the following commonly used classification systems.
In addition, OCM has developed an ESRI ArcGIS tool which converts spatial data (in ESRI shapefile format) into CMECS geodatabase feature layer outputs.