Skip to content

FAQ

This section contains Frequently Asked Questions and information about issues when working with the GIS manager.

Why I cannot create GDAL transformation object for output dataset creation?

When PostgreSQL/PostGIS is trying to use GDAL projection transformations, it looks at the following environment variables created (and updated) when installing PostgreSQL database services with the and PostGIS extension.

  • PROJ_LIB
    E.g. C:\Program Files\PostgreSQL\16\share\contrib\postgis-3.4\proj
  • PROJSO
    E.g. C:\Program Files\PostgreSQL\16\bin\libproj_8_2.dll
  • GDAL_DATA
    E.g. C:\Program Files\PostgreSQL\16\gdal-data

The environment variables are updated when running a new combination of the PostgreSQL database services with PostGIS installation.

When installing more PostgreSQL database services with the PostGIS extension, the environment variables could get out of sync with the database actually being used.

Make sure that the environment variables reflects the database service version with PostGIS used for the MIKE OPERATIONS database.

How are coordinate systems managed by MIKE OPERATIONS?

MIKE OPERATIONS relies on EPSG coordinate systems. The list of supported coordinate systems can be found in the PostGIS table public.spatial_ref_sys.

If a user tries to import or visualise (with a Provider) a dataset that is in a projection system not listed, MIKE Workbench will throw an error. MIKE Software supports additional coordinate systems, which can create problems when trying register a model or import a dfs2/dfsu file.

To improve this, the Import from Dfs2 file and Import from Dfsu file tools (also used in several MIKE adaptors) read the coordinate system from the file and display it in the Coordinate System property. During the import, if it is not supported, they will try to find and use a similar EPSG one. So the coordinate system used in MIKE Workbench can be slightly different than the one from the original file. This works well for visualisation purpuses. However, when preparing input dfs files for models, the dfs2/dfsu generated by the adaptor will not match anymore the orginal model projection.

MIKE OPERATIONS 2025.2

This limitation was addressed with MIKE OPERATIONS 2025.2.
Those two tools have a new property called Convert to EPSG. If set to FALSE, the MIKE coordinate system will be added to the database. This is the case when used in the different MIKE adaptors to ensure a correct behaviour of the model. When using tools in the user interface, by default, this is set to TRUE to be backward compatible and to ensure that the data can be used properly by Third party libraries embedded in MIKE OPERATIONS (e.g. ThinkGeo).