Skip to main content
Skip table of contents

Geoid Model Parameters Dialog

As the geoid model file alone contains insufficient geodetic information, it must be accompanied by a WKT file. By completing the fields in the dialog, it is possible to generate the necessary WKT file for use with the Geodetic User Interface. For detailed information regarding the fields, please refer to the table below the image.

Upon completing the configuration of the fields, click the ‘Create Model’ button to copy or convert the geoid model and save the WKT file to the default shared location.
(On Windows: Public Documents\QPS\Shared\Geo\Geoid)

250804-173310-2641-QPS.png

Item

Info

File Path

This is the path where the geoid model file is located

File Format

Shows you the file format

Horizontal Unit

For the Latitude and Longitude

Vertical Unit

For the separation values

Model Type

This shows you if a model is Absolute or Relative:

  • Absolute - separation values are referenced to a Datum
    (for example, ETRS '89 or NAD '83 (2011));

  • Relative - separation values are referenced to another offset model (which is Absolute and on the same Horizontal Datum).

Horizontal Datum

Select the datum on which the separation model was created.
In this case, the Latitude and Longitude were defined on ETRS '89.

Source Vertical Datum

Relevant when dealing with a relative model
This is the vertical datum to which the separation value is linked.

Target Vertical Datum

Select the target vertical datum. This can be a model for which an EPSG code is defined. Optional to create a custom vertical datum.
In this case, heights are related to DHHN 2016

Name

The name of the model that will be shown in the Geodetic User Interface

Interpolation Method

  • Spline - spline interpolation using 16 points
    (4 by 4 window around the current position)

  • Bilinear -  linear interpolation using 4 points around the current position

Transform Accuracy

A fixed accuracy can be defined

Mask

Dependent on the file format, fixed value or definable

Unique ID

Unique Model ID may not overlap with existing custom geoid models

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.