Map Objects Configuration

Note: this is one of a series of topics outlining the syntax expected in a Studio Mapper System Configuration File.

Warning: updating the system configuration file will affect all Studio Mapper projects with which it is associated. Changes should only be made if you are familiar with the XML format, and changes should be tested in an appropriate environment before rolling out to a live system.

Syntax

In the table below, each XML "tag" refers to an enclosed XML node that may be subordinate to a "parent" node or have one or more child "elements".

Tag Req? Description Parent(s) Element(s)
<MappingObjects> Yes Contains mapping object data types <MappingConfiguration>

<Georeference>

<Properties>

<Features>

<Structures>

<ChannelSamples>

<Areas>

<Profiles>

<Comments>

<Sketches>

<Pictures>

<StratSections>

<ObjectType> No

A node representing a data object container for map data. Supported by the following map data types:

  • Features

  • Stratigraphic Sections

<Features>

<StratSections>

<Name>

<Attributes>

<Template>

<PlotTemplate>

<UseOffset>

<VisualisationFeature>

<VisualisationSourceField>

<VisualisationDestinationField>

<Properties> No Contains map property data types. <MappingObjects> <Attributes>
<Features> No

Contains feature definitions.

Note: unless this configuration element is fully defined, the Features tab will not appear in the Mapping Task Bar.

<MappingObjects> <ObjectType>
<Areas> No Contains channel sample area formatting and threshold information. <MappingObjects>

<Template>

<PlotTemplate>

<ErrorThreshold>

<OverlapThreshold>

<ChannelSamples> No

Contains channel sample attribute definitions.

Note: unless this configuration element is fully defined, the Channel Samples and Areas tabs will not appear in the Mapping Task Bar.

<MappingObjects>

<Name>

<Template>

<PlotTemplate>

<Attributes>

<Comments> No Contains comment formatting and information for plot reports. <MappingObjects>

<Template>

<PlotTemplate>

<ColumnLabel> No The table header cell description used to describe a <SegmentColumn> in the Stratigraphic Sections table. <SegmentColumn…> None
<FieldName> No

Determines the table header cell dimension value (LENGTH, FROM, TO) to be displayed in the Stratigraphic Sections intervals table.

For example:

<FieldName>TO</FieldName>

 <SegmentColumn…> None
<ErrorThreshold> No

A decimal representing a percentage by which the total area of all profiles on a map (Profile Area) can differ from the sum of all sample areas (Sample Area) on the Areas panel.

For example: <ErrorThreshold>0.005 </ErrorThreshold> represents a 0.5% threshold tolerance.

<Areas> None
<Georeference> No Contains georeferenced plane formatting and information for plot reports <MappingObjects>

<Template>

<PlotTemplate>

<Name> Yes The name of a mapping object (feature, structure, sample and so on) <ObjectType> None
<ObjectType> Yes An element describing a mapping object name, template and attribute collection. An object container is available for features, structures and channel samples only.

<Features>

<Structures>

<ChannelSamples>

<Name>

<Template>

<PlotTemplate>

<Attributes>

<OverlapThreshold> No

A decimal representing a percentage overlap of a single channel sample area. An area overlap is the sum of all overlaps with any neighbouring area.

For example:

<OverlapThreshold>0.005 </OverlapThreshold>

represents a 0.5% overlap tolerance.

<Areas> None
<Pictures> No Contains picture object formatting and information for plot reports <MappingObjects>

<Template>

<PlotTemplate>

<PlotTemplate> No A plot template (.dmtpl) that will be used to format data for an output PDF report. This will not affect visual formatting in the 3D or Map windows.

<ObjectType>

<Areas>

<ChannelSamples>

<Comments>

<Georeference>

<Pictures>

<Profiles>

<Sketches>

<SurveyStrings>

<SurveyPoints>

 None
<Profiles> No Contains profile formatting and information for the 3D window and plot reports <MappingObjects>

<Template>

<PlotTemplate>

<SegmentColumn…> No

Represents a table column in the Stratigraphic Sections interval table.

Further qualification is possible to set the column to be the default selected column when a new record is created, using the format:

  • <SegmentColumn default=”TRUE”> or;

  • <SegmentColumn default=”FALSE”>

If the default parameter is missing, FALSE is assumed.

<StratSections>

<ColumnLabel>

<FieldName>

<Sketches> No Contains sketch formatting and information for plot reports <MappingObjects>

<Template>

<PlotTemplate>

<StratSections> No

Contains configuration settings for stratigraphic (vertical) section maps.

For example:

<StratSections>
<SegmentColumn default="TRUE"> <ColumnLabel>Length</ColumnLabel> <FieldName>TO</FieldName> </SegmentColumn> …

You can also choose the vertical section mapping measurement unit using an additional parameter. For example, to log vertical section lengths in centimetres:

<StratSections segmentLengthsInCm="TRUE">

To log in metres, either remove the segmentLengthsInCm parameter string, or use:

<StratSections segmentLengthsInCm="FALSE">

 

 <MappingObjects> <SegmentColumn…>
<Template> No A 3D window template name (in the Studio Mapper project) to apply to a 3D object.

<ObjectType>

<Areas>

<ChannelSamples>

<Comments>

<Georeference>

<Pictures>

<Profiles>

<Sketches>

<SurveyStrings>

<SurveyPoints>

 None

Examples

The following snippet demonstrates the configuration of a Map Properties object, with an example attribute, empty by default:

<MappingConfiguration>
 <MappingObjects>
  <Properties>
   <Attributes>
    <Attribute>
     <ColumnLabel>Survey Station</ColumnLabel>
     <FieldName>SurveyStnNum</FieldName>
     <EntryProperties>
      <Type>TEXT</Type>
     </EntryProperties>
     <Default>_NONE</Default>
    <Attribute>
   </Attributes>
  </MappingObjects>
 </MappingConfiguration>

For more information on defining custom attributes and value validation, see Attributes & Values Configuration.

This snippet sets up a 3D and plot template for sketch map data types. This is probably the simplest example as there is no object container support for sketches, and a similar approach works for channel sample areas, comments, georeference plane data, pictures and profiles:

<MappingConfiguration>
 <MappingObjects>
  <Sketches>
   <Name>Contacts</Name>
   <Template>Demo_Sketch</Template>
   <PlotTemplate>Plot_Sketches</PlotTemplate>
  </Sketches>
 </MappingObjects>
</MappingConfiguration>

Similar to the above, this example follows the specification of a custom object in the Features panel in which to store contact, polygon and point mapping data. A similar syntax is used for other map data types supporting multiple 'object' storage containers (which includes channel samples and stratigraphic sections also).

<MappingConfiguration>
 <MappingObjects>
  <Features>
   <ObjectType>
    <Name>Contacts</Name>
    <Template>Demo_Contact</Template>
    <PlotTemplate>Plot_Contact</PlotTemplate>
   </ObjectType>
  </Features>
 </MappingObjects>
</MappingConfiguration>

The following example demonstrates the configuration of a Stratigraphic Section object, with 3 defined segment attributes (FROM, TO and LENGTH) and some per-object configuration. 

<MappingConfiguration>
 <MappingObjects>
  <StratSections>
   <SegmentColumn default="TRUE">
    <ColumnLabel>FROM</ColumnLabel>
    <FieldName>FROM</FieldName>
   </SegmentColumn>
   <SegmentColumn default="TRUE">
    <ColumnLabel>TO</ColumnLabel>
    <FieldName>TO</FieldName>
   </SegmentColumn>
   <SegmentColumn default="TRUE">
    <ColumnLabel>LENGTH</ColumnLabel>
    <FieldName>LENGTH</FieldName>
   </SegmentColumn>
 
    <ObjectType>
     <Name>Strat_Unstable</Name>
     <VisualisationFeature>Auto_Hatch</VisualisationFeature>
     <VisualisationSourceField>Stratigraphy</VisualisationSourceField>
     <VisualisationDestinationField>Stratigraphy</VisualisationDestinationField>
     
     <Template>Demo_Sections</Template>
     <PlotTemplate>Plot_Sections</PlotTemplate>
     
     <UseOffset>TRUE</UseOffset>
     
     <Attributes>
      <Attribute>
       <ColumnLabel>Profile_ID</ColumnLabel>
       <FieldName>PROF_ID</FieldName>
       <TargetItem>SECTION</TargetItem>
       <EntryProperties>
        <Type>TEXT</Type>
       </EntryProperties>
      </Attribute>
     </Attributes>
     </ObjectType>
  </StratSections>
 </MappingObjects>
</MappingConfiguration>