Dear Ted,
Here are several things that might help you :
- Spot5 and WV2 spatial resolution and radiometric differences are huge
(not to mention the possible time gap and season change). You should at
least zoom out the WV2 to a SPOT5 equivalent resolution. SIFT and SURF
are tolerant to resolution change, but only up to a certain point.
Radiometric processing to make the image look similar (like working on
the same radiometric channel for instance),
- the HomologousPoints / RefineSensorModel workflow is not meant to be
used with both images already orthorectified. You can have the reference
image ortho, but at least the moving one should be sensor. If you can
not have this configuration, you can still search for homolgous point
and estimate a rigid transform from the points on you own,
- I think there is a confusion in the metadata of the WV2 image. Since
it is already ortho, you should not have a geom file anymore. Can you
try to remove it ?
Regards,
Julien
Le 18/03/2014 19:38, Ted a écrit :
Dears,
I did a complete preprocessing workflow for a WV2 scene as described
in the CookBook. However, the last step, the residual registration,
makes some problems. I need to co-register the WV2 scene on a Spot 5
scene. The homologous point extraction already delivers no homologous
points. According to the console output it finds plenty of surf point
for the second image, which is the Spot 5 scene, but most times not a
single for the first image, the WV2 scene.Since the WV2 scene has been
processed with other OTB applications before (incl.
OrthoRectification) there exists a .geom file. for the Spot scene no
geom file exists and the otbcli_ReadImageInfo does not write an output
file (only console output). I therefore redirected the console output
into a textfile (see attached metadata.geom). For completeness I've
also attached the WV2 .geom file (12JAN01-P2AS_P001_toc_ortho.geom).
Of course both images are of different resolutions which might by a
difficulty for automatic tie point extraction. However, I am not sure
if there is another error since at least a few point should be
possible to extract.
As substitute for automatic tie point extraction I would also be
interested in manual tie point extraction. For this I would need to
know the precise format how and which coordinates have to be written
in the text file. Is there any experience with using manual tie points
with the next tool in the workflow: otbcli_RefineSensorModel? I read
about a possibility to manually extract tie points in Monteverdi but
can not find any such tool there.
Last question: When I do the residual registration as the last step in
the pre-processing workflow, does it matter if I already did the
orthorectification of the input image which should be adapted?
Thanks a lot!
Ted
--
--
Check the OTB FAQ at
http://www.orfeo-toolbox.org/FAQ.html
You received this message because you are subscribed to the Google
Groups "otb-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/otb-users?hl=en
---
You received this message because you are subscribed to the Google
Groups "otb-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Julien MICHEL
CNES - DCT/SI/AP - BPI 1219
18, avenue Edouard Belin
31401 Toulouse Cedex 09 - France
Tel: +33 561 282 894 - Fax: +33 561 283 109
--
--
Check the OTB FAQ at
http://www.orfeo-toolbox.org/FAQ.html
You received this message because you are subscribed to the Google
Groups "otb-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/otb-users?hl=en
---
You received this message because you are subscribed to the Google Groups "otb-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
