Configuration Basics

From ObjectVision

Revision as of 15:09, 19 November 2019 by Martin (Talk | contribs)
Jump to: navigation, search

Contents

Getting acquainted

A part of an GeoDMS configuration:

container ExampleProject
{
   container Units
   {
       unit<float32> m   := BaseUnit('m', float32),  cdf  = "Classifications/M3K/Classes";
       unit<float32> m2 := m * m;
   }
   #include <Classifications.dms>
   container SourceData; Using = "Units"
   {
       // BAG is the registration of buildings and addresses in the Netherlands
       container BAG
       {
           unit<uint32> vbo: StorageName = "%SourceDataDir/BagSnapshot/20190101/vbo.fss"
           {
               attribute<string>      identificatie;
               attribute<units/m2> oppervlakte;
           }
       }
   }
}

Hierarchical Structure

Each GeoDMS configuration has a hierarchical structure, used to name items (called tree items) in a context, also known as NameSpace.

Curly bracket characters { and } introduce new levels, all elements within these brackets are subitems of a higher level item (parent).

The use of tabs to indicate the levels is not obligatory but strongly advised. The convention is to position the brackets at the same level as the parent item, subitems are positioned one tab position to the right.

Keywords

In configurations we can find keywords:

Each item is configured with one of the first four keywords, a name and optionally one or more properties. The definition of an item is ended by a semicolon, unless the item has subitems.

Comments

Two forward slashes(//) in a row indicates that the following text is interpreted as comments (like the line : BAG is the registration of buildings and addresses in the Netherlands in the example).

To comment blocks with multiple lines, use /* to start and */ to finish a comment block.

Personal tools