X

Help Articles are product support tips and information straight from the NV5 Geospatial Technical Support team developed to help you use our products to their fullest potential.



9102 Rate this article:
5.0

FILE INCONSISTENCY error during a coregistration step in SARscape

Sometimes when performing coregistration or any type of interferogram generation (which includes a coregistration) in SARscape, one will receive an error message that says something like:

     SARscape error message

     FILE INCONSISTENCY [EC : 40001]

This can happen for a variety of reasons. Some datasets are just not coherent enough for SARscape to find enough points for a reasonable coregistration. For example, if everything in the scene has changed between datasets, coregistration can fail. This can happen if the area is heavily vegetated (because vegetation changes and moves a lot, and so can look very different from image to image at a particular location). We have also heard of coregistration failing for datasets from before and after a tornado that destroyed and changed everything in the scene. There really is not a solution for that problem. Sometimes if the problem is vegetation, and you are not mostly interested in the vegetated areas, then you can specify a relatively non-vegetated area to analyze. You would do this using the Sample Selections tools under SARscape > General Tools.

Some other problems that can occur:

For some datasets, the orbital data may not be precise enough for an accurate coregistration. SARscape may be able to update the orbital information, with precise orbit files that you get from the data provider. ERS and Radarsat-2 datasets are in this category. Once you have the precise orbit files, you can find the tools to apply them to the datasets under SARscape > General Tools > Orbital Correction > Update to Precise Orbits.

If the datasets have a lot of topography, it can be tricky to find good tie points between the datasets. In this case, you will want to be sure to specify a DEM during the coregistration. It will be necessary in this case to get good results. If you do not have a DEM, you can generate one that matches your master dataset in SARscape, using the tool under SARscape > General Tools > Digital Elevation Model Extraction > SRTM-3 Version 4 (you can extract a DEM for your area from any of the global DEM datasets listed under digital Elevation Model Extraction, but we recommend using an SRTM DEM).

Below are some parameters you might try changing, if you can't get coregistration after updating the orbital information or adding a DEM:

1. In the dialog where you set up the processing parameters, under the Parameters tab, choose Coregistration from the drop down menu near the top. Then try tripling the Range Window Number and Azimuth Window Number parameter values.

2. If that doesn't work, then leave those values at their new larger values and additionally try doubling the Range Window Size and the Azimuth Window Size.

 

Review by MMin, 2015-02-12

Please login or register to post comments.
Featured

End-of-Life Policy Enforcement for ENVI 5.3 / IDL 8.5 and Earlier Versions

5/6/2024

April 1, 2024 Dear ENVI/IDL Customer,  We are reaching out to notify you of our supported... more »

How to Upgrade licenses to ENVI 6.x / IDL 9.x

12/5/2023

What is the new Upgrade function? Starting with ENVI 6.0 and IDL 9.0, we have implemented an... more »

What to do if the 'License Administrator - License Server' for the Next-Generation License Server does not start?

6/13/2023

Background: With the release of ENVI 5.7 & IDL 8.9 and the corresponding Next-Generation licensing... more »

Next-Generation Licensing FAQ

4/28/2023

  NV5 Geospatial has adopted a new licensing technology for all future releases of our ENVI, IDL... more »

The IDL Virtual Machine

6/6/2013

What is the IDL Virtual Machine? An IDL Virtual Machine is a runtime version of IDL that can... more »