Skip to content

Delivery in SOSI Format

Municipalities can require that the zoning plan be delivered in SOSI format level 4 (with surfaces and properties). A plan constructed in Gemini Terrain according to the construction procedure will satisfy these requirements.

When exporting to SOSI, we can choose between export to three different SOSI versions:

  • 4.5 (for plan data without elevations)
  • 4.3 (for plan data without elevations)
  • 4.2 (for plan data without elevations)

For plans, SOSI version 4.5 is now applicable. The program will export the correct geometry types based on the settings. A prerequisite for correct export is that the correct template has been used when creating the application layers, so that codes and structure are in accordance with the current standard. Note that all plan exports are performed without elevations, neither as 2D or 3D elevation (..HØYDE/NØH).

When we construct a plan in Gemini Terrain, we place the data on several application layers. These can be exported to SOSI with the following procedure:

Procedure

  1. Select all application layers for the plan in the application layer list
  2. Right-click and select Export other formats...
  3. Click Format...
  4. Click Format setup... and check that the settings are correct
  5. Click OK twice
  6. Click Browse...
  7. Enter the file name and click Open...
  8. Click Export

Note

The templates for SOSI version 4.5 contain export directives. This means that you can only perform the set up export in the export directive, which is set up to export to the correct SOSI version and without elevations.
Unit (0.001) and correct product specification (zoning plan/zoning plan proposal) must be selected manually.

Alternatively, we can also export the layers separately. If SOSI control reports errors in the plan, it can often be easier to find the error by checking layer by layer.

It can therefore be useful to have some knowledge of how SOSI files are structured and how the geometry types in Gemini Terrain are linked to SOSI. Below is a small excerpt that is relevant for zoning plans. We refer to the SOSI manual for a complete description of the SOSI standard.

SOSI Format

The SOSI file has this main structure:

.HODE
. DEF
. OBJDEF
.the actual data (data groups)
.SLUTT

Data Groups in SOSI

Data groups always begin with a SOSI group element name. The most used in zoning plans are:

  • .PUNKT/.SYMBOL
  • .KURVE
  • .BUEP
  • .FLATE
  • .TEKST

.SYMBOL is used when we want to include the rotation of point symbols. RPJURPUNKT 1242, 1243 and 1244 depend on using SYMBOL to be able to specify the rotation.

Data groups are numbered with serial numbers for identification within the SOSI file.

Furthermore, data groups can be logically linked together using reference numbers that point to serial numbers for other data groups. This is used, among other things, by the geometry type FLATE.

Each data group can have one or more properties. Note that we call everything except the coordinates properties. Properties are specified with a SOSI name and associated value (e.g.: ..OBJTYPE RpJuridiskLinje).

In Gemini Terrain we have corresponding geometry types. An application layer consists, as known, of two files (.aly and .gmi). The data is stored in the gmi file and it can contain the following geometry types:

  • Line
  • Point
  • Text
  • Polygon

In addition, each geometry type can have an unknown number of properties such as OBJTYPE, etc.

SOSI File Header

The header of the SOSI file contains information that applies to the entire file. The dialog below shows the settings for SOSI.

Note

We see that the fields Municipality no., Measurement method, Accuracy and Visibility are gray. These are no longer valid properties in the header for files in SOSI version 4.5/4.3/4.0.

Normally, the export function in Gemini Terrain sets the correct settings so we don't need to open this dialog. However, this requires that you have used the templates that come with the program (which contain export directives) and that the coordinate system is selected under Settings Gemini Terrain... - Project - General.

For plans, version 4.5 now applies with the associated product specification, Zoning Plan Proposal. When the product specification is in the SOSI file, SOSI control itself finds which controls should be run on the file.

If we open the SOSI file after export, we find the following in the header:

.HODE  
..TEGNSETT ISO8859-1  
..SOSI-VERSJON 4.5  
..SOSI-NIVÅ 4  
..TRANSPAR  
...KOORDSYS 22  
...ORIGO-NØ 0 0  
...ENHET 0.001  
..OMRÅDE  
...MIN-NØ 80919 59406  
...MAX-NØ 81106 59698  
..OBJEKTKATALOG  Regplanforslag 20120416 \* Arealplan Reguleringsplanforslag

Geometry Type: PUNKT, KURVE, BUEP and TEKST

The geometry type PUNKT is a single point (standalone) that can be either "3-dimensional" (NØH) or "2-dimensional" (NØ).

The geometry type KURVE consists of several points in a sequence where each point has a specific position. Knot points on lines (...KP 1) are also common. Where 2 or more geometry types meet, there should be a node point. The elements are connected at the node point and have common coordinates.

The geometry type BUEP defines a three-point arc.

If we export the data in the layer for Lines_and_point_and_annotation, an extract of the file could look like this:

.KURVE 1:  
..OBJTYPE RpJuridiskLinje  
..RPJURLINJE 1221  
..VERTNIV 2  
..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 200901  
..NØ  
80986557 59529564 ...KP 1  
..NØ  
81021479 59482139

.BUEP 2:  
..OBJTYPE RpJuridiskLinje  
..RPJURLINJE 1221  
..VERTNIV 2  
..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 200901  
..NØ  
80981534 59554322 ...KP 1  
..NØ  
80981313 59541389  
80986557 59529564 ...KP 1

.KURVE 3:  
..OBJTYPE RpJuridiskLinje  
..RPJURLINJE 1211  
..VERTNIV 2  
..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 200901  
..NØ  
81027116 59486289  
80992193 59533715 ...KP 1

.SYMBOL 4:  
..OBJTYPE RpJuridiskPunkt  
..RPJURPUNKT 1242  
..VERTNIV 2  
..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 200901  
..NØH  
80988395 59596338 0  
80988395 59596338 0  
80987442 59596641 0

.SYMBOL 5:  
..OBJTYPE RpJuridiskPunkt  
..RPJURPUNKT 1273  
..VERTNIV 2  
..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 200901  
..NØH  
80986173 59559895 0  
80986173 59559895 0  
80985185 59560048 0

.TEKST 6:  
..OBJTYPE RpPåskrift  
..VERTNIV 2  
..RPPÅSKRIFTTYPE 7  
..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 200901  
..STRENG "R=7.0"  
..NØ  
80996891 59590554  
80996891 59590554  
80993082 59599800

PUNKT, KURVE and BUEP correspond to the object types Point and Line in Gemini Terrain. A line object in Gemini Terrain can consist of the elements line and arc.

The cartographic element TEKST corresponds to the object type Text in Gemini Terrain.

Geometry Type: FLATE

FLATE is a continuous area bounded by, among other things, KURVE and BUEP. The definition is done by referring to the data groups that delimit the surface. The groups are referenced in a descriptive order. There should be knot points and equal coordinates between the geometry types that are included.

If we export the data in the layer for land use purposes, an extract of the file could look like this:

.KURVE 1  
.. OBJTYPE RpFormålGrense  
..NØ  
59489 194634  
61661 185617

.KURVE 2  
 (followed by attributes, coordinates etc.)

.KURVE 3  
(followed by attributes, coordinates etc.)

.KURVE 4  
(followed by attributes, coordinates etc.)

.FLATE 1  
.. OBJTYPE RpArealformålOmråde  
..RPAREALFORMÅL 1110  
..REF :1 :2 :3 :4  -> references to lines

Polygon in Gemini Terrain corresponds to surface in SOSI. Creation of SURFACES according to SOSI syntax is done by the program when we export to SOSI. The program then creates representation points and inserts all properties associated with each surface. The export requires that the lines are in topological form and that there is a connection between lines and polygons in Gemini Terrain.

KVALITET

SOSI has a separate property to describe quality of positioning.

In connection with plans, it is MEASUREMENT METHOD and ACCURACY that can be interesting. If we have entered values for these in Gemini Terrain, the program will create the property KVALITET during export:

..KVALITET

UTNYTT

SOSI plan has a property to describe the degree of utilization.

This consists of UTNTYP, UTNTALL and UTNTALL_MIN. If we have entered values for these in Gemini Terrain, the program will create the property UTNYTT during export:

..UTNYTT

NASJONALAREALPLANID

SOSI has a separate property to provide a nationwide, unique and unambiguous identifier (identification) for a land use plan.

This consists of KOMM, FYLKESNR, LANDSKODE and PLANID. Only one of the first three properties should be included. If we have entered values for these in Gemini Terrain, the program will create the property NASJONALAREALPLANID during export.

Example:

..NASJONALAREALPLANID  
...KOMM 1201  
...PLANID 01-2012

HØYDEFRAPLANBEST

SOSI has a separate property to specify provisions about elevation values given in plan provisions.

This consists in SOSI version 4.5 of REGULERTHØYDE (number for contour elevation when determining regulated elevation) and HØYDE-REF (elevation reference system, specified with separate codes). If we have entered values for these in Gemini Terrain, the program will create the property HØYDEFRAPLANBEST during export.

Example:

..HØYDEFRAPLANBEST  
...REGULERTHØYDE 20  
...HØYDE-REF NN2000

Note that this is different from SOSI version 4.3 where you only have ..REGULERTHØYDE.