From 2f2b7779a27f9a9ad9639443546f5f5f417ccaeb Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Thu, 28 Oct 2021 22:43:10 +0200 Subject: [PATCH 01/13] DOC: Add new cookbook page about supported formats --- .../Cookbook/rst/Supported_Sensors.rst | 76 +++++++++++++++++++ Documentation/Cookbook/rst/index.rst | 1 + 2 files changed, 77 insertions(+) create mode 100644 Documentation/Cookbook/rst/Supported_Sensors.rst diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst new file mode 100644 index 0000000000..0af48ea5eb --- /dev/null +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -0,0 +1,76 @@ +Supported file formats +====================== + +OTB relies on `GDAL `_ for reading and writing data +(either raster or vector images). This means that all formats +supported by GDAL are theoretically also supported by OTB. That being +said, there are some limitations. + +Raster images +~~~~~~~~~~~~~ + +GDAL provides a very large panel of drivers to access metadata in +image files. OTB stores the metadata in a special dictionary called +otbImageMetadata. There is a metadata framework that uses interfaces +(ImageMetadataInterface) to link data read by GDAL to the +otbImageMetadata. Thus, to access metadata for a specific sensor, the +corresponding interface is required. As this time, available +interfaces are: + ++------------------------+-------------------------+-------------------+ +| Sensor | Format | Notes | ++========================+=========================+===================+ +| CosmoSkyMed | HDF5 / TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| Formosat | DIMAP / TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| Ikonos | TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| Pleiades | JPEG2000 / TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| QuickBird | TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| Radarsat 2 | TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| Sentinel 1 | TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| Spot 5 | DIMAP / TIFF | RPC not available | ++------------------------+-------------------------+-------------------+ +| Spot 6 | DIMAP / JPEG2000 / TIFF | N/A | ++------------------------+-------------------------+-------------------+ +| TerraSarX | COS | N/A | ++------------------------+-------------------------+-------------------+ +| WorldView 2 | TIFF | N/A | ++------------------------+-------------------------+-------------------+ + +Sensors not in this list can still be used with OTB, but the metadata +won't be accessible. + +Full products generally contain multiple files (image files, manifest, +metadata files, etc). For SAR products, OTB takes necessarily an image +file. For optical sensor, OTB can also take the manifest file as +input. In that case, OTB will consider all the bands of the product. + +Vector images +~~~~~~~~~~~~~ + +OTB implements two ways of dealing with vector data. The first one +uses OGR::Datasource. The second one uses otb::VectorData. Depending +on which class is used by the application, different formats are +available. This is confusing, and we plan on fixing this. For now, +formats fully supported (IE. supported by all applications) are: + +- ESRI Shapefile (.shp) + +- MapInfo File (.tab) + +- Geographical Markup Language (.gml) + +- GPS Exchange Format (.gpx) + +- SQLite (.sqlite) + +- Keyhole Markup Language (.kml) + +- GeoPackage (.gpkg) + diff --git a/Documentation/Cookbook/rst/index.rst b/Documentation/Cookbook/rst/index.rst index 648334ad54..896ffa290c 100644 --- a/Documentation/Cookbook/rst/index.rst +++ b/Documentation/Cookbook/rst/index.rst @@ -43,6 +43,7 @@ Table of Contents :caption: Get Started Installation + Supported_Sensors Monteverdi .. toctree:: -- GitLab From 618ca42d2e4a1a8940c765f216984997b414b72b Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 2 Nov 2021 09:07:28 +0100 Subject: [PATCH 02/13] DOC: Precision on reading/writing vector data --- Documentation/Cookbook/rst/Supported_Sensors.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index 0af48ea5eb..f5017cf5c5 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -54,11 +54,13 @@ input. In that case, OTB will consider all the bands of the product. Vector images ~~~~~~~~~~~~~ -OTB implements two ways of dealing with vector data. The first one -uses OGR::Datasource. The second one uses otb::VectorData. Depending -on which class is used by the application, different formats are -available. This is confusing, and we plan on fixing this. For now, -formats fully supported (IE. supported by all applications) are: +OTB can read all vorctor format supported by ORG. But the writting +process is a little tricky. OTB implements two ways of dealing with +writting vector data. The first one uses OGR::Datasource. The second +one uses otb::VectorData. Depending on which class is used by the +application, different formats are available. This is confusing, and +we plan on fixing this. For now, formats fully supported +(IE. supported by all applications) are: - ESRI Shapefile (.shp) -- GitLab From 3d91b41e72282d4c824dbb41036ad20d149b7722 Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 2 Nov 2021 09:41:07 +0100 Subject: [PATCH 03/13] DOC: explaine particularity of HDF datasets --- .../Cookbook/rst/Supported_Sensors.rst | 63 +++++++++++-------- 1 file changed, 36 insertions(+), 27 deletions(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index f5017cf5c5..3f6223f695 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -7,7 +7,7 @@ supported by GDAL are theoretically also supported by OTB. That being said, there are some limitations. Raster images -~~~~~~~~~~~~~ +------------- GDAL provides a very large panel of drivers to access metadata in image files. OTB stores the metadata in a special dictionary called @@ -17,31 +17,31 @@ otbImageMetadata. Thus, to access metadata for a specific sensor, the corresponding interface is required. As this time, available interfaces are: -+------------------------+-------------------------+-------------------+ -| Sensor | Format | Notes | -+========================+=========================+===================+ -| CosmoSkyMed | HDF5 / TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| Formosat | DIMAP / TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| Ikonos | TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| Pleiades | JPEG2000 / TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| QuickBird | TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| Radarsat 2 | TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| Sentinel 1 | TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| Spot 5 | DIMAP / TIFF | RPC not available | -+------------------------+-------------------------+-------------------+ -| Spot 6 | DIMAP / JPEG2000 / TIFF | N/A | -+------------------------+-------------------------+-------------------+ -| TerraSarX | COS | N/A | -+------------------------+-------------------------+-------------------+ -| WorldView 2 | TIFF | N/A | -+------------------------+-------------------------+-------------------+ ++------------------------+-------------------------+-----------------------------+ +| Sensor | Format | Notes | ++========================+=========================+=============================+ +| CosmoSkyMed | HDF5 / TIFF | See HDF particularity below | ++------------------------+-------------------------+-----------------------------+ +| Formosat | DIMAP / TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| Ikonos | TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| Pleiades | JPEG2000 / TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| QuickBird | TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| Radarsat 2 | TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| Sentinel 1 | TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| Spot 5 | DIMAP / TIFF | RPC not available | ++------------------------+-------------------------+-----------------------------+ +| Spot 6 | DIMAP / JPEG2000 / TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ +| TerraSarX | COS | N/A | ++------------------------+-------------------------+-----------------------------+ +| WorldView 2 | TIFF | N/A | ++------------------------+-------------------------+-----------------------------+ Sensors not in this list can still be used with OTB, but the metadata won't be accessible. @@ -51,8 +51,17 @@ metadata files, etc). For SAR products, OTB takes necessarily an image file. For optical sensor, OTB can also take the manifest file as input. In that case, OTB will consider all the bands of the product. +A particularity of HDF datasets +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +When reading a HDF dataset, one needs to select the right subdataset +using the :doc:`Extended filenames` ``&sdataidx=<(int)idx>``. For +example, in some COsmoSkyMed products, the first subDataset is a +quicklook, and the actual product is the second subdataset. + + Vector images -~~~~~~~~~~~~~ +------------- OTB can read all vorctor format supported by ORG. But the writting process is a little tricky. OTB implements two ways of dealing with -- GitLab From bbd12f853cbd79abb4487c4c9777ee395a635106 Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 2 Nov 2021 09:58:42 +0100 Subject: [PATCH 04/13] DOC: Describe available output raster file formats --- .../Cookbook/rst/Supported_Sensors.rst | 31 ++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index 3f6223f695..15e6083fab 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -9,6 +9,9 @@ said, there are some limitations. Raster images ------------- +Reading a raster image +~~~~~~~~~~~~~~~~~~~~~~ + GDAL provides a very large panel of drivers to access metadata in image files. OTB stores the metadata in a special dictionary called otbImageMetadata. There is a metadata framework that uses interfaces @@ -51,12 +54,38 @@ metadata files, etc). For SAR products, OTB takes necessarily an image file. For optical sensor, OTB can also take the manifest file as input. In that case, OTB will consider all the bands of the product. +Writing a raster image +~~~~~~~~~~~~~~~~~~~~~~ + +OTB uses a correspondence table to link a specific file extension to a +GDAL driver. This means that formats not present in this table can't +be writen, even if the driver exists in GDAL. The formats available in +OTB for writing a raster are: + +- GTiff (.tif / .tiff) + +- ENVI (.hdr) + +- HFA (.img) + +- NITF (.ntf) + +- PNG (.png) + +- JPEG (.jpg / .jpeg) + +- PCIDSK (.pix) + +- ISIS2 (.lbl / .pds) + +- JP2OpenJPEG / JP2KAK / JP2ECW (.j2k / .jp2 / .jpx) + A particularity of HDF datasets ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When reading a HDF dataset, one needs to select the right subdataset using the :doc:`Extended filenames` ``&sdataidx=<(int)idx>``. For -example, in some COsmoSkyMed products, the first subDataset is a +example, in some CosmoSkyMed products, the first subDataset is a quicklook, and the actual product is the second subdataset. -- GitLab From 65bcb37818748af0b4aa1b56e4de0d4595688e0e Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 2 Nov 2021 10:06:05 +0100 Subject: [PATCH 05/13] DOC: Add precisions on which file to use for Sentinel1 and Terrasarx --- .../Cookbook/rst/Supported_Sensors.rst | 52 +++++++++---------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index 15e6083fab..0afa14509b 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -20,31 +20,31 @@ otbImageMetadata. Thus, to access metadata for a specific sensor, the corresponding interface is required. As this time, available interfaces are: -+------------------------+-------------------------+-----------------------------+ -| Sensor | Format | Notes | -+========================+=========================+=============================+ -| CosmoSkyMed | HDF5 / TIFF | See HDF particularity below | -+------------------------+-------------------------+-----------------------------+ -| Formosat | DIMAP / TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| Ikonos | TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| Pleiades | JPEG2000 / TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| QuickBird | TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| Radarsat 2 | TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| Sentinel 1 | TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| Spot 5 | DIMAP / TIFF | RPC not available | -+------------------------+-------------------------+-----------------------------+ -| Spot 6 | DIMAP / JPEG2000 / TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ -| TerraSarX | COS | N/A | -+------------------------+-------------------------+-----------------------------+ -| WorldView 2 | TIFF | N/A | -+------------------------+-------------------------+-----------------------------+ ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Sensor | Format | Notes | ++========================+=========================+====================================================================+ +| CosmoSkyMed | HDF5 / TIFF | See HDF particularity below | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Formosat | DIMAP / TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Ikonos | TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Pleiades | JPEG2000 / TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| QuickBird | TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Radarsat 2 | TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Sentinel 1 | TIFF | Use the tiff file, not the manifest | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Spot 5 | DIMAP / TIFF | RPC not available | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| Spot 6 | DIMAP / JPEG2000 / TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| TerraSarX | COS | Use the cos file, not the main XML. MGD products are not supported | ++------------------------+-------------------------+--------------------------------------------------------------------+ +| WorldView 2 | TIFF | N/A | ++------------------------+-------------------------+--------------------------------------------------------------------+ Sensors not in this list can still be used with OTB, but the metadata won't be accessible. @@ -89,7 +89,7 @@ example, in some CosmoSkyMed products, the first subDataset is a quicklook, and the actual product is the second subdataset. -Vector images +Vector data ------------- OTB can read all vorctor format supported by ORG. But the writting -- GitLab From 94336263f459a234eac2b01d15a8b80c1d3b82c2 Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 2 Nov 2021 10:19:05 +0100 Subject: [PATCH 06/13] DOC: Add link to Extended Filenames documentation --- Documentation/Cookbook/rst/ExtendedFilenames.rst | 2 ++ Documentation/Cookbook/rst/Supported_Sensors.rst | 9 +++++---- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/Documentation/Cookbook/rst/ExtendedFilenames.rst b/Documentation/Cookbook/rst/ExtendedFilenames.rst index 77f9651340..5f3d1b77f2 100644 --- a/Documentation/Cookbook/rst/ExtendedFilenames.rst +++ b/Documentation/Cookbook/rst/ExtendedFilenames.rst @@ -55,6 +55,8 @@ Reader options ----------------------------------------------- +.. _extended-filename-sdataidx: + :: &sdataidx=<(int)idx> diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index 0afa14509b..6f48c6308a 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -84,15 +84,16 @@ A particularity of HDF datasets ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When reading a HDF dataset, one needs to select the right subdataset -using the :doc:`Extended filenames` ``&sdataidx=<(int)idx>``. For -example, in some CosmoSkyMed products, the first subDataset is a -quicklook, and the actual product is the second subdataset. +using the :ref:`Extended Filename ` +``&sdataidx=<(int)idx>``. For example, in some CosmoSkyMed products, +the first subDataset is a quicklook, and the actual product is the +second subdataset. Vector data ------------- -OTB can read all vorctor format supported by ORG. But the writting +OTB can read all vorctor format supported by ORG. But the writing process is a little tricky. OTB implements two ways of dealing with writting vector data. The first one uses OGR::Datasource. The second one uses otb::VectorData. Depending on which class is used by the -- GitLab From f805e79e957dc8502e17e88be16cbe0395682e9a Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 2 Nov 2021 10:24:49 +0100 Subject: [PATCH 07/13] DOC: typos --- Documentation/Cookbook/rst/Supported_Sensors.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index 6f48c6308a..bf7a382031 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -59,7 +59,7 @@ Writing a raster image OTB uses a correspondence table to link a specific file extension to a GDAL driver. This means that formats not present in this table can't -be writen, even if the driver exists in GDAL. The formats available in +be written, even if the driver exists in GDAL. The formats available in OTB for writing a raster are: - GTiff (.tif / .tiff) @@ -93,9 +93,9 @@ second subdataset. Vector data ------------- -OTB can read all vorctor format supported by ORG. But the writing +OTB can read all vector format supported by ORG. But the writing process is a little tricky. OTB implements two ways of dealing with -writting vector data. The first one uses OGR::Datasource. The second +writing vector data. The first one uses OGR::Datasource. The second one uses otb::VectorData. Depending on which class is used by the application, different formats are available. This is confusing, and we plan on fixing this. For now, formats fully supported -- GitLab From bdea5d4a90f51fc6988568cfb6c3a04806503e8e Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Wed, 3 Nov 2021 14:13:23 +0100 Subject: [PATCH 08/13] DOC: Add a section about the DEM in supported sensors --- Documentation/Cookbook/rst/C++/DEM.rst | 21 ---------- .../Cookbook/rst/Supported_Sensors.rst | 39 ++++++++++++++++++- 2 files changed, 38 insertions(+), 22 deletions(-) diff --git a/Documentation/Cookbook/rst/C++/DEM.rst b/Documentation/Cookbook/rst/C++/DEM.rst index 13696c527f..e86aadd1f7 100644 --- a/Documentation/Cookbook/rst/C++/DEM.rst +++ b/Documentation/Cookbook/rst/C++/DEM.rst @@ -17,24 +17,3 @@ The ``otb::DEMHandler`` class is a singleton, a reference to the singleton objec * No SRTM and no geoid available: 0 Several DEM tiles can be provided at the same time, using the ``OpenDEMDirectory`` method. All raster from the input directory will be opened by GDAL. Internally, a mosaic of all DEM tiles is then created as a virtual dataset (vrt). - -All raster that can be opened by gdal can be used as a geoid. In previous OTB versions (using Ossim) it was common to use the egm96.grd file as geoid, this file cannot be opened by GDAL. However it is still possible to use it by using the following egm96.grd.hdr file:: - - ENVI - samples = 1441 - lines = 721 - bands = 1 - header offset = 24 - file type = ENVI Standard - data type = 4 - interleave = bsq - sensor type = Unknown - byte order = 1 - wavelength units = Unknown - map info = {Geographic Lat/Lon, 1, 1,-0.125, 90.125, 0.25, 0.25,WGS-84} - coordinate system string = {GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]]} - band names = { - Band 1} - - -With this file attached, GDAL will be able to read the egm96.grd file as a ENVI dataset \ No newline at end of file diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index bf7a382031..367ee371ef 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -91,7 +91,7 @@ second subdataset. Vector data -------------- +----------- OTB can read all vector format supported by ORG. But the writing process is a little tricky. OTB implements two ways of dealing with @@ -115,3 +115,40 @@ we plan on fixing this. For now, formats fully supported - GeoPackage (.gpkg) +Digital Elevation Modele +------------------------ + +OTB also relies on GDAL to access DEM data. Therefore, any raster +format supported by GDAL can be used as DEM. Several DEM tiles can be +provided at the same time by providing a directory. All raster from +the input directory will be opened by GDAL. + +It is the same for the geoid. + +A note on the egm96.grd file +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In previous OTB versions (using Ossim) it was common to use the +egm96.grd file as geoid. This file cannot be opened by GDAL. However +it is still possible to use it by using the following egm96.grd.hdr +file:: + + ENVI + samples = 1441 + lines = 721 + bands = 1 + header offset = 24 + file type = ENVI Standard + data type = 4 + interleave = bsq + sensor type = Unknown + byte order = 1 + wavelength units = Unknown + map info = {Geographic Lat/Lon, 1, 1,-0.125, 90.125, 0.25, 0.25,WGS-84} + coordinate system string = {GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]]} + band names = { + Band 1} + + +With this file attached, GDAL will be able to read the egm96.grd file +as a ENVI dataset. -- GitLab From a9026606ac01d69029771114be3b1017e5aa121a Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Wed, 3 Nov 2021 14:32:07 +0100 Subject: [PATCH 09/13] DOC: Typo --- Documentation/Cookbook/rst/Supported_Sensors.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index 367ee371ef..a992ea7a05 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -93,7 +93,7 @@ second subdataset. Vector data ----------- -OTB can read all vector format supported by ORG. But the writing +OTB can read all vector formats supported by OGR. But the writing process is a little tricky. OTB implements two ways of dealing with writing vector data. The first one uses OGR::Datasource. The second one uses otb::VectorData. Depending on which class is used by the @@ -115,8 +115,8 @@ we plan on fixing this. For now, formats fully supported - GeoPackage (.gpkg) -Digital Elevation Modele ------------------------- +Digital Elevation Model +----------------------- OTB also relies on GDAL to access DEM data. Therefore, any raster format supported by GDAL can be used as DEM. Several DEM tiles can be -- GitLab From 01bb55184fa618b2d43aa6557b55daa8deda53e4 Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 9 Nov 2021 16:03:08 +0100 Subject: [PATCH 10/13] DOC: Add info about Pleiades and DIMAP --- Documentation/Cookbook/rst/Supported_Sensors.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index a992ea7a05..a59880f19a 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -29,7 +29,7 @@ interfaces are: +------------------------+-------------------------+--------------------------------------------------------------------+ | Ikonos | TIFF | N/A | +------------------------+-------------------------+--------------------------------------------------------------------+ -| Pleiades | JPEG2000 / TIFF | N/A | +| Pleiades | JPEG2000 / TIFF | Don't use the DIMAP file, it causes a 0.5 pixel shift | +------------------------+-------------------------+--------------------------------------------------------------------+ | QuickBird | TIFF | N/A | +------------------------+-------------------------+--------------------------------------------------------------------+ -- GitLab From 9a93b56ffc48e0cbe2d5e57c0c5493a8333cc37a Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 9 Nov 2021 16:04:41 +0100 Subject: [PATCH 11/13] DOC: Describe the -elem parameters --- .../Cookbook/rst/Supported_Sensors.rst | 24 +++++++++++++++---- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index a59880f19a..ddb8cf951c 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -118,13 +118,27 @@ we plan on fixing this. For now, formats fully supported Digital Elevation Model ----------------------- -OTB also relies on GDAL to access DEM data. Therefore, any raster -format supported by GDAL can be used as DEM. Several DEM tiles can be -provided at the same time by providing a directory. All raster from -the input directory will be opened by GDAL. +Many OTB application use an elevation model as input, usually with the +parameter “-elev.dem”. This parameter accepts any raster file +supported by GDAL, or a directory containing such files. In this +second case, all rasters from the input directory will be opened by +GDAL, so it could be a good idea to use a VRT. Beware that the DEM +folder should contain only DEM files. It is the same for the geoid +with the parameter "-elev.geoid". One can usually set a default +elevation with the parameter "-elev.default". -It is the same for the geoid. +Depending on the provided parameters, the application will: +- compute the DEM + the value of the geoid if both the DEM and the + geoid are provided. + +- use the default value if none is provided. + +- use the value read in the DEM if only the DEM is provided. + +- compute the default elevation + the value of the geoid if only the + geoid is povided. + A note on the egm96.grd file ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- GitLab From 1bd55fb83f0cdc08e3454411edf5675a914586dd Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Tue, 9 Nov 2021 16:20:38 +0100 Subject: [PATCH 12/13] DOC: typo --- Documentation/Cookbook/rst/Supported_Sensors.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index ddb8cf951c..d198cb9086 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -137,7 +137,7 @@ Depending on the provided parameters, the application will: - use the value read in the DEM if only the DEM is provided. - compute the default elevation + the value of the geoid if only the - geoid is povided. + geoid is provided. A note on the egm96.grd file ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- GitLab From 41c2375d95859bbb550156bd9e7397ce649979e7 Mon Sep 17 00:00:00 2001 From: Julien Osman Date: Thu, 18 Nov 2021 15:22:29 +0100 Subject: [PATCH 13/13] DOC: Document spot 7 --- Documentation/Cookbook/rst/Supported_Sensors.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Cookbook/rst/Supported_Sensors.rst b/Documentation/Cookbook/rst/Supported_Sensors.rst index d198cb9086..01cdda1dba 100644 --- a/Documentation/Cookbook/rst/Supported_Sensors.rst +++ b/Documentation/Cookbook/rst/Supported_Sensors.rst @@ -39,7 +39,7 @@ interfaces are: +------------------------+-------------------------+--------------------------------------------------------------------+ | Spot 5 | DIMAP / TIFF | RPC not available | +------------------------+-------------------------+--------------------------------------------------------------------+ -| Spot 6 | DIMAP / JPEG2000 / TIFF | N/A | +| Spot 6/7 | DIMAP / JPEG2000 / TIFF | N/A | +------------------------+-------------------------+--------------------------------------------------------------------+ | TerraSarX | COS | Use the cos file, not the main XML. MGD products are not supported | +------------------------+-------------------------+--------------------------------------------------------------------+ -- GitLab