Dear Javier,
It seems that the sensor geometry of L1A CSK products is not supported
at the moment. A sensor model is already implemented in the OSSIM
plugins but the implementation is incomplete. Other processing that
doesn't need geometric model should work fine.
I will check if previous work has been done on the subject and if it is
ready for integration.
Best Regards,
Guillaume
Le 18/08/2014 08:18, Javier Martin a écrit :
Dear Guillaume,
sorry for the late answer, but I was on vacation.
The result of the*otbcli_ReadImageInfo* fails in the geom generation,
but print the next keywordlist:
*otbcli_ReadImageInfo* -in
CSKS1_SCS_B_S2_02_HH_LD_SF_20090630185955_20090630190002.h5 -outkwl
csk_keywordlist.geom
2014 Aug 18 07:54:41 : Application.logger (INFO)
Image general informations:
Number of bands : 1
Start index : [0,0]
Size : [984,959]
Origin : [0,0]
Spacing : [1,1]
Estimated ground spacing (in meters): [43731.1,2564.87]
Image acquisition informations:
Sensor :
Image identification number:
Image default RGB composition:
[R, G, B] = [0,1,2]
Ground control points information:
Number of GCPs = 0
GCPs projection =
Output parameters value:
indexx: 0
indexy: 0
sizex: 984
sizey: 959
spacingx: 1
spacingy: 1
originx: 0
originy: 0
estimatedgroundspacingx: 43731.10547
estimatedgroundspacingy: 2564.873047
numberbands: 1
sensor:
id:
time:
ullat: 0
ullon: 0
urlat: 0
urlon: 0
lrlat: 0
lrlon: 0
lllat: 0
lllon: 0
town:
country:
rgb.r: 0
rgb.g: 1
rgb.b: 2
projectionref:
keyword:
gcp.count: 0
gcp.proj:
gcp.ids:
gcp.info <http://gcp.info>:
gcp.imcoord:
gcp.geocoord:
The *gedalindo* file output is attached in the email:
*gdalinfo*
HDF5:./CSKS1_SCS_B_S2_02_HH_LD_SF_20090630185955_20090630190002.h5://S01/SBI
> gdalInfo.txt
Thank you for your help and best regards,
Javier.
2014-08-04 17:59 GMT+02:00 Guillaume Pasero <[email protected]
<mailto:[email protected]>>:
Hello Javier,
The CSK images are known to cause errors in a few cases.
Sometimes, GDAL fails to interpret datasets with 3 dimensions
(multi-band datasets), and the number of detected bands is
mistaken with one of the 2D buffer dimensions. I think a patch has
already been submitted to GDAL.
In order to detail your problem, could you send the results of the
application *otbcli_ReadImageInfo* on your .h5 image (also print
the keywordlist).
You could also check what *gdalinfo *is reporting (might be a bit
verbose with all the metadata).
Regards,
Guillaume
Le 17/07/2014 08:30, Javier a écrit :
Dear,
I installed OTB 4in Linux, for which I installed GDAL 1.11. I am
working with L1 images both optical and SAR and I've found that
hdf5 (.h5) images of CSK produce an error when trying to access
its metadata. Using the Ortho-rectification program I obtain the
next error.
OTB-4.0.0/Code/Projections/otbImageToGenericRSOutputParameters.txx:50:
itk::ERROR: ImageToGenericRSOutputParameters(0x15af480): No
information in the metadata, please set an image with non empty
metadata
At the end of the program execution I obtain the next error:
$ otbgui_OrthoRectification
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5D.c line 377 in H5Dclose(): not a dataset
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5S.c line 365 in H5Sclose(): not a dataspace
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5G.c line 711 in H5Gclose(): not a group
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5F.c line 1957 in H5Fclose(): invalid file
identifier
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
[SAR\jmartin@workstationrh5 build]$ otbgui_Convert
Warning 1: Lost metadata writing to GeoTIFF ... too large to fit
in tag.
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5D.c line 377 in H5Dclose(): not a dataset
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5S.c line 365 in H5Sclose(): not a dataspace
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5G.c line 711 in H5Gclose(): not a group
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5F.c line 1957 in H5Fclose(): invalid file
identifier
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ../../src/H5T.c line 1721 in H5Tclose(): not a datatype
major: Invalid arguments to routine
minor: Inappropriate type
GDAL configuration is the next:
./configure --prefix=/usr/local --with-libtiff=internal
--with-geotiff=internal
--with-rename-internal-libtiff-symbols=yes
--with-rename-internal-libgeotiff-symbols=yes --with-hdf4 --with-hdf5
The report configuration:
...
LIBTIFF support: internal (BigTIFF=yes)
LIBGEOTIFF support: internal
...
HDF4 support: yes
HDF5 support: yes
...
I solved one error in the GDAL frmts/hdf5 hdf5dataset.cpp, the
MAX_METADATA_LEN definition is 32768, this caused the metadata
truncation. The problem was solved by Increasing this
MAX_METADATA_LEN to 1 MByte. Still the metadata reading problem
persists. Do you have any idea?
Best regards.
Javier.
--
--
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]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[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.
--
<http://www.c-s.fr> *Guillaume PASERO*
Ingénieur d'études et développement
*Business Unit E-SPACE & Geo Information*
<https://thor.si.c-s.fr/blogs/cs-blogs-business/>*- Département
APPLICATIONS*
*CS Systèmes d'Information*
Parc de la Grande Plaine - 5, Rue Brindejonc des Moulinais - BP 15872
31506 Toulouse Cedex 05 - FRANCE
+33 561 17 64 21 - [email protected]
<mailto:[email protected]>
--
--
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]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:otb-users%[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 a topic in
the Google Groups "otb-users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/otb-users/cn18GfZ2e30/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Javier Martín Abasolo
660428293
--
--
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.
--
<www.c-s.fr> *Guillaume PASERO*
Ingénieur d'études et développement
*Business Unit E-SPACE & Geo Information*
<https://thor.si.c-s.fr/blogs/cs-blogs-business/>*- Département
APPLICATIONS*
*CS Systèmes d'Information*
Parc de la Grande Plaine - 5, Rue Brindejonc des Moulinais - BP 15872
31506 Toulouse Cedex 05 - FRANCE
+33 561 17 64 21 - [email protected]
--
--
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.
