The object mapping parameters are contained between the <ObjectMappings> tags. Each CARIS feature code in this section is mapped to an S-57 feature. There must be at least one object mapping in this section.
Entries are ordered from the most specific to the least specific. The structure and syntax of the object mapping section is similar to other mapping files. To find out more about how object mapping works, see Object Mapping.
The basic structure of the mapping file is shown below.
<Object FeatureCode="DRGARE_*" WildCards="True" Description="An area of the bottom which has been deepened by dredging"> <Filter> <PrimitiveIsEqualTo Primitive="Polygon"/> </Filter> <MapObject> <MapObjectAcronym Acronym="DRGARE"/> <ExecuteAttributeScript Script="assign_depthdrgare" From="CARIS_FCODE"/> </MapObject> </Object> |
The following table describes the tags in the object mappings section.
Tag | Description | Status |
|---|---|---|
| The The The The | Mandatory Optional Optional Optional |
| The | Optional |
| The | Mandatory |
Wildcards
In this example, all CARIS objects with a feature code NASTPHR with one character following the acronym will be matched. For example, NASHTPHR1, NASTPHRA, NASTPHR.
<Object FeatureCode="NASTPHR%" Wildcards="True" |
In this example, all CARIS objects with a feature code NASTPHR with any number of characters following the acronym will be matched. For example, NASHTPHR1, NASHTPHRABC, NASTPHR1A1B2
<Object FeatureCode="NASTPHR*" Wildcards="True" |
Formatted Example
This example matches all CARIS objects with a feature code that starts with one or more digits followed by an underscore and at least one more digits plus a character at the end. For example, 10_20M would match while 10_20MH would not.
<Object FeatureCode="%[0-9]_%[0-9]%1s" Formatted="True" Description="An area of water whose depth is within a defined range of values"> </Object> |
The CARIS mapping file mostly uses the same functions as other mapping files. See Mapping Functions.