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.
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).
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.
More information on the DSFL format can be found on the web site of GeoForum: http://www.geoforum.dk/DSFL-formatet-10299.aspx
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 |