Changes between Version 4 and Version 5 of Processing/KnownProblems


Ignore:
Timestamp:
Oct 4, 2007 1:18:07 PM (11 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/KnownProblems

    v4 v5  
    1616This means the CASI data files are missing the GPS sync markers (or azcaschk2 can't find them).  As a consequence, scans can't be tied to navigation and azgcorr has nothing to work with.  Typically, you'll be able to get the file to level 1 without problems, but level 3 can't be done.
    1717
    18 To work around the lack of GPS sync, azcaschk2 allows you to use "frame headers" for sync instead.  You need to add `-FRsync` to the azcaschk2 command line.  In the normal batch files, amend the CSYNC line to read: `CSYNC="-FRsync"`.
    19 
    20 == Image Ok but vector layers did not lined up==
    21 If the image looked okay after modifiying the GPSOFF and then the vector layers did not line up, them it is better to modify the SCTOFF instead of GPSOFF. This will bring the vector layers to their places (e.g project 206 line 1 , 4 , 5 )
    22 
     18To work around the lack of GPS sync, azcaschk2 allows you to use "frame headers" for sync instead.  You need to add `-FRsync` to the azcaschk2 command line.
    2319
    2420This should then process through to level 3, though you may need to correct for navigation timing.
     21
     22---------------------
     23
     24== Image looks straight but vector layers are not not lined up ==
     25
     26If the image looked okay after modifiying the GPSOFF and then the vector layers did not line up, them it is better to modify the SCTOFF instead of GPSOFF. This will bring the vector layers to their places (e.g project 2006/206 line 1 , 4 , 5 )