UTG0 Export Config File

UTG0 Config File Format

The config file used by the UTG0 module allows the following 'GML' feature records to be created from the associated DGN element types:

  1. TopographicArea (from DGN element types: Shape, Complex Shape)
  2. TopographicPoint (from DGN element types: Cell, Shared Cell)
  3. TopographicLine (from DGN element types: Line, Linestring, Complex Chain)
  4. CartographicText (from DGN element types: Text, Text Node)
  5. CartographicSymbol (from DGN element types: Cell, Shared Cell)
  6. BoundaryLine (from DGN element types: Line, Linestring, Complex Chain)

Database Section

The config file allows the operator to specifiy the name of a database to connect to. The name of the database is defined as follows:

dhp11

The value 'dhp11' - between the tag defines the name of the database connection string. This is used by the UTG0 module to establish a connection to the database 'dhp11'.

NOTE: The value between the tag is the equivalent of entering the following command in the Microstation 'keyin' window:
dbdhp11

This requires an existing database 'connection' to be already established.
For example - if an 'ODBC' datasource has been setup and named as 'dhp11db1' - then the tag value would be set to:

dhp11db1

TopographicArea? Section

This allows the operator to define the following Microstation DGN 'element' types to be exported as GML '!TopographicArea' record:
  1. Shape (Element Type 6)
  2. Complex Shape (Element Type 14)

The following section is an example of how the operator would setup the 'config' file to 'export' a specific DGN 'Shape' element as a GML '!TopographicArea' feature:

- The first line of the above section - beginning with DGN element type as a SHAPE. The 'colour, weight, style, level' fields help identify a specific DGN element by its symbology.<br /> - The second line beginning with GML file. The 'code="0008"' value is the elements 'feature code' - as it will be output to the GML file. The 'type="osgb:!TopographicArea' section shows how the type of GML record that will be created for the identified DGN element.<br />

TopographicLine? Section

This allows the operator to define the following Microstation DGN 'element' types to be exported as GML '!TopographicLine' record:
  1. Line (Element Type 3)
  2. LineString (Element Type 4)
  3. Complex String (Element Type 12)

The following section is an example of how the operator would setup the 'config' file to 'export' a specific DGN 'Linear' element as a GML '!TopographicLine' feature:

- The first line of the above section - beginning with DGN element type as a LINESTRING. The 'colour, weight, style, level' fields help identify a specific DGN element by its symbology.<br /> - The second line beginning with GML file. The 'code="0010"' values is the elements 'feature code' - as it will be output to the GML file. The 'type="osgb:!TopographicLine' section shows how the type of GML record that will be created for the identified DGN element.<br />

TopographicPoint? Section

This allows the operator to define the following Microstation DGN 'element' types to be exported as GML '!TopographicPoint' record:
  1. Cell (Element Type 2)
  2. Shared Cell (Element Type 35)

The following section is an example of how the operator would setup the 'config' file to 'export' a specific DGN 'Cell' element as a GML '!TopographicPoint' feature:

MatchFirstComponentSymbology?="Y"/>

- The first line of the above section - beginning with DGN element type as a CELL. The 'colour, weight, style, level' fields help identify a specific DGN element by its symbology.<br /> - The second line beginning with NOTE:
1) For type"2" (a cell) then this value can be set to either 'Y' or 'N'.
i) The 'Y' or 'N' flag is 'case-sensitive' and MUST BE set to uppercase.
ii) If set to 'Y' then the feature will be identified by cell 'name' and feature symbology of the first element of the specified cell.
iii) If set to 'N' then the cell will be identified by cell 'name' and the specified 'level' only.
For type"35" (a shared cell) then this value should always be set as '!MatchFirstComponentSymbology='N' - meaning only the shared cells 'name' and specified 'level' is used to identify a cell.
2) The 'name' value is 'case-sensitive' - all values MUST BE uppercase (i.e. "CIRCLE", "B_POST", etc...)
- The third line beginning with GML file. The 'code="0011"' values is the elements 'feature code' - as it will be output to the GML file. The 'type="osgb:TopographicPoint' section shows how the type of GML record that will be created for the identified DGN element.<br />

CartographicText? Section

This allows the operator to define the following Microstation DGN 'element' types to be exported as GML '!CartographicText' record:
  1. Text (Element Type 17)
  2. Text Node (Element Type 7)

The following section is an example of how the operator would setup the 'config' file to 'export' a specific DGN 'Text' element as a GML '!CartographicText' feature:

- The first line of the above section - beginning with DGN element type as TEXT. The 'colour, weight, style, level' fields help identify a specific DGN element by its symbology.<br /> - The second line beginning with - The third line beginning with GML file. The 'code="1006"' values is the elements 'feature code' as it will be output to the GML file. The 'type="osgb:!CartographicText' section shows how the type of GML record that will be created for the identified DGN element.<br />

NOTE: The UTG0 module only allows a Justification value of between 0-8 to be output for TEXT/TEXTNODE elements. The Justification value is output to the GML file as the tag:
Microstation TEXTNODE elements allow justification values of between: 0-14
This means that ANY TEXTNODE element justification would be output to tag with the following values:

tag Text Node Justification Text Justification
LB: 0 LMB: 0, LB: 3 LB: 0
LC: 1 LMC: 1, LC: 4 LC: 1
LT: 2 LMT: 2, LT: 5 LT: 2
CB: 3 CB: 6 CB: 3
CC: 4 CC 7 CC 4
CT: 5 CT 8 CT 5
RB: 6 RB: 9, RMB: 12 RB: 6
RB: 7 RC: 10, RMC: 13 RB: 7
RB: 8 RT: 11, RMT: 14 RB: 8

CartographicSymbol? Section

This allows the operator to define the following Microstation DGN 'element' types to be exported as GML '!CartographicSymbol' record:
  1. Cell (Element Type 2)
  2. Shared Cell (Element Type 35)

NOTE: A CartographicSymbol is very similar to a TopographicPoint - except that the 'orientation' and 'scale' values (for a specific DGN 'cell' element) are output for a CartographicSymbol record. A TopographicPoint record DOES NOT contain 'tags' for either of these values.

The following section is an example of how the operator would setup the 'config' file to 'export' a specific DGN 'Cell' element as a GML '!CartographicSymbol' feature:

MatchFirstComponentSymbology?="Y"/>

- The first line of the above section - beginning with DGN element type as a CELL. The 'colour, weight, style, level' fields help identify a specific DGN element by its symbology.<br /> - The second line beginning with NOTE:
1) For type"2" (a cell) then this value can be set to either 'Y' or 'N'.
i) The 'Y' or 'N' flag is 'case-sensitive' and MUST BE set to uppercase.
ii) If set to 'Y' then the feature will be identified by cell 'name' and feature symbology of the first element of the specified cell.
iii) If set to 'N' then the cell will be identified by cell 'name' and the specified 'level' only.
For type"35" (a shared cell) then this value should always be set as '!MatchFirstComponentSymbology='N' - meaning only the shared cells 'name' and specified 'level' is used to identify a cell.
2) The 'name' value is 'case-sensitive' - all values MUST BE uppercase (i.e. "CIRCLE", "BSEED", etc...)
- The third line beginning with GML file. The 'code="0321"' values is the elements 'feature code' - as it will be output to the GML file. The 'type="osgb:!CartographicSymbol' section shows how the type of GML record that will be created for the identified DGN element.<br />

BoundaryLine? Section

This allows the operator to define the following Microstation DGN 'element' types to be exported as GML '!BoundaryLine' record:
  1. Line (Element Type 3)
  2. LineString (Element Type 4)
  3. Complex String (Element Type 12)

The following section is an example of how the operator would setup the 'config' file to 'export' a specific DGN 'Linear' element as a GML '!BoundaryLine' feature:

- The first line of the above section - beginning with DGN element type as a LINESTRING. The 'colour, weight, style, level' fields help identify a specific DGN element by its symbology.<br /> - The second line beginning with GML file. The 'code="10136"' values is the elements 'feature code' - as it will be output to the GML file. The 'type="osgb:!BoundaryLine' section shows how the type of GML record that will be created for the identified DGN element.<br />

Attributes Section

For any DGN feature that has a linkages to an existing database table - the UTG0 module allows a database tables record - for an associated DGN feature - to be output as attribute tag data to a GML file.

NOTE:
For attribute tag records to be created a valid 'Database' connection needs to have been setup/established and a valid /section will need to exist in the config file (see 'Database Section' above for more information).

The config file allows associated database table record information, associated with a specific DGN feature being 'exported' - to be output as 'attribute' tag/records to a GML file.
A standard 'attribute' section can be specified that will work for all of the above GML record sections which includes: TopographicArea, TopographicLine, TopographicPoint, CartographicText, CartographicSymbol

The following section is an example of how an operator can select ALL columns for a specific database table to be output as 'attribute' tags for an associated DGN element:

*

- The first line of the above section - beginning with DGN element. The 'table="main"' specifies the name of the database table that the DGN element is associated with. The '*' character signifies that ALL colums from the database table 'MAIN' are to be output as 'attribute' tags to the GML file.<br />

NOTE:
The '*' character is in effect the 'select all' character from an SQL statement. For example if specific columns where only required from a related database tables these could be 'set' instead of the '*' character.
i.e. To return only the columns 'ID, MSLINK' from table 'MAIN' then the following would exists in the config file:

ID, MSLINK

This would mean that only 'attributes' tags would be generated for ID and MSLINK.

Example Config File

0865

* * *

MatchFirstComponentSymbology?="Y"/> MatchFirstComponentSymbology?="N"/> MatchFirstComponentSymbology?="Y"/> MatchFirstComponentSymbology?="N"/>

Topic revision: r1 - 12 May 2011 - 12:00:09 - WikiGuest
 

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback