GEODI works with SSL structure and can be accessed as HTTPS. In this way, data communication is managed securely.

The port 1982 is the default port required for the GEODI server to access the Client. A different port can be used upon request. In addition, the Client must also be able to access GEODI through the specified port(s).

Possible impact. Since GEODI works with big data, some rules in security tools during communications may slow down operations or completely prevent communication. In such cases, the relevant GEODI tools should be excluded in these rules with the support of the DECE technical team.

This is normal behavior. Power outages, system hardware problems, deliberate application shutdowns, and many other issues can cause unintentional shutdowns. In this case, the index will undergo a health check at the next startup for possible damage and any errors found will be fixed.

To speed up the process, you need to back up the index and recover from backup on startup. Recovering from backup does not cause irreversible data loss. The next time you index what has changed, the latest additions are refreshed.

Active-Passive and Active-Active configuration

Index Backup and Recovery

GEODI is designed to make optimum use of the server. Server memory and CPU resources are used dynamically. The number of concurrent tasks is increased for simple and fast processing files and decreased for heavy files.

If the processing is too slow

• Memory may be low or being used by other processes running on the server

• There may be processes that consume high CPU resources, such as intensive OCR.

• Network connections to the filerserver may be very slow

• There is content such as a large number of logs, csv, large excel files.

• There may be network problems with database connectivity or database congestion

• The GEODI indexing speed mentioned in the Project Wizard may be the lowest.

You may need to stop GEODI for maintenance on the server computer, relocation, updating GEODI or for any other reason. You can do this with the interface or scripts. During intensive data processing, stopping can take time. Stopping from the task manager will cause the index to go into repair or recovery from backup at startup.

Periodic backup of the index and creation of an active/passive DRM environment is described on page Active-Passive and Active-Active configuration By only backing up, it speeds up the system startup and activation in case of possible interruptions.

In the Advanced settings on the last page of the GEODI Project Wizard, the project index backup directory can be given against possible system outages. GEODI index can be used through this directory in case of possible interruptions. You can use the Index Backup and Recovery page for backup.

Indexing is done as "Read-Only" according to the authorizations of the user given during database connection.

GEODI indexes only the name of password protected files. Protected files indexed in this way can be listed with the queries "status:GEODICryptedContent" or "status:GEODICryptedContentPart".

Files with errors can be queried with “status:HasScanError”

Due to nested folders, there may be problems accessing files whose full path is too long. The source of this problem is the Windows operating system, you may also get similar errors when copying. You can solve it by shortening file paths by defining a network drive.

This issue is related to a security update to Windows. You can overcome this problem by performing the steps on the following page.

https://social.msdn.microsoft.com/Forums/vstudio/en-US/f8026f8f-3fba-4925-9344-87e16f085957/c-windows-10-systemiodirectoryexists-returns-false-for-a-mapped-drive?forum=csharpgeneral

A solution in case "strange" characters appear in short summaries when viewing records:

• Create a CPG or CST file with the same name as the shape file and write the encoding name like ( UTF-8 , ISO-... ... https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx  )

• If writing encoding is not a solution, after backing up the DBF file in the same directory as the SHP file, open it with OpenOffice or other software and select the encoding. The file is saved with the same name and extension.

  • ! The dbf file must be backed up. After this process, errors may be received when SHP is viewed with different programs.

This behaviour is by design. In order to remove deleted files from the GEODI index, you need to delete deleted files from the Project Management interface.

Windows can access directories up to 260 characters long.After this value, “System.io Path too Long Exception“ error is received. As a solution, you can edit the path appropriately (mapping).

• If the shape file projections are missing or incorrect, you may experience problems in reading, viewing and using the file as a dictionary.

  • In case of a projection problem you need to edit or recreate the PRJ file.

    • The projection problem will be displayed directly during operations such as dictionary preparation, during scanning it will be recorded in the scan log file.

    • Example "Missing projection parameter 'latitude_of_origin' It is also not defined as 'latitude_of_center'. Parameter name: parameterNam" is an example of GEODI not recognizing the projection in question. 

    • For editing it is necessary to create a Projection WKT using another software that recognizes the projection of the file and modify the PRJ content.

    • You can make use of

      • ArcGIS

      • Netcad

      • https://www.epsg-registry.org/

      • and other resources.

• If you want us to help, you can also send us the Shape file or PRJ file you are having trouble with.

Defining the projection for DWG and DGN files containing plans or maps will increase the usefulness of GeoArchive and CAD&GIS viewer modules.

Supported Formats

GEODI keeps its logs under appdata/dece/geodi. These logs are in CEF format and can be processed by SIEM tools.

%AppData%\Dece\Logs\GEODI\AppUsage directory contains the logs required for SIEM.

In case you mention another friend in the notes, tracking query is forwarded to the email. There may be a problem with the settings made on the server for this purpose. You can access through GEODI Management Panel / settings.

If the problem occurs in a number of users, Spam folders or mail rules should be checked.

GEODI checks for an update on startup and if you confirm, an update can take place. The index structure may be converted to the new version according to the features introduced in the new version. This is indicated by a warning. It is recommended to back up the old index before proceeding. GEODI must be turned off during the update.