Dear Ivana,

My name is Elena Prado and I am a user to azgcorr. I have some questions for you,

I try to geocorrect CASI images to achieve L3 product. The images were
acquired over Guadalajara (Spain).

Datum transformation

I am using azgcorr with the option of 7 parameters for datum transformation;
the parameters are specially adapted to the flight zone. But when I check the
results, the images have an offsets in coordinates (offset in Xutm = 104
offset in Yutm = 132).

I know that the images are synchronized with the navigation data because the
effects of the aircraft movement have been removed correctly. 

The offset in Xutm fit with the difference between WGS84 and European Datum
1950 so I am not sure that the azcorr makes the transformation.

I send you the azgcorr command line:

> azgcorr  -p 3.5 3.5 –bl 45 15 5 -1 –d7 0 131.032 100.251 163.354 -1.2438 -0.0195 -1.1436 -9.39 –mUTM -3 –eh /MDT25_IGN_GUADA_ED50_3m_he.txt –es NO –ua 0 0 -0.465 –ut -59.995 -1 /c154011b.hdf -3 /c154013_ed50.hdf

-p 3.5 3.5 : pixel size 3.5 meters
-bl 45 15 5 -1 CASI bands to georeference 45/15/05
–d7 0 131.032 100.251 163.354 -1.2438 -0.0195 -1.1436 -9.39: seven parameters for datum transformation
-mUTM -3 : UTM projection zone 30. (central meridian longitude -3)
-eh : DEM file in UTM H30 ED50 and ellipsoidal height
-es NO : no geoid undulation
-ua 0 0 0.465 : offset in heading to apply the meridian convergence
-ut -59.995: offset  to correct the synchronization between image and navigation data

Can you help me with the Datum transformation?

ENVI header

I use the azexhdf to get a Envi header.

> azexhdf –h /c154013_ed50.hdf –Be /c154013_ed50.bil

I get a BIL format image with this command line and in other
folder (I don’t know why azexhdf doesn’t write in the same folder)
get another file P9.hdr with the Envi header. But the map info in
the header is not correct. The datum of the L3 image doesn’t appear
in the header file and the coordinate of the header is the SW image
corner coordinate instead of NW image coordinate that ENVI needs.

Map info = {UTM, 1, 1, 562233.00, 4518052.00, 3.50, 3.50, 30, North}

Do you know how I can solve this?

Image line start – line end

I detect that the data have a des-synchronization between the image
and navigation data, this time offset is 59 seconds more or less 
This time is equivalent to 909 lines from the first line in the image
L1b. I think that with this scan timing offset (-ut -59.995) the
synchronization is ok, so I don’t know how use the information about
the scan line (start / end) number information.

Can I do without these??

Data extracted from c154011b.hdf
MIsscan: 248
MIsescan: 6009
NVscnum 248 -> 6009
CAsscan: 248
CAescan: 6010
COsscan: 248
COescan: 4205
COscans: 3958
 
Thanks you very much,

Elena Prado Ortega
<Contact details removed, see internal contact details page>
MailScanner has detected a possible fraud attempt from "correo.uah.es" claiming to be http://www.geogra.uah.es/teledeteccion-ambiental
___________________________________________________________________ Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o CONFIDENCIAL. Si vd. no es la persona a quien se dirige este mensaje, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. This message is intended exclusively for its addressee and may contain information that is CONFIDENTIAL and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please immediately notify us via e-mail and delete it. 

Casi line 3 have alot of chequers and nav problems as in below image

ATM processing : After processing ATM, every thing seems to be okay, however, there are some funny color ( red, yallow) appear on the top of the image. (Peter said that we can deliver them as they are). The data can be delivered because these lines appeared on the top of clouds.

CASI processing : Line one seems to be okay, however line 2 and 3 are bugged. error messages are shown below For line 2 azcas2 using calibration file: /users/rsg/arsf/calibration/casi/in34a4.rad for aperture: 4 casi IMAGE bands: 14 pixels: 512 lines: 62 no SRC processed or not present casi ILS bands: 14 pixels: 1 lines: 62 Using RSC calibration file: /users/rsg/arsf/calibration/casi/in34a4.rad NB: aperture from file search: 4

Creating dark data array... Dark frames used: 100 seq_ids: 52 to: 151 skipping 90 start frames on file: 0 Data processed using CASI read routine: frame_cal_dark

line: 0 seq_id: 242 first image line (0) was seq id: 242 last image line (61) was seq id: 303 Updated hdf file is: ./lev1/c271021b.hdf ./runc/c27102.sh: line 176: 4206 Segmentation fault aznav ${V} ${ATT} ${POS} -f 7 7 1 -so ${SCTOFF} -at ${GPTOFF} 0.0 -ao 0 0 0 ${ACVE} -h ${P_HDF1}

For line 3 azcas2 using calibration file: /users/rsg/arsf/calibration/casi/in34a4.rad for aperture: 4 casi IMAGE bands: 14 pixels: 512 lines: 3951 no SRC processed or not present casi ILS bands: 14 pixels: 1 lines: 3951 Using RSC calibration file: /users/rsg/arsf/calibration/casi/in34a4.rad NB: aperture from file search: 4

Creating dark data array... Dark frames used: 100 seq_ids: 52 to: 151 skipping 90 start frames on file: 0 Data processed using CASI read routine: frame_cal_dark

line: 0 seq_id: 242 line: 1000 seq_id: 1242 line: 2000 seq_id: 2242 line: 3000 seq_id: 3242 first image line (0) was seq id: 242 last image line (3950) was seq id: 4192 Updated hdf file is: ./lev1/c271031b.hdf