Batch Tab

In the Batch Tab you can perform transformation of multiple points given in data files. KMSTrans2 reads and writes a number of different data file formats as described below.
KMSTrans2 uses a command line program in the ./bin subfolder called trogr to perform transformations of data sources like files and databases.
Before performing transformation of files, it is important to note that trogr is linked against the Geospatial Data Abstraction Library (GDAL) which must be installed on your system in order for the program to run. Prepackaged versions of KMSTrans2 will come with a default GDAL installation.

Formats

KMSTrans2 uses the following data formats:

OGR – A library of vector data formats compiled by the Open Source Geospatial Foundation to be used with GDAL
Text – Simple text format which can be modified
DSFL – Format developed for exchange of data by Dansk Selskab for Fotogrammetri og Landmåling (now GeoForum)
KMSformat – Internal data format from Kort & Matrikelstyrelsen (now Geodatastyrelsen)

Generally, input and output data source formats will be the same, except for input formats readable by OGR, where a specific OGR output format can be chosen.

OGR - a range of common vector formats, including various databases, depending on your GDAL installation.

Available input and output vector data formats will depend on your GDAL installation. OGR will try to open an input data source by iteration over available drivers. This behaviour can be overridden by specifying a specific input driver, for instance (if the WFS driver is available):

WFS:http://kortforsyningen.kms.dk/service?servicename=dagi_gml2&service=WFS&version=1.0.0&login=usr_name&password=pass_wd

Refer to the list of OGR formats for more details. Note that many ogr formats will not be available in the default distribution that comes with prepackaged versions of KMSTrans2 for windows. See the GDAL installation page for information on how to enable a "full" installation of GDAL.

TEXT - simple column based text format with one point on each line. The column separator and sequence of coordinates in the columns can be specified in the File2file settings dialog..

When pressing the Open Text settings button, the File2File settings appear. Here the column separators must be set and the sequence of coordinates in the input file must be provided. If the input file contains height information, the “Has z” box is checked.
The File2file settings dialog can also be opened via Settings in the top menu bar.
Examples of valid formats for coordinate lines are:

K-47-200 , 11.75 , 55.10 , 100 , windy
CITY, 9.31, 56.20 , 127, sunny

where X column=2, Y column =3, Z column=4 and the column separator is "," (comma).
Point ID and other attributes can be text or numbers or a combination.
The column separator defaults to all whitespace.

An input system can be specified by using a hash in front of a MiniLabel, for instance:
#geoEetrs89 (geographical coordinates in ETRS89 datum, ellipsoidal heights).
For a description of the MiniLabels please refer to the Mini Labels page.

NOTE: KMSTrans2 expects geographical input coordinates to be in decimal degrees. Generally input coordinates must be decimal numbers without spaces or units. If you have a more complicated format consider using the KMS-format which accepts things like units and spaces in coordinates (and remember to use two spaces as column separator).

KMSformat - A special text format used internally at KMS/GST.

Column separator is *always* at least two spaces and coordinates must have units. The implementation in KMSTrans2 is (still) a 'thin' version of the KMSformat - the region prefix of a coordinate MiniLabel does not infer special parsing / writing of station names.

A line with coordinates could look like:

BUDD 6 143 200.5 m 512 200.12 m ...other attributes for instance height...

The format is:

One point on each line, and each line composed as:

<Station_name> <two_spaces> <X or Y> <two_spaces> <X or Y> <two_spaces> <An optional Z-value - depending on the system> <two_spaces> <extra_attributes>

The order of the coordinates, e.g. X,Y (,Z) or Y,X (,Z) depends on the input system, but generally the KMSformat expects planar coordinates in the order N,E (Northing, Easting).
See the MiniLabels page for more details!

The input system is specified like for the TEXT-format using mini labels as for instance: #utm32_etrs89

NOTE: with the eralier KMStrans software, modifications to the KMS format was possible. This is not possible with KMSTrans2. Files which could be read by KMStrans can therefore not always be read by KMSTrans2, if for instance units, point ID or other information is not included. In such cases, the user is encouraged to use the TEXT format instead.

DSFL - a specific Danish exchange format for vector data.

More information on the DSFL format can be found on the web site of GeoForum: http://www.geoforum.dk/DSFL-formatet-10299.aspx

Updating / overwriting:

For output OGR datasources the behaviour of the program (trogr) is to try to update a datasource if it is an existing directory in the file system and create new layers corresponding to layers in the input datasource. If the output datasource is an existing file, which is not a directory, trogr will try to delete the existing datasource and create a new one (i.e. overwrite).
For the other, textual, formats TEXT, KMSformat and DSFL, the behaviour is always to overwrite an existing file by the same name as the output file.

Coordinate sequence

When working with the TEXT format in KMSTrans2, it is important to know how the program reads x, y and z coordinates. The following table contains examples of coordinate designation for the most common systems used in Denmark.

System	X coordinate/column	Y coordinate/column	Z coordinate/column
DKTM	Easting	Northing	Height
UTM	Easting	Northing	Height
Geographic coordinates	Longitude	Latitude	Height
Cartesian coordinates	X	Y	Z
System 34	X ( i.e. the usual s34 'Westing')	Y	Height

Generally Easting should correspond to X, Northing to Y and Height to Z.