Only in ERR/WARN/INFO/DBUG/OGS_FATAL and similar, not in
formatted output like xml files.

Otherwise there is a memory leak.

New versions of logog do not have an implicit ; after the macros.

1. Changed urls to https which fixed the following error:

xsd/OpenGeoSysGLI.xsd, at line 1, column 66: Document is not a XML schema.
Error XSDError in ..., at line 3, column 194: Loaded schema file is invalid.

If this error ever pops up again try to cut the internet connection! No joke!

2. Local schema files are now copied to bin-directory during CMake configuration and package generatiion (install step).

Sometimes the computed grid coordinates are to large which leads to memory errors.

Clang format run on near-the-header lines.

Happy New Year

* reimplemented raster to mesh conversion

* fixed index issues and added 3d index calculation

* added necessary changes to gui dialogue

* added tests

* clang format

* added ifdef for data explorer/vtk includes

* modified dereferencing of unique pointers, formatting

* changed pointer to vector in vtk prep

* using const& for nodes vec

* fixed remaining occurences of dereferencing raster object

Using tellg for size is not a portable idea.
The solution is from https://stackoverflow.com/a/116220.

To create correctely oriented mesh elements
(OGS-6 viewpoint) using gmsh the input polygon
is required to have ccw order.

This crashed the convertGEO utility. Thanks to JM for reporting!
This bug was introduced with a6ff2c7a.

See clang-tidy docu https://clang.llvm.org/extra/clang-tidy/checks/readability-simplify-boolean-expr.html

From llvm documentation https://clang.llvm.org/extra/clang-tidy/checks/misc-string-compare.html
"A common mistake is to use the string’s compare method instead of using the equality or inequality operators. The compare method is intended for sorting functions and thus returns a negative number, a positive number or zero depending on the lexicographical relationship between the strings compared. If an equality or inequality check can suffice, that is recommended. This is recommended to avoid the risk of incorrect interpretation of the return value and to simplify the code. The string equality and inequality operators can also be faster than the compare method due to early termination."