Help Content > General Information > Catalogue of Processing Messages

Purpose

This section is intended to provide preliminary information, which are useful to better understand data processing related messages such as warnings and errors.

Error List

Connection failure (E.C. 260001) - The downloading process got stuck due to an internet connection failure. It can happen for instance when the Tools>Digital Elevation Model Extraction functionality is executed and the SRTM-3 or GTOPO30 tiles are being downloaded. In case one of the Digital Elevation Model tiles is not found in the internet, or the internet connection fails before or during the data downloading, the names of the required DEM tiles are written in the Process.log file in order to enable to user to retrieve the files manually and store them in the appropriate folder (default work directory).

Connection login failure (E.C. 260002) - The downloading process got stuck due to an internet connection failure. It can happen for instance when the Tools>Digital Elevation Model Extraction functionality is executed and the SRTM-3 or GTOPO30 tiles are being downloaded. In case one of the Digital Elevation Model tiles is not found in the internet, or the internet connection fails before or during the data downloading, the names of the required DEM tiles are written in the Process.log file in order to enable to user to retrieve the files manually and store them in the appropriate folder (default work directory).

Connection timeout elapsed (E.C. 260003) - The downloading process got stuck due to an internet connection failure. It can happen for instance when the Tools>Digital Elevation Model Extraction functionality is executed and the SRTM-3 or GTOPO30 tiles are being downloaded. In case one of the Digital Elevation Model tiles is not found in the internet, or the internet connection fails before or during the data downloading, the names of the required DEM tiles are written in the Process.log file in order to enable to user to retrieve the files manually and store them in the appropriate folder (default work directory).

Coregistration central window anomaly (E.C. 100011) - An anomaly has been reported in the definition of the coregistration central window. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Coherence threshold must be lowered (E.C. 240001) - The "Product Coherence Threshold" has been set too high and none Persistent Scatterer has been found. The threshold must be lowered according to the value of the scene specific multi-temporal coherence (_cc output product) and the processing iterated after having selected only the "Generated Geocoded Products" flag.

Coregistration window grid anomaly (E.C. 100012) - An anomaly has been reported in the definition of the coregistration central window. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Computation error (E.C. 80000) - A math error has been reported. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Coregistration error (E.C. 100006) - The cross-correlation process fails with the current coregistration parameters setting; consequently the coregistration step is not performed. In this case the number of windows (and if necessary also their size), in range and azimuth direction, should be increased. A manual location of the coregistration window can also be done.

Coregistration initialization failure (E.C. 100010) - The coregistration process initialization fails due to an unexpected anomaly. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Data Formatting anomaly (E.C. 130004) - Anomalies, such as missing sections and parameters or not initialized arrays, have been found in the data. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Data Formatting anomaly (E.C. 130005) - Anomalies, such as missing sections and parameters or not initialized arrays, have been found in the data. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Data Formatting anomaly (E.C. 130006) - Anomalies, such as missing sections and parameters or not initialized arrays, have been found in the data. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

File Path too long (E.C. 40007) - This error occurs, only using a WINDOWS operating system, when a file path is longer than 260 characters. It often happens when TerraSAR-X and Tandem-X data, acquired in bistatic mode, are being imported.

Data Formatting anomaly (E.C. 130007) - Anomalies, such as missing sections and parameters or not initialized arrays, have been found in the data. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Data incompatibility (E.C. 100000) - Generic error message related to differences identified in the input data, which should have had same pixel size and/or same number of pixels and or same geographic location/projection.

Different cartographic system (E.C. 100004) - The cartographic reference system must be the same for all input data. This is a mandatory requirement for some processing steps, such as the Conventional Mosaic.

Different number of columns (E.C. 100002) - The number of columns is not the same for all input data. This is a mandatory requirement for some processing steps, such as the Phase to Height Conversion and Geocoding, where all inputs must have the same number of pixels.

Different number of rows (E.C. 100003) - The number of rows is not the same for all input data. This is a mandatory requirement for some processing steps, such as the Phase to Height Conversion and Geocoding, where all inputs must have the same number of pixels.

Expired license (E.C. 110002) - Your SARscape license has expired. Contact your local SARscape distributor to know how to renew it.

Fatal Error (E.C. 140000) - Hardware as well as software or data related problems can cause this kind of error. The problem must be investigated by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Fatal Error (E.C. 140001) - Hardware as well as software or data related problems can cause this kind of error. The problem must be investigated by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

File error (E.C. 40000) - It can be related to different kind of software or data problems. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

File inconsistency (E.C. 40001) - It can be related to different kind of software or data problems. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

File not found (E.C. 40002) - The required input file is missing. This can happen for instance when the processing is executed in batch mode and the file name, extension or repository folder is wrongly entered.

File create error (E.C. 40003) - It is not possible to create the file in the output folder. This can happen when the user has not the required privileges to write in the specified folder or the output folder has been wrongly located in the CD or DVD. Change the output directory or modify the user privileges and try again.

File write error (E.C. 40004) - It is not possible to write the file in the output folder. It can happen when the disk is full or the connection to the output drive get lost (this last is typically reported when writing on external drives).

Fine coregistration failure (E.C. 100013) - The final part of the coregistration process (fine shift estimate) fails due to an unexpected anomaly. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Generic error (E.C. 20000) - It can be related to different kind of software or data problems. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Geocoding inconsistency (E.C. 160001) - An inconsistency has been found while executing the Geocoding process. It can happen for instance when the "GCP File" is outside the input file/s coverage.

Header file anomaly (E.C. 130001) - Mandatory fields are missing in the .sml file. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Header file inconsistency (E.C. 130000) - A generic problem has been detected in the .sml file. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Inconsistent option selection (E.C. 70008) - It is related to the attempt of performing an operation, which has already been done and it cannot be executed twice. It typically happens when the user is either adding the geoid to a geoidal DEM or subtracting the geoid from an ellipsoidal DEM.

Inconsistent pixel spacing (E.C. 100001) - The pixel dimension is not the same for all input data. This is a mandatory requirement for some processing steps such as the Conventional Mosaic.

Input files are not enough (E.C. 70006) - The number of input data is not sufficient to execute the processing. It can happen for instance when the Persistent Scatterers functionality is executed with just a few acquisitions.

Installation error (E.C. 120000) - Uninstall SARscape from your PC and install the latest software version. Contact your local SARscape distributor in case the problem persists.

Invalid dongle (E.C. 110003) - A problem has been detected in your license hardware key (USB dongle). The following procedure can be attempted to solve it:

1.Remove the SARscape dongle, which is currently plugged in the PC, and restart it.

2.Run the "Install.exe" file, which is stored in the original SARscape installation package (SARscape x.x.xxx\install_sar_scape_directory\config_file folder).

3.Select both the flags "USB Dongle" and "Standalone" ("Install.exe" panel) and then click the "Begin Install" button.

4.Plug the SARscape dongle in the PC and follow the USB installation procedure.

Contact your local SARscape distributor in case the problem persists.

Invalid License (E.C. 110000) - A license related problem has been detected. Contact your local SARscape distributor.

Memory not found (E.C. 30000) - It can be related to different kind of software or data problems. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed.

Missing data record (E.C. 130003) - Some data records are missing in the .sml file. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Missing information (E.C. 130002) - Some parts of the header ( .sml file) are missing or corrupted. This error must be checked by the sarmap team for a solution; for this purpose the relevant error report must be saved and e-mailed together with the .sml input file/s header.

Missing license for this module (E.C. 110001) - Your SARscape license does not allow operating this module. Contact your local SARscape distributor for more information.

Missing mandatory step (E.C. 70007) - The specific processing requires a previous mandatory step to be executed first. It can happen for instance when the Phase to Height Conversion and Geocoding functionality is executed without having previously performed the Refinement and Re-flattening or even during the execution of the SBAS processing chain where a step can be compulsory for the execution of the next one.

Missing reference file (E.C. 240004) - The "Reference file" acquisition is not among the data in the "Input File List" when the Persistent Scatterer processing is executed.

Only null values (E.C. 40006) - All image pixels are NaN (null values or dummy pixels).

Process cancelled (E.C. 50000) - The user has deliberately interrupted the process (for instance by clicking the "cancel" button in the running bar) or the process stopped automatically due to a conflict with another processing initiated in parallel using the same working directory.

Processing information are missing (E.C. 70009) - Some mandatory flag has not been set in the processing panel. It can happen for instance when none processing option has been set in the Dual Pair Differential Interferometry step; in such instance or more of the following three flags must necessarily be checked: i) From SLC to Phase Unwrapping; ii) Generate Slant Range Products; iii) Generate Geocoded Products.

Refinement/Re-flattening error (E.C. 170001) - An inconsistency has been found while executing the Refinement and Re-flattening process in any of the modules where it is foreseen (i.e. Interferometry, ScanSAR Interferometry). It happens when the number of GCPs, which are used to remove erroneous phase components (ramps or constant terms), is not sufficient to execute the process (refer to the Preferences_specific>Flattening for details).

Statistic calculation failure (E.C. 150000) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150001) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150002) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150003) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150004) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150005) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150006) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150007) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150008) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Statistic calculation failure (E.C. 150009) - An inconsistency has been found while executing the Data Statistic functionality. It can happen for instance when the "Vector File" (or the area of interest co-ordinates) are located outside the input file/s coverage.

Warning message (E.C. 10000) - It is not an error message and it does not cause a processing interruption. The message informs the user of an anomaly detected during the data processing. As an example this kind of message is provided when the ENVISAT ASAR data are imported and some mandatory ancillary file is missing.

Wrong input format (E.C. 90000) - The input file/s type or format is not correct. It can happen for instance when: i) a wrong sensor or data type is specified in the import functionality; ii) an input product is entered, which is not suitable for a specific processing (e.g. an amplitude/intensity SAR image to convert a DEM to Slope image.

Wrong input parameters (E.C. 70000) - One or more parameters in the processing panel has been wrongly entered or there is someone missing.

Wrong window size (E.C. 70001) - Not admitted values have been entered as window dimension. It can happen when the widow size, in any processing step where this parameter is foreseen, is set to values which cannot be used (for instance the filter window size cannot be set to 0 or decimal values).