|
EDCS Reference Manual
Concept Mapping from EDCS 3.x to EDCS 4.2 |
|---|
This document describes how environmental concepts are mapped from the EDCS Version 3.x (including, in particular, EDCS Version 3.1) to EDCS Version 4.2.
The EDCS Version 4.2 has no significant changes from EDCS Version 3.x in the manner in which EDCS concepts (classifications, attributes, enumerants, and units of measure) are denoted -- i.e., how each unique concept may be referenced by either humans or software.
In EDCS Version 3.x, there was a dictionary called the EDCS Attribute Value Metadata dictionary that contained concepts which were descriptions of the attribute data value rather than the attribute data value itself.
In EDCS Version 4.2, the EDCS Attribute Value Metadata dictionary has been renamed to the EDCS Attribute Value Characteristics Dictionary, but the meaning of the concepts within the dictionary remain the same. Also, one concept has been removed from the dictionary (SIGNFICANT_DIGITS), and others have had their codes changed. See the mapping tables for the EDCS Attribute Value Metadata concepts.
With EDCS Version 4.2, several additional datatypes have been added to help store the various types of values are associated with EDCS Attributes. For a full description of the data types and where they are used see the EDCS 4.2 Types HTML documentation.
While the concepts encoded using the EDCS Version 3.x are encoded the same way for EDCS Version 4.2, many of the concepts themselves have had their labels and/or codes changed. However, essentially all concepts supported by EDCS Version 3.x are also supported by EDCS Version 4.2, albeit sometimes using a combination of several EDCS Version 4.2 "atomic" concepts. In many cases the EDCS 3.1 concept label will be exactly the same as the EDCS 4.2 concept label, but the code for those labels will be different.
The tables at the end of this section document the mapping of concepts from EDCS Version 3.x to EDCS Version 4.2. In the significant majority of cases, the concept mapping is one-to-one and direct. In some cases, however, the mapping is more complex.
These tables document the mappings for each of the concept types in EDCS Version 3.x: classifications, attributes, enumerants, groups, and metadata. In addition to listing the "EDCS 3.1 Code" and "EDCS 3.1 "Label"" for each concept, each table includes the columns "EDCS 4.2 Concept Mapping Type", "EDCS 4.2 Concept Mapping Information", and "Additional Notes".
The Concept Mapping Types are as follows:
ONE_TO_ZERO - The EDCS Version 3.x concept does not exist in the EDCS Version 4.2. The "EDCS 4.2 Concept Mapping Information" column will be empty.
ONE_TO_ONE - The EDCS Version 3.x concept is mapped directly to a single EDCS Version 4.2 concept. The "EDCS 4.2 Concept Mapping Information" column will contain the symbolic constant of the appropriate EDCS Version 4.2 concept.
ONE_TO_MANY - The EDCS Version 3.x concept possibly maps to two or more different EDCS Version 4.2 concepts. The "EDCS 4.2 Concept Mapping Information" column will be empty and the "Additional Notes" column will contain information about the possible EDCS Version 4.2 concepts.
Example:
CHANGE_IN_DATATYPE - The EDCS Version 3.x concept is mapped directly to a single EDCS Version 4.2 concept, however the data type used to represent the value of the concept has changed.
Examples:
EDCS 3.x Attribute value of type ENUMERANT maps to EDCS 4.2 Attribute value of type BOOLEAN
EAC_UNCOVERING_HEIGHT_INFORMATION
with ENUMERANT value of
EEC_UNCVRHGTINF_KNOWN
maps to
EAC_UNCOVERING_HEIGHT_KNOWN
with the BOOLEAN value of TRUE
EDCS 3.x Attribute value of type ENUMERANT maps to EDCS 4.2 Attribute value of type CONSTRAINED_STRING
EAC_NATIONAL_PAINT_SCHEME
with ENUMERANT value of EEC_NATLPAINTSCHEM_ARGENTINA
maps to
EAC_NATIONAL_PAINT_SCHEME
with the CONSTRAINED_STRING value of "ARGENTINA"
SPECIAL_CASE - These cases will require some human reasoning to determine the best way to realize the EDCS Version 3.x concept in EDCS Version 4.2. Both the "EDCS 4.2 Concept Mapping Information" column and "Additional Notes" column contains information giving recommendations regarding how to handle the specific case.
When the Concept Mapping Type is ONE_TO_ONE or CHANGE_IN_DATATYPE, then the "EDCS 4.2 Concept Mapping Information" column has very specific formatted information in it. It will be one or more of the following possibilities (multiple concepts will be of this form, separated by semicolons):
(Classification)
The symbolic constant of a single
EDCS Version 4.2 classification concept; there will be no
additional information.
(Attribute)
The symbolic constant of a single
EDCS Version 4.2 attribution concept; there will be no
additional information.
(Attribute) -
(value)
The label of a single EDCS Version 4.2 attribute
concept with a specific (value).
The type of the (value) by default is
ENUMERANT, and
the value displayed will be the label of the
ENUMERANT.
However, if the Concept Mapping Type is CHANGE_IN_DATATYPE
then then value will be proceded by the type.
Examples:
ACOUSTIC_CENTRE_FREQUENCY_BAND - BAND_1_HZ
NATIONAL_PAINT_SCHEME - constrained string "LAO_PEOPLES_DEM_REPUBLIC"
UNCOVERING_HEIGHT_KNOWN - boolean EDCS_TRUE
This section describes the EDCS Version 3.x to EDCS Version 4.2 Mapping API functions, data structures, and use examples.
map_3p1_classification.c: A sample program taking a list of EDCS Version 3.x classification codes or labels on the command line, and printing out the associated EDCS Version 4.2 concept mapping information.
Example: To retrieve mapping information for ECC_ANTENNA and ECC_ANTENNA_SUPPORT_MAST:
"map_3p1_classification ANTENNA ANTENNA_SUPPORT_MAST"
OR
"map_3p1_classification 60 61"
Example Output:
"EDCS 3.1 classification ANTENNA maps exactly to the EDCS 4.2 classification symbolic constant ECC_AERIAL
EDCS 3.1 classification ANTENNA_SUPPORT_MAST maps exactly to the EDCS 4.2 classification symbolic constant ECC_AERIAL_SUPPORT_MAST"
map_3p1_attribute.c: A sample program taking a list of EDCS Version 3.x attribute codes or labels on the command line, and printing out the associated EDCS Version 4.2 concept mapping information.
Example: To retrieve mapping information for
EAC_MEDIAN and EAC_MEDIAN_WIDTH:
"map_3p1_attribute MEDIAN MEDIAN_WIDTH"
OR
"map_3p1_attribute 657 658"
Example Output:
"EDCS 3.1 attribute MEDIAN maps exactly to the EDCS 4.2 attribute symbolic constant EAC_LAND_TRNSP_MEDIAN_PRESENT.
EDCS 3.1 attribute MEDIAN_WIDTH maps exactly to the EDCS 4.2 attribute symbolic constant EAC_LAND_TRNSP_MEDIAN_WIDTH."
map_3p1_enumerant.c: A sample program taking a list of comma separated pairs of EDCS Version 3.x attribute codes and enumerant codes or attribute labels and enumerant labels on the command line, and printing out the associated EDCS Version 4.2 concept mapping information.
Example: To find mapping information for EAC_COMMUNICATION_TYPE with the enumerant value of EEC_COMMTY_BEACON, and EAC_CLOUD_CEILING_METHOD with the value of EEC_CLDCEILMETH_RADAR:
"map_3p1_enumerant COMMUNICATION_TYPE,BEACON 196,7
Example Output:
EDCS 3.1 attribute COMMUNICATION_TYPE with enumerant BEACON maps exactly to the EDCS 4.2 attribute symbolic constant EAC_COMMUNICATION_STRUCTURE_TYPE with the enumerant symbolic constant EEC_COMMSTRTY_BEACON
EDCS 3.1 attribute CLOUD_CEILING_METHOD with enumerant RADAR maps exactly to the EDCS 4.2 attribute symbolic constant EAC_ATM_CEILING_METHOD with the enumerant symbolic constant EEC_ATMCEILMETH_RADAR
Concept mapping from EDCS Version 3.x groups
map_3p1_group.c: A sample program taking a list of EDCS Version 3.x group codes or labels on the command line, and printing out the associated EDCS Version 4.2 concept mapping information.
Example: To retrieve mapping information for EGC_GEN_ABSTRACT_CONCEPT and EGC_GEN_BATHYMETRY:
"map_3p1_group ABSTRACT_CONCEPT BATHYMETRY"
OR
"map_3p1_group 1 13"
Example Output:
EDCS 3.1 group ABSTRACT_CONCEPT maps exactly to the EDCS 4.2 group symbolic constant EGC_GEN_ABSTRACT_OBJECT
EDCS 3.1 group BATHYMETRY maps exactly to the EDCS 4.2 group symbolic constant EGC_GEN_WATERBODY_FLOOR
Concept mapping from EDCS Version 3.x metadata
map_3p1_value_characteristic.c: A sample program taking a list of EDCS Version 3.x metadata codes or labels on the command line, and printing out the associated EDCS Version 4.2 concept mapping information.
Example: To retrieve mapping information for EMC_SIGNIFICANT_DIGITS and EMC_TOLERANCE:
"map_3p1_value_characteristic SIGNIFICANT_DIGITS TOLERANCE"
OR
"map_3p1_value_characteristic 12 13"
Example Output:
"EDCS 3.1 metadata SIGNIFICANT_DIGITS maps to
no EDCS 4.2 concept. The concept was deleted.
"Notes: No mapping
EDCS 3.1 metadata TOLERANCE maps exactly to the EDCS 4.2 metadata symbolic constant EVC_TOLERANCE
|