SEPM Products 2017-02 · PDF fileThe following gives a quick overview over the SEPM products...

© Copyright SEPM 2017

SEPM Products 2017-02

SEPM X-Database

SEPM X-Translator

SEPM X-Raster

SEPM NEPLAN Interface

SEPM SIA405 Interface

SEPM ISYBAU Interface

Product Description

SEPM Product Description


2

Document Data

Key Value

Abstract This document describes the SEPM products X-Database, X-Translator, X-Raster and SEPM Interfaces

Version 2017-02

Disclaimers

All logos and trademarks in this document are property of their respective owners.

Contact

Software Engineering and Project Management

Gerliswilstrasse 42 CH-6020 Emmenbrücke Switzerland

Tel +41 79 632 28 20 Fax +41 41 260 57 20

www.sepm.ch

[email protected]

http://www.sepm.ch/



3

Contents

1 Introduction 6

1.1 Glossary .......................................................................................................... 8

2 X-Database 9

2.1 Overview ......................................................................................................... 9 2.2 X-Database "Sia Geo405" ............................................................................. 10

2.2.1 Data Models ......................................................................................... 10 2.2.2 Example ............................................................................................... 10

2.3 X-Database "Swisstopo" ................................................................................ 11 2.3.1 Overview .............................................................................................. 11 2.3.2 Data models ......................................................................................... 11

3 X-Translator 15

3.1 Introduction ................................................................................................... 15 3.1.1 Overview .............................................................................................. 15 3.1.2 Supported Formats ............................................................................... 15

3.2 Use ................................................................................................................ 16 3.2.1 Import ................................................................................................... 16 3.2.2 Export ................................................................................................... 19

3.3 Functionality .................................................................................................. 21 3.3.1 Source, Target, Mapping, Options ........................................................ 21 3.3.2 Smallworld Export................................................................................. 22 3.3.3 Support for custom style methods and dimensions .............................. 23 3.3.4 Export predicates ................................................................................. 24 3.3.5 Coordinate system conversion ............................................................. 24 3.3.6 Worlds .................................................................................................. 25 3.3.7 "Simple GUI" ........................................................................................ 25 3.3.8 Options ................................................................................................. 26

3.4 Formats ......................................................................................................... 27 3.4.1 TFM/TFD Import and Export ................................................................. 27 3.4.2 DWG/DXF Export ................................................................................. 27 3.4.3 DWG/DXF Import ................................................................................. 28 3.4.4 DXF Export ........................................................................................... 28



4

3.4.5 MapInfo MIF ......................................................................................... 28 3.4.6 ESRI Shape .......................................................................................... 28 3.4.7 INTERLIS 1 .......................................................................................... 29 3.4.8 INTERLIS 2.3 ....................................................................................... 29 3.4.9 KML Export ........................................................................................... 30 3.4.10 Text .................................................................................................. 31 3.4.11 Spatial Target .................................................................................. 33 3.4.12 PostGIS ........................................................................................... 34 3.4.13 SVG ................................................................................................. 35

3.5 Installation ..................................................................................................... 36 3.5.1 Software Modules ................................................................................. 36 3.5.2 X-Translator Database ......................................................................... 37

3.6 X-Translator XML Format .............................................................................. 38 3.6.1 Data Model ........................................................................................... 38 3.6.2 Example ............................................................................................... 38

3.7 Configuration ................................................................................................. 40 3.7.1 User Applications.................................................................................. 40 3.7.2 Magik Configuration Features............................................................... 40 3.7.3 Create Database .................................................................................. 41

3.8 Applications ................................................................................................... 43 3.8.1 SIAS ..................................................................................................... 43

3.9 Limitations ..................................................................................................... 44 3.9.1 Platform and Software Requirements ................................................... 44 3.9.2 Smallworld Export ................................................................................. 44 3.9.3 DWG Import ......................................................................................... 44 3.9.4 DWG Export ......................................................................................... 46 3.9.5 DXF Export ........................................................................................... 46 3.9.6 INTERLIS Import .................................................................................. 46 3.9.7 Shape ................................................................................................... 46

4 Interfaces 47

4.1 SIA Interfaces ................................................................................................ 47 4.1.1 SIA Overview ........................................................................................ 47 4.1.2 Interfaces ............................................................................................. 48 4.1.3 User Interface ....................................................................................... 48

4.2 SEPM NEPLAN Interface .............................................................................. 49 4.2.1 Description ........................................................................................... 49

5 X-Raster 50

5.1 Overview ....................................................................................................... 50 5.1.1 Supported Formats ............................................................................... 50 5.1.2 Applications .......................................................................................... 51

5.2 Use ................................................................................................................ 51 5.2.1 Export ................................................................................................... 51 5.2.2 Import ................................................................................................... 53

5.3 Architecture ................................................................................................... 53 5.3.1 Export ................................................................................................... 53 5.3.2 Import ................................................................................................... 53

5.4 Applications ................................................................................................... 54



5

5.4.1 SIAS ..................................................................................................... 54 5.5 Limitations ..................................................................................................... 55

5.5.1 Export ................................................................................................... 55 5.5.2 Import ................................................................................................... 55

5.6 X-Raster Export inside the SEPM X-Translator ............................................. 56 5.6.1 Description ........................................................................................... 56 5.6.2 User Interface ....................................................................................... 56 5.6.3 Use as engine ...................................................................................... 58

6 Licensing 59

6.1 X-Database ................................................................................................... 59 6.1.1 License per seat ................................................................................... 59

6.2 X-Translator / X-Raster ................................................................................. 59 6.2.1 Evaluation license (Node-locked) ......................................................... 59 6.2.2 SEPM "Enterprise" Licenses ................................................................ 59 6.2.3 SEPM X-Translator INTERLIS License ................................................ 59

6.3 SEPM Interfaces ........................................................................................... 59



6

1 Introduction

The products SEPM X-Database, SEPM X-Manager, SEPM X-Translator and

SEPM X-Raster add value to a Smallworld GIS application.

The following screen shows some of the SEPM products in action:

SEPM X-Database objects in the object view at the lower right.

SEPM X-Manager objects in the main map view

SEPM X-Translator loading some data.

Import and export GIS data with X-Translator

X-Manager objects for documenting third party infra-structure

X-Database GIS back-ground data



7

The following gives a quick overview over the SEPM products inside a Smallworld GIS environment:

The SEPM X-Database accommodates GIS background data for a variety of for-mats and data models for different regions (Switzerland, Germany, Europe, World, etc.).

The SEPM X-Manager is a GIS application that provides a simple yet complete da-

ta model covering the most common real world objects for the Construction, Elec-

tricity, Telecom, Mobile, Gas, Water, Waster Water and District Heating do-mains.

The SEPM X-Translator is a data translation interface for importing and exporting

data in MIF, Shape, DXF, DWG, INTERLIS and other formats. The X-Translator transfers geometric and alphanumeric data, as well as visibility and style infor-mation, symbols, relations and enumerators and can be configured in a variety of ways.

SEPM X-Raster is a tool for importing and exporting different raster formats.

SEPM supports its customers for an efficient and successful installation of SEPM

products and offers supplementary services:

❖ Installation, configuration, training, maintenance and support

❖ Integration of new data models into the SEPM X-Database

❖ Development of new functionality for the SEPM X-Manager

❖ Configuration and development of new formats for the SEPM X-Translator

and SEPM X-Raster

This document describes all major features of the SEPM products.

Smallworld Applications

(e.g. NRM, PNI)

SEPM

X-Translator

SEPM

X-Raster

Smallworld 4 SWAF

DXF /DWG MIF Shape INTERLIS 1 INTERLIS 2.3 KML Leica GSI Text Oracle PostGIS

ECW TIFF JPEG

SEPM

X-Database

SEPM

X-Manager



8

1.1 Glossary

In this documen the following terms are frequently used:

Term Description

DWG Binary format for storing AutoCAD drawings.

DXF Ascii format for storing AutoCAD drawings.

ECW Highly compressed raster format

ILI, ITF File extensions of the Swiss INTERLIS 1 format

KML Format used in Google Earth

MIF MapInfo Interchange Format

Shape Format defined by ESRI to store geographic data.

TFM Translator Feature Model: Data Model and Styles of geographic data.

TFD Translator Feature Data: GIS data

TSM Translator Symbol Model. Data model for GIS symbols.

TSD Translator Symbol Data. Data of a GIS symbol library.

X-Translator XML Format developed by SEPM to store and transfer GIS data. A transfer consists of TFM and TFD files and optionally TSM and TSD files



9

2 X-Database

2.1 Overview

The SEPM X-Database provides common data models of geographic background data as ready-to-use Smallworld database.



10

2.2 X-Database "Sia Geo405"

2.2.1 Data Models

The SEPM X-Database SIA implements SIA models 1998 and 2004. The models are available as Smallworld databases:

❖ sia405_1998: SIA 1998 model

❖ sia405_1_d_lk:: SIA 2004 LK model

❖ sia405_1_d_wi: SIA 2004 WI model

INTERLIS 1 data in these data models can be loaded and displayed.

The INTERLIS 2.3 version available in 2010-01 has been removed from the product for now is it was only possible to implement it with changes to the standard.

2.2.2 Example

Loaded SIA INTERLIS 1 data



11

2.3 X-Database "Swisstopo"

2.3.1 Overview

A number of raster and vector data is available from the Swiss cadastral authority

Swisstopo. Many of those can be downloaded for free from the Swisstopo web site.

The SEPM X-Database "Swisstopo" allows loading this data.

The user must acquire the rights for using this data. Also freely available data must be downloaded once from the Swisstopo web site. The user must also agree with the "Finished products license" as well as with all other Swisstopo regulations.

2.3.2 Data models

Raster data

Name Description

Geological map

Ground water map

Gravity map



12

Tecontical map

Vulnerability map

Ice age map

Landsat

Pixel map 1:1Mio grey scale



13

Pixel map 1:1Mio Colour

Swissimage and SPOT

Vector data

Name Description

Outline of pixel maps 1:25'000, 1:50'000, 1:100'000

Swissnames 200

DHM200

Loaded as point geometries with x/y/z attributes



14

Vector 25

Vector25 Modell generated from the INTERLIS file vektor25.ili, Version 1.7, 28.4.2006.

GG25

Generated objects community, district, canton and lake (Gemeinde, Bezirk, Kanton, See)

Vector 200

Zip code boundaries (Stand 2010)

SwissBOUNDARIES3D SwissBUILDINGS3D

Generated objects community, district, canton and lake (Gemeinde, Bezirk, Kanton, See)

Legends to the raster files and other meta-information can be found on the Swis-stopo web site.



15

3 X-Translator

3.1 Introduction

3.1.1 Overview

The SEPM X-Translator is a data translation interface for Smallworld GIS and of-fers powerful import and export functionality. The X-Translator's clean design allows adding new formats easily.

The SEPM X-Translator uses an internal "generic" data model covering geographic and alphanumeric data as well as relations, visibilities, representation and a lot

more (X-Translator Feature Model TFM). The corresponding schema is specified in the document X-Translator 2010-01 XML Format Description.pdf.

3.1.2 Supported Formats

Format Read? Write?

Smallworld Yes Yes

DXF Export (DXF Version 12)

No Yes

DXF/DWG (DXF/DWG bis Autocad 2004)

Yes Yes

INTERLIS1 Yes Yes

INTERLIS 2.3 Yes Yes

MIF Yes Yes

Shape Yes Yes

KML No Yes

TFM/TFD (X-Translator XML Austauschformat)

Yes Yes

Text Yes Yes

Spatial No Yes

PostGIS Yes Yes



16

3.2 Use

This chapter gives a quick example of the workflow necessary for importing and ex-porting a DWG file.

3.2.1 Import

The following DWG file should be imported:



17

To complete this task, the following steps are required:

- Select the file in the DWG source specification menu

Use the command From Trail to define the scale factor of the current trail's map display style. This scale factor is used to convert symbol sizes and text heights.

Also indicate the unit and coordinate system of the source file.

- Select the Smallworld target format, create a trail in the map view and click on Get Trail in the Smallworld Target Specification window:

When clicking on Ok the corresponding data model is created and shown in the user interface.



18

- Map the source to the target objects. The comman Connect all matching can be used for this purpose ( ).

- Load the data with the Transfer action.

The objects are now created in the database.



19

3.2.2 Export

To export data from Smallworld to DWG, the following steps are required:

-

Save the objects and geometries to export as a user visibility in the object control

- Select the Smallworld source format and select the user visibility.



20

- Select the DWG target format and enter the necessary information for the DWG target file. For the conversion of symbol sizes and text heights a scale factor is required, which you can get from the map view with the From Trail command.

- The Transfer action is now used to export the data.



21

3.3 Functionality

3.3.1 Source, Target, Mapping, Options

To transfer data the following information is required

❖ Source Specification of the data source

❖ Target Specification of the data target

❖ Mapping from source to target

❖ Options General and format specific parameters

The source data model is shown in the tree to the left.

The target either defines its own data model (Smallworld or INTERLIS) or does not define its own data model (e.g. MIF or Shape). In the first case the target data mod-el is shown in the tree to the right and a mapping from the source to the target can be defined with the mouse (actions "Connect" or "Connect matching"). This map-ping is also shown in the GUI.

If the target format does not define its own data model (e.g. Shape), the target data is created as defined in the source model.



22

3.3.2 Smallworld Export

A Smallworld export requires the following information:

❖ Data Source All = all objects in the selected tables, Trail = Objects within the trail, Clipboard = Objects within the clipboard

❖ Visibility Saved object control visibility

❖ Display Style Display style to use (e.g. which styles to use)

❖ Style Category Drawing application to use

❖ Geometry Export Mode This mode controls how to treat mapped geometry fields: Top = only the parent geometry gets modeled, Explode = all geome-tries get modeled, MobilePad = corresponds to Top for areas, polylines and points and to Explode for Texts.



23

3.3.3 Support for custom style methods and dimensions

Custom style methods are often used in a Smallworld application to draw objects during the screen refresh without storing those objects in the database. In a similar way dimensions are often painted during screen refresh.

The SEPM X-Translator supports many custom style methods, which means that these methods are called during the export and corresponding geometries are writ-ten to the target format.

Simple example: The motorway object of the cambridge database is drawn as a double-line during screen refresh, even though one single line geometry is stored in the database. By supporting custom style methods, the double-line is exported. The option Resolve style methods allows turning this feature on or off.

Similarly dimensions are implemented like custom draw methods and the X-Translator exports the actually drawn geometries:

Example: Export of DTK2 dimensions



24

3.3.4 Export predicates

It is possible to defined queries which are evaluated during export.

In this example only those roads are exported, that have the name "King" inside of their name:

3.3.5 Coordinate system conversion

The SEPM X-Translator supports the conversion of coordinates. The coordinate systems to use must be configured in Smallworld GIS and visible to the user.



25

3.3.6 Worlds

The selection of worlds for import and export is done through the From Trail com-mand. This allows transferring data from the geographic view but also from internal worlds.

3.3.7 "Simple GUI"

A simple graphic user interface is availabel to execute preconfigured data transfers:

The Simple GUI can be adapted to customer requirements and offers the following functions:

❖ Selection of a predefined configuration. A configuration corresponds to a hardwired data transfer

❖ Selection of the export area through the Trail or

❖ Selection of the export area through a list of database objects

❖ Selection of the target path

All these settings can be activated or deactivated through Magik.



26

3.3.8 Options

Comprehensive Options are available for all areas and are documented in detail in the User-, Admin- and Reference Manuals.



27

3.4 Formats

The SEPM X-Translator supports the following formats:

3.4.1 TFM/TFD Import and Export

Transfer of the X-Translator XML Format.

3.4.2 DWG/DXF Export

The X-Translator allows export of Smallworld GIS data directly to DWG/DXF with a similar appearance in AutoCAD as in Smallworld.

This format uses the external program dwg2sw.exe which reads the Smallworld da-ta from temporary XML files to convert them to DWG.



28

3.4.3 DWG/DXF Import

The X-Translator supports import of DWG/DXF files (up to AutoCAD 200). Some style information can be imported into Smallworld.

This format uses an external program dwg2sw.exe to convert the DWG to tempo-rary XML files.

3.4.4 DXF Export

Export to DXF12. This format is completely Magik-based and corresponds to the "DXF Export" functionality of the "SEPM Translator" product.

3.4.5 MapInfo MIF

Support for the MapInfo MIF format for import and export.

3.4.6 ESRI Shape

Support for the ESRI Shape format for import and export.



29

3.4.7 INTERLIS 1

Any kind of data in the INTERLIS1 format can be read:

❖ ILI file (data model) and ITF file(data) are read directly

❖ Interlis AREA and SURFACE geometries are created in memory

INTERLIS1 files can be exported. For a correct mapping of relations and infor-mation as text orientation and justification Magik configuration is required.

3.4.8 INTERLIS 2.3

INTERLIS 2.3 is supported in the following way:

❖ Creation of the Translator Feature Model TFM directly from the XML Sche-ma created by the INTERLIS Compiler.

❖ Because of the many features of INTERLIS 2, only models tested by SEPM can be used with this interface.

Example configuration of a INTERLIS 2.3 data source



30

3.4.9 KML Export

Smallworld data can be exported to KML and readily used thereafter in Google Earth.

BExample: Smallworld data in Google Earth

The export of colors and line widths is supported.

Symbols are exported to PNG files and then referenced in the corresponding KML point style.

The APIs x_kml_name and x_kml_description can be used for an RWO to refine further the KML output.



31

3.4.10 Text

Text import/export allows transfer of CSV-Ascii files. The following features are available:

❖ Lines with #Dataset and #Collection headers lead to automatically search-ing for the target dataset and collection, which is then used in the Connect Matching command. The external names of the datasets and collections are used.

❖ Lines with headers #x#<external geometry name>, #y#<external geome-

try name> and optionally #z#<external geometry name> lead to a point geometry in the source model

❖ #ID#<external name of an identifier field>. If set, the field is connected with the Connect ID to the target identifier field.

❖ Optionally you can set #ori#<external geometry name> to set the orienta-tion of the point or text geometries (in degrees, 0-360).

❖ Optionally you can set #hjust#<external geometry name>,

#vjust#<external geometry name> to set the text justification. Valid values

are left, center and right for hjust and top, center, bottom for vjust.

❖ In an #ID# column, you can set the special #new# string to create new rec-ords in the Smallworld database.

Example:

❖ Two level crossing objects were exported

❖ The attribute values for Cost Penalty were updated

❖ A new line was added

❖ After selecting the directory containing the updated CSV file in the text

source, the Gis datasets were selected on both sides and the Connect Matching command was called:



32

After loading the data the existing objects were updated and a new object with an-notation "SEPM" was created:



33

3.4.11 Spatial Target

The Spatial Target format permits generating SQL and Magik instance metadata for fast configuration of the Smallworld Oracle SOM.

Example: SQL generated from a source TFM data model

Example: generated Magik file

The x_oracle middleware can then be used to help open the Oracle database with the generated Magik files, once the data model is installed inside Oracle.



34

3.4.12 PostGIS

PostGIS is a freeware database that can also store geographic data. The new

SEPM X-Translator PostGIS interface supports the most import geographic data types supported by PostGIS.

The interface is based on the Smallworld JDBC connection; a suitable Java envi-ronment is therefore required.

In the PostGIS target data can be written directly to the database. Alternatively a text file with SQL-command can be created. The geometries are stored in OpenGIS Well-Known-Text format in this case:

BEGIN; INSERT INTO roads (road_id, roads_geom, road_name) VALUES (1,ST_GeomFromText('LINESTRING(191232 243118,191108 243242)',-1),'Jeff Rd'); INSERT INTO roads (road_id, roads_geom, road_name) VALUES (2,ST_GeomFromText('LINESTRING(189141 244158,189265 244817)',-1),'Geordie Rd'); INSERT INTO roads (road_id, roads_geom, road_name) VALUES (3,ST_GeomFromText('LINESTRING(192783 228138,192612 229814)',-1),'Paul St'); COMMIT;

Based on a source model (Translator Feature Model) CREATE TABLE statements can be generated:

CREATE TABLE sel_trasseabschnitt ( id SERIAL PRIMARY KEY, tid VARCHAR(30), name_nummer VARCHAR(20), art VARCHAR(18), trassebreite BIGINT, lagebestimmung VARCHAR(9), x_translator_history_id BIGINT ); SELECT AddGeometryColumn( 'sel_trasseabschnitt', 'geometrie', 21781, 'LINESTRING', 2 );



35

3.4.13 SVG

Exporting data into Scalable Vector Graphics (SVG) XML files opens interesting opportunities to process GIS data in vector graphics packages such as Adobe Illus-trator or Inkscape.

The following use cases come to mind:

❖ Use of SVG files in web sites instead of bitmaps

❖ Postprocessing of exported SVG files for internal or external company com-munications

The following screen shows how data from a typical Smallworld application...

...was exported to SVG and opened in the program Inkscape:



36

3.5 Installation

3.5.1 Software Modules

The X-Translator is delivered as a layered product and designed for easy installa-tion into an existing Smallworld application:

Load software modules

Customisations such as changes to configuration shared constants or the installa-

tion of the license is usually done in a x_translator_customer module. This module will also depend on the required X-Translator modules, e.g. x_translator_swaf.

The code can then be loaded in an image build script like this:

smallworld_product.add_product( << Path to X-Translator product >> ) sw_module_manager.load_module(:x_translator_customer)

Configure XML files

To make the SEPM tools available to the Smallworld application and to add the ac-tivation commands to some menus the following changes need to be made to the applications XML configuration files:

config.xml <plugin name="x_translator_plugin" class_name="x_translator_plugin" /> gui.xml <action name = "x_translator_plugin.x_activate_translator"/> <action name = "x_raster_plugin.x_activate_raster"/>



37

3.5.2 X-Translator Database

Optionally the X-Translator database can be added to the Smallworld installation for DXF/DWG import.

The X-Translator database provides the same data model as generated by the DWG source format in the X-Translator Model mode for easy DXF/DWG import.

Collection Description

X-Translator History One entry is created for each transfer

X-Translator Event Errors and other events that occur during the transfer

X-Translator Coverage Area object

X-Translator Polyline Line object

X-Translator Point Point object

X-Translator Label Text object



38

3.6 X-Translator XML Format

3.6.1 Data Model

The data model structure used in the TFM (and TSM) is shown in the following graphic. The joins between the objects are 1:n relations. For example, a Model Col-lection can have 0, 1 or more Model Attributes.

3.6.2 Example

The following example shows some of the features of the X-Translator XML format. All elements are specified in the document [XTRXML]. SEPM also delivers a XML Schema file against which X-Translator XML files can be validated.

Translator Feature Model

<?xml version ="1.0" encoding ="UTF-8"?>

<translator version="2009-01">

<model>

<model_dataset name="electricity" external_name="Electricity">

<model_collection name="cable" external_name="Cable">

<model_attribute name="id" external_name="Id" type="uint" size="1"

is_mandatory="True" is_key="True" />

<model_attribute name="known_as" external_name="Known As" type="char"

size="32" is_mandatory="False" />

<model_attribute name="voltage" external_name="Voltage" type="char"

size="10" is_mandatory="True" />

<model_attribute name="status" external_name="Status" type="char"

size="14" is_mandatory="True" />

<model_attribute name="length" external_name="Length" type="float"

size="1" unit="m" is_mandatory="False" />

<model_geometry name="centreline" external_name="Centreline" type="polyline"

is_mandatory="False" is_maingeometry="True" minscale="0"

maxscale="1000000000" manifold="None">

<model_style name="centreline_dv" external_name="centreline_dv" line_dashes="1"

line_width="2" foreground_color="16738560" />

<model_style name="centreline_inactive" external_name="centreline_inactive"

line_dashes="8_8" line_width="2" foreground_color="10751" />

<model_style name="centreline_lv" external_name="centreline_lv" line_dashes="1"


<model_style name="centreline_hv" external_name="centreline_hv" line_dashes="1"


</model_geometry>

</model_collection>

Model Context

Model Collection

Model Attribute Model Style

Model Geometry

Model Dataset

Model Enumerator Value

Model Enumerator

Model

Model Relation



39

<model_collection id_collection="322160" name="substation" external_name="Substation">

<model_attribute name="known_as" external_name="Known As" type="char"

size="32" is_mandatory="False" />

<model_geometry name="location" external_name="Location" type="coverage"



<model_style name="0" external_name="0" line_dashes="1" line_width="1"

line_foreground_color="0" foreground_color="2687231" fill_percent="50" />

</model_geometry>

<model_geometry name="annotation" external_name="Annotation" type="label"



<model_style name="0" external_name="0" foreground_color="0" label_font="fancy"

label_size="6.181818" label_aspect="0.800000" label_is_boxed="False"

label_is_underline="False" label_is_overstrike="False" label_is_clear="False" />

</model_geometry>

</model_collection>

</model_dataset>

</model>

</translator>

Translator Feature Data

<?xml version ="1.0" encoding ="UTF-8"?>

<translator version="2009-01">

<data>

<dataset name="electricity">

<collection name="supply_point">

</collection>

<collection name="cable">

<feature xtrid="502-322126-920930" operation="insert">

<attribute name="id" value="920930" />

<attribute name="known_as" value="Lower Milton Rd LV" />

<attribute name="voltage" value="LV" />

<attribute name="status" value="In service" />

<attribute name="length" value="206.164650" />

<geometry name="centreline" type="polyline" style_name="centreline_lv">

<polyline_part>

<sector>

<c x="545891.595000" y="260101.215000" z="0.000000" />

<c x="545883.220000" y="260110.561000" z="0.000000" />

</sector>

<sector>

<c x="545883.220000" y="260110.561000" z="0.000000" />

<c x="545868.143000" y="260126.025000" z="0.000000" />

<c x="545848.385000" y="260136.904000" z="0.000000" />

<c x="545870.535000" y="260187.099000" z="0.000000" />

<c x="545887.390000" y="260187.099000" z="0.000000" />

</sector>

</polyline_part>

</geometry>

</feature>

</collection>

<collection name="substation">

<feature xtrid="502-322160-914910" operation="insert">

<attribute name="known_as" value="Union Lane Substation" />

<geometry name="location" type="coverage" style_name="0">

<coverage_part>

<outline>

<sector>

<c x="545899.295000" y="260185.703000" z="0.000000" />

<c x="545899.227000" y="260180.666000" z="0.000000" />

<c x="545887.390000" y="260180.666000" z="0.000000" />

<c x="545887.390000" y="260191.594000" z="0.000000" />

<c x="545899.295000" y="260191.594000" z="0.000000" />

<c x="545899.295000" y="260185.703000" z="0.000000" />

</sector>

</outline>

</coverage_part>

</geometry>

<geometry name="annotation" type="label" style_name="0">

<label_part string="Union Lane Substation" x="545866.705000" y="260166.437000"

hjust="left" vjust="bottom" outline_x1="545866.705000" outline_y1="260166.437000"

outline_x2="545919.738492" outline_y2="260166.437000" outline_x3="545919.738492"

outline_y3="260174.164273" outline_x4="545866.705000" outline_y4="260174.164" />

</geometry>

</feature>

</collection>

</dataset>

</data>

</translator>



40

3.7 Configuration

3.7.1 User Applications

The SEPM X-Translator offers flexible configuration possibilities which allow rapid implementation of specific requirements.

The User Application feature is a powerful tool to control the transfer process in many ways:

❖ "Enhancement" of the source data model, for example to add information like target collection names, case coordinate, style information, etc.

❖ Definition of "DXF Information" (DXF layer, linetype, color, text style, block name for each object or for each geometry)

❖ Custom Insert/Update API (for example to change the data before inserting it into the Smallworld database)

❖ Definition of logical attributes or geometry that are calculated on the fly dur-ing the data transfer

❖ Definition of logical collections in the Smallworld source. This allows config-uring an export of two or more source collections into one single target col-lection.

❖ Definition of a report method to create custom reports on the number of ob-jects and geometries transferred.

3.7.2 Magik Configuration Features

The following supplementary configuration features are available:

❖ Simple GUI In this simplified user interface the user can only execute pre-configured data transfers.

❖ Hooks There are different possibilities, to call custom methods at strategic places during the data transfer

❖ Export of rwo_sets

❖ Authorisation: Formats can be authorised through configuration of special groups in the Smallworld authorisation system.

The module x_translator_cambridge contains examples of many of the possible configuration capabilities.



41

3.7.3 Create Database

The X-Translator is particularly well suited for complex data models that are availa-ble electronically. Once mapped to the TFM, Smallworld Case, ACE and Style ob-jects are created with the X-Translator's "Create Database" command.

The following paragraphs demonstrate how this feature was used in the implemen-tation of the X-Database AV01 database:

1) Source data model available as ILI file:

... TABLE LFP1 = !! Triangulationspunkt I-IIIter Ordnung Entstehung: -> LFP1Nachfuehrung; !! Beziehung 1-mc NBIdent: TEXT*12; !! Beziehung 1-m zu Nummerierungsbereich Nummer: TEXT*12; !! Vergabe durch swisstopo Geometrie: LKoord; HoeheGeom: OPTIONAL Hoehe; LageGen: Genauigkeit; LageZuv: Zuverlaessigkeit; HoeheGen: OPTIONAL Genauigkeit; !! abhaengig von HoeheGeom HoeheZuv: OPTIONAL Zuverlaessigkeit; !! abhaengig von HoeheGeom Begehbarkeit: ( begehbar, nicht_begehbar); Punktzeichen: OPTIONAL Versicherungsart; IDENT NBIdent, Nummer; END LFP1; ...

2) The INTERLIS source spec converts the source data model to the TFM

3) The AV01 user application "enhances" the raw TFM model for installation into Smallworld:

... c << m.get_model_collection_by_name( :fixpunktekategorie1, :lfp1 ) c.set_property(:case_coords, "21 99" ) c.set_property(:target_name_prefix, :av_f1_ ) c << m.get_model_collection_by_name( :fixpunktekategorie1, :lfp1pos ) c.set_property(:case_coords, "22 98" ) c.set_property(:target_name_prefix, :av_f1_ ) x_translator_model_style_library.set_style( c, :pos, "xav_fcircle1_small" ) x_translator_model_style_library.set_style( c, :posl, "label_default_small" )

This code snippet of the user application's model method sets the case_coords and target_name_prefix properties. Styles are created for geometries.

4) The "enhanced" data model can now be installed in the Case and applied to a database. The x_create_database() is implemented on the Smallworld target spec:

... _av01_model << _self.get_av01_model() _local l_target_spec << x_translator_smallworld_target_spec.new( :target_world, l_world, :ace_context, "Default",



42

:display_style_name, "Auto", :is_unit, _false, :csys_name, p_sepm_db[:coordinate_system_name], :unit_name, :mm, :db_is_create_case, _true, :db_case_application, l_crs, :db_priority, 10, :db_manifold, "xman", :db_is_create_label, _false, :db_is_apply, _true, :db_dataset_name_for_apply, :av01, :db_is_create_exems, l_db_is_create_exems, :db_exem_path, l_exem_path, :db_rwo_exem_name, l_rwo_exem_name, :db_dataless_rwo_exem, l_dataless_rwo_exem_name, :db_ds_exem_name, l_ds_exem_name, :db_exem_topic, l_exem_topic ) _local l_options << x_translator_options.new() # Get target model l_target_spec.x_set_options(l_options) l_target_spec.x_open_write() l_target_spec.x_create_database( l_av01_model ) ...

4) After the case apply, ACE and Style objects are created:

(not shown, see x_manager_install.magik for an example).



43

3.8 Applications

3.8.1 SIAS

You can easily add a "download to DXF" feature to a SIAS application to allow a user to download the current SIAS main view to DXF.

The x_translator_sis module provides an example of such a service.



44

3.9 Limitations

3.9.1 Platform and Software Requirements

The SEPM X-Translator is available for Smallworld SWAF (400 to 430)

DWG import/export is only available on Windows.

3.9.2 Smallworld Export

Custom draw methods

Drawing methods that perform complex calculations are not supported.

Drawing methods that use the following methods are supported:

Supported Smallworld APIs

draw_line_transform()

fill_line_transform()

draw_sector_transform()

draw_sector_rope_transform()

draw_area_transform()

draw_vtext_transform()

draw_symbol()

draw_link()

draw_polygon()

fill_polygon()

fill_polygon_holes()

paint()*, draw()*

* Only some geometries using this API can be exported.

3.9.3 DWG Import

The following DWG entities are supported:

Entity TFM type Style color Style dahses Style width

3DFACE not supported

3DSOLID not supported

ACAD_PROXY_ENTITY not supported

ARC (1) coverage color linetype lineweight

ARC (2) polyline color linetype lineweight

ATTRIB not supported

BODY not supported

CIRCLE coverage color linetype lineweight

DIMENSION not supported

ELLIPSE coverage color linetype lineweight

HATCH coverage color linetype lineweight



45

IMAGE not supported

INSERT point color linetype lineweight

LEADER not supported

LINE polyline color linetype lineweight

LWPOLYLINE polyline color linetype lineweight

MLINE polyline color linetype lineweight

MTEXT label color linetype lineweight

OLEFRAME not supported

OLE2FRAME not supported

POINT point color linetype lineweight

POLYLINE (1)

Group code 70 = 1

coverage color linetype lineweight

POLYLINE (2)

Group code 70 = 0

polyline color linetype lineweight

RAY not supported

REGION not supported

SEQEND part of other entities

SHAPE not supported

SOLID coverage color linetype lineweight

SPLINE* polyline color linetype lineweight

TEXT label color linetype lineweight

TOLERANCE not supported

TRACE coverage color linetype lineweight

VERTEX part of other entities

VIEWPORT not supported

XLINE not supported

*SPLINE: Only control points are exported as a linear polyline.

The columns Style color, Style dashes and Style width show, which style infor-mation can be extracted from the entity.

Versions

AutoCAD DWG/DXF up to 2004.

Other limitations

No alphanumeric data is transferred.

Only entities in the DWG "Model Space" and Block definitions are transferred. Transfer of entities in the DWG "Paper Space" is not supported.

BYBLOCK colors are imported as black. The color of an INSERT entity are not im-ported (such inserts appear black in Smallworld).

Transfer of holes ("Donut Polygons") is not supported.



46

3.9.4 DWG Export

The following Smallworld data types are supported:

Smallworld Geometry Mapping to DWG/DXF

area, simple_area HATCH, export of holes not supported

chain, simple_chain For each sector, one DWG entity is created

point, simple_point INSERT

text TEXT

dimension Semantic transfer is not supported. Dimensions are exploded into their area, line and text components.

raster not supported

tin not supported

Smallworld Sectors Mapping to DWG/DXF

sector, sector_z POLYLINE

arc ARC if circular, elliptic arcs are vectorised

rational_b_spline POLYLINE (vectorised)

circle CIRCLE

No alphanumeric data is transferred.

Formats

AutoCAD DWG 2004.

3.9.5 DXF Export

DXF Version 12

Surfaces can not be shown filled with this DXF version.

3.9.6 INTERLIS Import

Only 1-n and 0-n relations are supported.

Too long names must be shortened through a mapping table. This is only possible through Magik configuration.

LINEATTR are not supported.

Arcs that are practically a straight segment are imported as a straight segment.

3.9.7 Shape

The version "dBASE 5.0 for Windows" is supported for reading and writing DBF files.



47

4 Interfaces

4.1 SIA Interfaces

4.1.1 SIA Overview

SEPM SIA-Interfaces are used to export data from common Smallworld applica-tions into the models published by the Schweizerischen Ingenieur und Architekten-verein (Swiss association of engineers and architects). These interfaces are based

on the SEPM X-Translator. The following graphic shows the elements of this solu-tion:

For each supported Smallworld application a Magik-script is available to process the following steps:

❖ Configuration of the X-Translator Smallworld-Source to output the objects required by the given SIA model

❖ A X-Translator user application offers Magik-level configuration, for example to define logical attributes

❖ The mapping of the Smallworld-data-model to the SIA-data-model is defined in a X-Translator Mapping defined, that is saved in an XML file

❖ Finally the X-Translator INTERLIS target format is used to generate INTERLIS 1 ITF export data

SIA 405

INTERLIS ITF 1998 LK 2004 LK

Smallworld

NIS Strom PNI FS Gas FS Wasser FS Fernw.

SEPM X-Translator

Smallworld Source Format User Application Mapping loaded from XML INTERLIS Target Format



48

4.1.2 Interfaces

The following interfaces are available at this release:

Name Description

NRM Gas SIA 405 (1998), INTERLIS 1 ITF

Export from NRM Gas to SIA 1998

NRM Gas SIA 405 (2004) LK, INTERLIS 1 ITF

Export from NRM Gas to SIA 2004 LK

NRM Water SIA 405 (1998), INTERLIS 1 ITF

Export from NRM Water to SIA 1998

NRM Water SIA 405 (2004) LK, INTERLIS 1 ITF

Export from NRM Water to SIA 2004 LK

NRM District Heating SIA 405 (1998), INTERLIS 1 ITF

Export from NRM District Heating to SIA 1998

NRM District Heating SIA 405 (2004) LK, INTERLIS 1 ITF

Export from NRM District Heating to SIA 2004 LK

NIS Strom SIA 405 (1998), INTERLIS 1 ITF

Export from NIS Strom to SIA 1998

PNI/Telecom SIA 405 (1998), INTERLIS 1 ITF

Export from PNI to SIA 1998

4.1.3 User Interface

A pre-configured "SEPM Simple GUI" is available to select the desired configura-tion, to enter a path and to start the dump process.



49

4.2 SEPM NEPLAN Interface

4.2.1 Description

The SEPM NEPLAN Interface allows exporting Smallworld data into the NEPLAN network calculation package:

Configurations with different parameterization of the interface can be created, for

example a configuration for the distribution network and one for the medium

voltage network.

The SEPM X-Translator offers many possibilities for configuring the Smallworld source side of the exported objects.

The selection of the Smallworld objects can be done through network following,

through definition of an export area or through formulation of predicates (e.g. only objects of specific voltage levels and with status 'in service').

Different algorithms are available, which can be activated or disabled as required. The most important algorithms are:

❖ Assembly of subsequently connected cables into LINE and a list of associat-ed LINE_SUB.

❖ 'Evaporation' of switches between feeders and busbars in such a way that the switch state is set as logical switch on the outgoing cables.

❖ Generation of a piece of cable with a fuse at the house service

❖ Generation of feeders and loads at the primary or secondary transformer sides

❖ Substation internals can be kept as NEPLAN graphics or they can be pro-jected directly into the GIS-view.

❖ Busbars can be exported as line nodes or as point nodes

The network data is transferred through the NEPLAN ASCII Interface into a NEPLAN project (CDE format). In a future version it is planned to directly update an existing NEPLAN project through NPL (NEPLAN Programming Library).

NIS Strom

V40 V42

SEPM NEPLAN Interface

Based on SEPM X-Translator

Selection of the Smallworld source objects

Algorithms and modes can be activated or disabled.

Import into NEPLAN over the NEPLAN Ascii interface or through NPL

NEPLAN



50

5 X-Raster

5.1 Overview

SEPM X-Raster is an easy to use tool for Smallworld 4 SWAF and offers batch im-port and export of raster data for Smallworld GIS.

In the export implementation any Smallworld geometries (raster and vector) can be exported as raster "tiles".

The import permits loading complete directories of geocoded raster files in one go. Existing raster geometries can be updated based on the file name. The raster im-port can be adapted to different data models (e.g. to support mandatory attributes for objects with raster geometry fields).

5.1.1 Supported Formats

Export

Format Description

TIFF TIFF uncompressed or LZW

JPEG JPEG format

PNG PNG format

ECW Highly compressed raster format

Import

The formats supported by Smallworld can be used:

Format Description

TIFF, GeoTIFF uncompressed TIFF

BMP BMP format



51

5.1.2 Applications

Export

❖ Viewing Application Export raster data, to use them as background data in viewing applications

❖ Storage of scanned maps If you have loaded and trimmed scanned maps into the GIS, you can save them as geocoded raster

❖ GIS Archive Take a "snapshot" of your GIS data at a given date.

Import

❖ Batch load of a large number of raster files.

5.2 Use

5.2.1 Export

The raster tiles to export are defined with the trail. Enter the values for tile size, number of pixels in X/Y direction, etc.



52

After the transfer the exported data can be used in the target system.



53

5.2.2 Import

When importing data a directory containg raster files must be selected. The outlines of the raster geometries are shown as a preview in the Smallworld GIS.

5.3 Architecture

5.3.1 Export

Each tile gets rendered (equivalent to a screen refresh) and saved as JPEG or PNG file. For the target formats TIFF and ECW the exported files are further processed by the external program jpeg2ecw.exe, which permits to convert several source tiles into one single TIFF or ECW file.

The following files are also generated

❖ ArcExplorer 2 project file (*.aep)

❖ ArcExplorer 9.2 project file(*.axl)

❖ A text file to help positioning the raster in AutoCAD

5.3.2 Import

Smallworld supports two raster implementations:

❖ Group4 (internal name general_raster)

❖ Color raster (internal name ds_grid_pyramid)



54

For Group4 raster most parameters must be supplied by the API method ras-ter_parameters().

SEPM X-Raster supports both raster implementations.

5.4 Applications

5.4.1 SIAS

You can easily add a "download to TIFF" feature to a SIAS application to allow a user to download the current SIAS main view to a raster file:

Example: Raster Data downloaded to TIFF and shown in a 3d party viewer

The x_raster_sis module provides an example of such a service.



55

5.5 Limitations

5.5.1 Export

Only Smallworld datasets are supported, e.g. data displayed with SOMS cannot be exported with X-Raster.

5.5.2 Import

GeoTIFF

Only a subset of the GeoTIFF standard is supported:

❖ The freeware listgeo.exe gets used to extract a world file from the GeoTIFF. Therefore write-access to the directory containing the GeoTIFF files is nec-essary.

❖ The GeoTIFF coordinate system is not used.

❖ Only linear transformations from the pixel to the application space are sup-ported.

❖ Non-linear transformations are approximated, in this case the raster data can not be positioned accurately.

API

Raster real world objects often need custom supplementary information (e.g. man-datory fields). An API is available to adapt the import to specific data models. The following configurations are also avaible in the product:

❖ NRM (fs_rasterkarte)

❖ NIS Grundplan

❖ SEPM X-Database

Example: The raster types of the NRM Hintergrund Rasterkarte can be directly se-lected in the X-Raster GUI.



56

5.6 X-Raster Export inside the SEPM X-Translator

5.6.1 Description

Starting with Version 2011-01, X-Raster Export is integrated into the SEPM X-

Translator. A new raster geometry type has been defined in the Translator Feature Model. It is implemented either as an internal Buffer (memory_canvas) or as refer-ence to an external file.

5.6.2 User Interface

The most important parameters of the X-Raster export are available in the new tab 'Raster' in the Smallworld source. Not all parameters, that were available in the X-Raster Plugin product, have been made available. If you are missing something, these can be added again.

An important new feature is that you can set the target coordinate system without needing to change the application coordinate system.



57

The raster tiles to create are shown as red rectangles in the GIS. In this version ras-ter tiles are only created inside the trail, so that no unneeded "white" raster data is generated.

If you set the toggle Export Rasters, a new dataset Raster is added to the Source-TFM containing one collection with a geometry field of type raster.



58

5.6.3 Use as engine

You can use the X-Raster export as an engine, for example to implement a 'Down-load-to-TIFF' service in a web-based solution. _pragma(classify_level=advanced,topic={x_translator}) _method system.xras_2011_01_export() ## Parameters : ## Returns : ## Function : _local l_app << smallworld_product.application(:nis_strom_gwk_application) _local l_maps << l_app.plugin(:maps) # Für Fachschalen-Zeichenmethoden _dynamic !current_application! << l_app

_dynamic !current_map_view! << l_maps.current_map_view _local l_export_area << l_maps.current_map.trail.as_pseudo_geometry _local l_ace_control << l_app.get_ace_control_for( "Strom GWK" ) _local l_ace_context << "Strom GWK" _local l_gs_factory << x_base_manager.get_gs_factory() _local l_path << "D:\Temp\raster1" _local l_options << x_translator_options.new() l_options.x_default_options() l_options.x_set_option(:is_resolve_style_methods,_true) _local l_world << x_translator_world.new() _local l_source_spec << x_translator_smallworld_source_spec.new( :is_vector_export, _false,

:is_raster_export, _true,

:num_pixel_x, 1000,

:num_pixel_y, 1000,

:rounding, 2.0,

:size_x, 50.0,

:size_y, 50.0,

:raster_format, :png,

:raster_csys_name, :de_gk_3_m,

:raster_unit_name, :m,

:data_source, :trail, :export_area, l_export_area, :ace_context, l_ace_context, :gs_factory, l_gs_factory, :display_style_name, "1:500", :source_world, l_world, :visibility, :current, :is_unit, _false, :csys_name, :ch1903, :unit_name, :mm )

_local l_target_spec << x_translator_shape_target_spec.new( :path, l_path, :is_unit, _false, :csys_name, :de_gk_3_m, :unit_name, :m ) _local l_mapping << x_translator_mapping.new() _local l_engine << x_translator.new() l_engine.source_spec << l_source_spec l_engine.target_spec << l_target_spec l_engine.mapping << l_mapping l_engine.options << l_options l_engine.x_transfer()

_return l_engine _endmethod $



59

6 Licensing

6.1 X-Database

6.1.1 License per seat

For the products SEPM X-Database, one license is required per seat.

6.2 X-Translator / X-Raster

6.2.1 Evaluation license (Node-locked)

These licenses can be obtained from [email protected] or from an authorised SEPM Reseller for a limited period of time.

6.2.2 SEPM "Enterprise" Licenses

The license price depends on the number of Smallworld Commit licenses installed at the customer site.

6.2.3 SEPM X-Translator INTERLIS License

The license is valid for "one INTERLIS data model", which means that for each separate ILI-model to support one X-Translator INTERLIS license must be used.

6.3 SEPM Interfaces

A site license is required. Please contact SEPM or a SEPM Reseller for details.

Date post:	18-Mar-2018
Category:	Documents
Upload:	dokhuong
View:	228 times
Download:	3 times

SEPM Products 2017-02 · PDF fileThe following gives a quick overview over the SEPM products...

Documents