ossim-developer — Software development list for OSSIM

Re: [OSSIM] Direction on how to install on Ubuntu 22.04

[Trey W. <tre...@gm...>]

Hey Dave,

Thanks for your reply! So I was able to get it going. After running
ossim-info ––plugins I saw that the plugins were not getting loaded which
then pointed me to my preferences file missing some edits.

All is well now! Thank you so much for your time and help!

Thanks,
Trey

On Mon, Jun 9, 2025 at 07:40 David Burken <db...@gm...> wrote:

> I'm not really sure on the gdal configuration.  Your best bet would be to
> ping their list on how to enable j2k support.
>
> Are you sure it's j2k. You should be able to do a dump of tags and look
> for "nitf.image0.IC:  C8".
> IC == image compression:
>
> ossim-info -d your.ntf
>
> Dave
>
>
> On Sun, Jun 8, 2025 at 8:05 PM Trey Winbush <tre...@gm...>
> wrote:
>
>> Dave! Thank you so much for the response!
>>
>> I have the GDAL plugin, but I must not have compiled the plugin
>> correctly. The gdalinfo command can read it fine, but ossim-info does not.
>> I’m assuming that implies that the gdal plugin configuration was not setup
>> correctly.
>>
>> I will check the configuration. Can you help guide me on what
>> directory/library might be missing/not getting specified?
>>
>> Thanks,
>> Trey Winbush
>>
>>
>> On Sun, Jun 8, 2025 at 08:02 David Burken <db...@gm...> wrote:
>>
>>> Hi Trey,
>>>
>>> Is the nitf j2k compressed? If so, you need a plugin. Either kakadu,
>>> gdal compiled with j2k support, openjpeg. You can test by doing:
>>>
>>> $ ossim-info -d  5V090205P0001912264B220000100282M_001508507.ntf | grep
>>> IC
>>> // C8 is j2k.
>>> nitf.image0.IC:  C8
>>>
>>> // With no plugins:
>>> $ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
>>> ossimInfo::openImage ERROR:
>>> Could not open: 5V090205P0001912264B220000100282M_001508507.ntf
>>>
>>> // Added kakadu plugin:
>>> $ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
>>> ...
>>> image0.driver:  ossim_kakadu_nitf_reader
>>> ...
>>> image0.type:  ossimKakaduNitfReader
>>>
>>> To test your config you can use:
>>>
>>> // dumps preferences file:
>>> $ ossim-info --config
>>>
>>> // plugins:
>>> $ ossim-info --plugins
>>>
>>> // Check config:
>>> $ ossim-info --check-config
>>>
>>> Hope that helps,
>>> Dave
>>>
>>>

Re: [OSSIM] Direction on how to install on Ubuntu 22.04

[David B. <db...@gm...>]

I'm not really sure on the gdal configuration.  Your best bet would be to
ping their list on how to enable j2k support.

Are you sure it's j2k. You should be able to do a dump of tags and look for
"nitf.image0.IC:  C8".
IC == image compression:

ossim-info -d your.ntf

Dave


On Sun, Jun 8, 2025 at 8:05 PM Trey Winbush <tre...@gm...>
wrote:

> Dave! Thank you so much for the response!
>
> I have the GDAL plugin, but I must not have compiled the plugin correctly.
> The gdalinfo command can read it fine, but ossim-info does not. I’m
> assuming that implies that the gdal plugin configuration was not setup
> correctly.
>
> I will check the configuration. Can you help guide me on what
> directory/library might be missing/not getting specified?
>
> Thanks,
> Trey Winbush
>
>
> On Sun, Jun 8, 2025 at 08:02 David Burken <db...@gm...> wrote:
>
>> Hi Trey,
>>
>> Is the nitf j2k compressed? If so, you need a plugin. Either kakadu, gdal
>> compiled with j2k support, openjpeg. You can test by doing:
>>
>> $ ossim-info -d  5V090205P0001912264B220000100282M_001508507.ntf | grep IC
>> // C8 is j2k.
>> nitf.image0.IC:  C8
>>
>> // With no plugins:
>> $ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
>> ossimInfo::openImage ERROR:
>> Could not open: 5V090205P0001912264B220000100282M_001508507.ntf
>>
>> // Added kakadu plugin:
>> $ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
>> ...
>> image0.driver:  ossim_kakadu_nitf_reader
>> ...
>> image0.type:  ossimKakaduNitfReader
>>
>> To test your config you can use:
>>
>> // dumps preferences file:
>> $ ossim-info --config
>>
>> // plugins:
>> $ ossim-info --plugins
>>
>> // Check config:
>> $ ossim-info --check-config
>>
>> Hope that helps,
>> Dave
>>
>>

Re: [OSSIM] Direction on how to install on Ubuntu 22.04

[Trey W. <tre...@gm...>]

Dave! Thank you so much for the response!

I have the GDAL plugin, but I must not have compiled the plugin correctly.
The gdalinfo command can read it fine, but ossim-info does not. I’m
assuming that implies that the gdal plugin configuration was not setup
correctly.

I will check the configuration. Can you help guide me on what
directory/library might be missing/not getting specified?

Thanks,
Trey Winbush


On Sun, Jun 8, 2025 at 08:02 David Burken <db...@gm...> wrote:

> Hi Trey,
>
> Is the nitf j2k compressed? If so, you need a plugin. Either kakadu, gdal
> compiled with j2k support, openjpeg. You can test by doing:
>
> $ ossim-info -d  5V090205P0001912264B220000100282M_001508507.ntf | grep IC
> // C8 is j2k.
> nitf.image0.IC:  C8
>
> // With no plugins:
> $ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
> ossimInfo::openImage ERROR:
> Could not open: 5V090205P0001912264B220000100282M_001508507.ntf
>
> // Added kakadu plugin:
> $ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
> ...
> image0.driver:  ossim_kakadu_nitf_reader
> ...
> image0.type:  ossimKakaduNitfReader
>
> To test your config you can use:
>
> // dumps preferences file:
> $ ossim-info --config
>
> // plugins:
> $ ossim-info --plugins
>
> // Check config:
> $ ossim-info --check-config
>
> Hope that helps,
> Dave
>
>

Re: [OSSIM] Direction on how to install on Ubuntu 22.04

[David B. <db...@gm...>]

Hi Trey,

Is the nitf j2k compressed? If so, you need a plugin. Either kakadu, gdal
compiled with j2k support, openjpeg. You can test by doing:

$ ossim-info -d  5V090205P0001912264B220000100282M_001508507.ntf | grep IC
// C8 is j2k.
nitf.image0.IC:  C8

// With no plugins:
$ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
ossimInfo::openImage ERROR:
Could not open: 5V090205P0001912264B220000100282M_001508507.ntf

// Added kakadu plugin:
$ ossim-info  5V090205P0001912264B220000100282M_001508507.ntf
...
image0.driver:  ossim_kakadu_nitf_reader
...
image0.type:  ossimKakaduNitfReader

To test your config you can use:

// dumps preferences file:
$ ossim-info --config

// plugins:
$ ossim-info --plugins

// Check config:
$ ossim-info --check-config

Hope that helps,
Dave

[OSSIM] Direction on how to install on Ubuntu 22.04

[Trey W. <tre...@gm...>]

Good Day,

I am trying to understand how to install OSSIM on an
nvidia/cuda:12.0.0-cudnn8-devel-ubuntu22.04 image. I am able to
successfully install, but I cannot successfully open a NITF image.

I believe I have all of the libraries, but would you be able to point me to
the libraries I need to have in order to load a nitf?

Thanks,
Trey Winbush

Trey Winbush
tre...@gm...

[OSSIM] inquiry about Building OSSIM with GUI - Seeking Step-by-Step Guidance

[M b. R. <b2....@gm...>]

Dear OSSIM Developers,

I hope this email finds you well. My name is [Your Name], and I am reaching
out to you because I am interested in building OSSIM with a graphical user
interface (GUI). I have been using OSSIM for [mention your experience or
duration of use], and I believe that a GUI would enhance the usability of
the software for various tasks.

I am reaching out to seek your guidance on the step-by-step process to
build OSSIM with a GUI. I have experience with [mention any relevant
programming languages or development tools you are familiar with], and I am
eager to contribute to the project by adding this feature.

If there is any documentation, guidelines, or specific steps that you could
provide, it would be greatly appreciated. Additionally, if there are
specific tools or libraries that are recommended for building the GUI,
please let me know.

I understand that your time is valuable, and I appreciate any assistance or
direction you can provide on this matter. I am enthusiastic about the
prospect of contributing to the OSSIM project and look forward to your
guidance.

Thank you for your time and consideration. I am looking forward to hearing
from you.

Best regards,

Re: [OSSIM] OSSIM Elevation

[Mike T. <mik...@gm...>]

Hi Dave,

Thanks for the quick reply!!!

Changing to raster_directory worked! I had previously tried
"general_raster_directory" as I had somehow thought that was the correct
value.

Mike

On Tue, Dec 6, 2022 at 4:12 PM David Burken <db...@gm...> wrote:

> Hi Mike,
>
> elevation_manager.elevation_source0.type: srtm_directory
>
> Would look for dot.hgt files(raw raster). If you want to use tiffs change
> it to "image_directory". Also don't forget to setup the geoid in your
> preferences.
> geoid_egm_96_grid:  /usr/local/ossim/share/ossim/geoids/egm96.grd
>
> $ ossim-info --height 39.5 -105.5
> elevation.info.cell:  /data1/elevation/srtm/1arc/N39W106.hgt
> elevation.info.geoid_name:  geoid1996
> elevation.info.geoid_offset:  -13.8020000457764
> elevation.info.gpt:  (39.5,-105.5,0,WGE)
> elevation.info.height_above_ellipsoid:  2769.19799995422
> elevation.info.height_above_msl:  2783
>
> Hope that helps.
>
> Take care,
> Dave
>
>
> On Tue, Dec 6, 2022 at 6:04 PM Mike Thompson <mik...@gm...> wrote:
>
>> I recently built and installed OSSIM but am having trouble using
>> elevation data.
>> OS: Ubuntu 22.04.1 LTS
>> ossim-info --version
>> 1.9.0
>>
>> Snip from my ossim_preferences.txt file:
>> elevation_manager.elevation_source0.connection_string:
>> $(OSSIM_DATA)/elevation/srtm/1arc_tif_from_USGS
>> //elevation_manager.elevation_source0.connection_string:
>> /home/mike/elevation/srtm/1arc_dt2_from_USGS
>> //elevation_manager.elevation_source0.connection_string:
>> /home/mike/elevation/srtm/1arc_ras_from_tif
>> //elevation_manager.elevation_source0.connection_string:
>> /home/mike/elevation/srtm/1arc_bil_from_USGS
>> //elevation_manager.elevation_source0.filename:
>> /home/mike/elevation/srtm/1arc_bil_from_USGS
>> elevation_manager.elevation_source0.enabled: true
>> elevation_manager.elevation_source0.type: srtm_directory
>> elevation_manager.elevation_source0.min_open_cells: 25
>> elevation_manager.elevation_source0.max_open_cells: 50
>> elevation_manager.elevation_source0.memory_map_cells: false
>> elevation_manager.elevation_source0.geoid.type: geoid1996
>>
>> (the lines which are commented out are other things I have tried)
>>
>> I downloaded 1 arc second SRTM data from USGS, I tried all available
>> formats: .bil, .tif, and .dt2.  I also tried converting the .tif to a .ras.
>> Specifically, I downloaded n39_w106_1arc_v2.*
>>
>> ossim-info --check-config reports:
>> elevation sources loaded:
>> elevation_source[0].connetion_string:
>> /home/mike/elevation/srtm/1arc_tif_from_USGS
>>
>> This is encouraging, but
>> $ ossim-info --height 39.5 -105.5
>> reports:
>> elevation.info.cell:  not_found
>>
>> I loaded the data from USGS into QGIS to confirm my assumption that 39.5
>> -105.5 is within the specified file.
>>
>> I have also tried renaming the SRTM files from the USGS to:
>> n39w106.*
>> which I understand is the convention for SRTM.
>>
>> Any help would be appreciated.
>>
>> Thanks,
>>
>> Mike
>>
>> _______________________________________________
>> www.ossim.org
>> Ossim-developer mailing list
>> Oss...@li...
>> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>>
>

Re: [OSSIM] OSSIM Elevation

[David B. <db...@gm...>]

Hi Mike,

elevation_manager.elevation_source0.type: srtm_directory

Would look for dot.hgt files(raw raster). If you want to use tiffs change
it to "image_directory". Also don't forget to setup the geoid in your
preferences.
geoid_egm_96_grid:  /usr/local/ossim/share/ossim/geoids/egm96.grd

$ ossim-info --height 39.5 -105.5
elevation.info.cell:  /data1/elevation/srtm/1arc/N39W106.hgt
elevation.info.geoid_name:  geoid1996
elevation.info.geoid_offset:  -13.8020000457764
elevation.info.gpt:  (39.5,-105.5,0,WGE)
elevation.info.height_above_ellipsoid:  2769.19799995422
elevation.info.height_above_msl:  2783

Hope that helps.

Take care,
Dave


On Tue, Dec 6, 2022 at 6:04 PM Mike Thompson <mik...@gm...> wrote:

> I recently built and installed OSSIM but am having trouble using elevation
> data.
> OS: Ubuntu 22.04.1 LTS
> ossim-info --version
> 1.9.0
>
> Snip from my ossim_preferences.txt file:
> elevation_manager.elevation_source0.connection_string:
> $(OSSIM_DATA)/elevation/srtm/1arc_tif_from_USGS
> //elevation_manager.elevation_source0.connection_string:
> /home/mike/elevation/srtm/1arc_dt2_from_USGS
> //elevation_manager.elevation_source0.connection_string:
> /home/mike/elevation/srtm/1arc_ras_from_tif
> //elevation_manager.elevation_source0.connection_string:
> /home/mike/elevation/srtm/1arc_bil_from_USGS
> //elevation_manager.elevation_source0.filename:
> /home/mike/elevation/srtm/1arc_bil_from_USGS
> elevation_manager.elevation_source0.enabled: true
> elevation_manager.elevation_source0.type: srtm_directory
> elevation_manager.elevation_source0.min_open_cells: 25
> elevation_manager.elevation_source0.max_open_cells: 50
> elevation_manager.elevation_source0.memory_map_cells: false
> elevation_manager.elevation_source0.geoid.type: geoid1996
>
> (the lines which are commented out are other things I have tried)
>
> I downloaded 1 arc second SRTM data from USGS, I tried all available
> formats: .bil, .tif, and .dt2.  I also tried converting the .tif to a .ras.
> Specifically, I downloaded n39_w106_1arc_v2.*
>
> ossim-info --check-config reports:
> elevation sources loaded:
> elevation_source[0].connetion_string:
> /home/mike/elevation/srtm/1arc_tif_from_USGS
>
> This is encouraging, but
> $ ossim-info --height 39.5 -105.5
> reports:
> elevation.info.cell:  not_found
>
> I loaded the data from USGS into QGIS to confirm my assumption that 39.5
> -105.5 is within the specified file.
>
> I have also tried renaming the SRTM files from the USGS to:
> n39w106.*
> which I understand is the convention for SRTM.
>
> Any help would be appreciated.
>
> Thanks,
>
> Mike
>
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>

[OSSIM] OSSIM Elevation

[Mike T. <mik...@gm...>]

I recently built and installed OSSIM but am having trouble using elevation
data.
OS: Ubuntu 22.04.1 LTS
ossim-info --version
1.9.0

Snip from my ossim_preferences.txt file:
elevation_manager.elevation_source0.connection_string:
$(OSSIM_DATA)/elevation/srtm/1arc_tif_from_USGS
//elevation_manager.elevation_source0.connection_string:
/home/mike/elevation/srtm/1arc_dt2_from_USGS
//elevation_manager.elevation_source0.connection_string:
/home/mike/elevation/srtm/1arc_ras_from_tif
//elevation_manager.elevation_source0.connection_string:
/home/mike/elevation/srtm/1arc_bil_from_USGS
//elevation_manager.elevation_source0.filename:
/home/mike/elevation/srtm/1arc_bil_from_USGS
elevation_manager.elevation_source0.enabled: true
elevation_manager.elevation_source0.type: srtm_directory
elevation_manager.elevation_source0.min_open_cells: 25
elevation_manager.elevation_source0.max_open_cells: 50
elevation_manager.elevation_source0.memory_map_cells: false
elevation_manager.elevation_source0.geoid.type: geoid1996

(the lines which are commented out are other things I have tried)

I downloaded 1 arc second SRTM data from USGS, I tried all available
formats: .bil, .tif, and .dt2.  I also tried converting the .tif to a .ras.
Specifically, I downloaded n39_w106_1arc_v2.*

ossim-info --check-config reports:
elevation sources loaded:
elevation_source[0].connetion_string:
/home/mike/elevation/srtm/1arc_tif_from_USGS

This is encouraging, but
$ ossim-info --height 39.5 -105.5
reports:
elevation.info.cell:  not_found

I loaded the data from USGS into QGIS to confirm my assumption that 39.5
-105.5 is within the specified file.

I have also tried renaming the SRTM files from the USGS to:
n39w106.*
which I understand is the convention for SRTM.

Any help would be appreciated.

Thanks,

Mike

[OSSIM] I need the OSSIM test public data

[m13840348310 <138...@16...>]

Hello, I have been testing the functions of ossim recently, and I need the open data of Amazon S3 in test/config. May I ask how can I get the data

thank you



| |
刘明轩
|
|
138...@16...
|

Re: [OSSIM] ossim test-data access.

[Garrett P. <gc...@ma...>]

Hello Ed:

Thank you for the additions.  The easiest thing is to create a pull request for the additions and I will peep at them.  Please make sure it is off the latest dev branch and do a pull request for the dev branch and we will take a look

I have started adding MPI to the CMKAE but was unsuccessfull in allowing one to select between MPICH or OpenMPI.  Will give it a try.



Thank you again!


Take care

Garrett


> On May 19, 2020, at 5:14 PM, Ed Leaver <ewl...@co...> wrote:
> 
> Hi. I've three very minor ossim patches I'd like to test and push. Or push and test. What is the standard test procedure? Do ossim developers typically run the test suite locally, or let your Jenkins server handle it? To me the https://github.com/ossimlabs/ossim/blob/master/README.md is not at all clear. Neither is ossim-batch-test --help.
> 
> What I (think I) have done:
> 1. Enabled HDF5 as an OPTION (rather than just an environment variable) in ossim/CMakeLists.txt
> 2. Added include_directories( ${MPI_CXX_INCLUDE_DIRS} ${MPI_C_INCLUDE_DIRS} ) in ossim/CMakeLists to enable MPI on Fedora 32 (and perhaps others).
> 3. Taken ossimRpcModel's destructor public, as ossimRpcModel is a concrete base class (I've an application that uses it as such).
> 
> Thanks!
> 
> 
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer

[OSSIM] ossim test-data access.

[Ed L. <ewl...@co...>]

Hi. I've three very minor ossim patches I'd like to test and push. Or 
push and test. What is the standard test procedure? Do ossim developers 
typically run the test suite locally, or let your Jenkins server handle 
it? To me the https://github.com/ossimlabs/ossim/blob/master/README.md 
is not at all clear. Neither is ossim-batch-test --help.

What I (think I) have done:
1. Enabled HDF5 as an OPTION (rather than just an environment variable) 
in ossim/CMakeLists.txt
2. Added include_directories( ${MPI_CXX_INCLUDE_DIRS} 
${MPI_C_INCLUDE_DIRS} ) in ossim/CMakeLists to enable MPI on Fedora 32 
(and perhaps others).
3. Taken ossimRpcModel's destructor public, as ossimRpcModel is a 
concrete base class (I've an application that uses it as such).

Thanks!

Re: [OSSIM] Displaying Shapefiles using OSSIM Geocell

[David B. <db...@gm...>]

Hi Elan,

Man that's old, i.e. 2015. Let do some checking and I'll get back to you 
directly... Would like to spin up a build

Take care,
Dave


On 4/1/20 1:20 PM, Elan S wrote:
> Hi,
>
> I'm new to using OSSIM Geocell. Is it possible to display shapefiles 
> and its attribute information using this application? I know the old 
> application Imagelinker supports shapefiles, but I'm having trouble 
> doing this using the installer version of OSSIM built in 2015.
>
> http://download.osgeo.org/ossim/installers/windows/
>
> Thanks,
> Elan
>
>
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer

[OSSIM] Displaying Shapefiles using OSSIM Geocell

[Elan S <el...@gm...>]

Hi,

I'm new to using OSSIM Geocell. Is it possible to display shapefiles and
its attribute information using this application? I know the old
application Imagelinker supports shapefiles, but I'm having trouble doing
this using the installer version of OSSIM built in 2015.

http://download.osgeo.org/ossim/installers/windows/

Thanks,
Elan

Re: [OSSIM] JsonCPP re-amalgamated in OSSIM

[Potts, G. <Gar...@ma...>]

Hello Oscar:

I would allow to enable internal and external supported builds.   Also,  not sure if there would be symbol conflicts if someone is building to jsoncpp for another library and linking to ossim.


Take care

Garrett


From: Oscar Kramer <osc...@ya...>
Reply-To: Oscar Kramer <osc...@ya...>
Date: Wednesday, September 18, 2019 at 10:36 AM
To: "Potts, Garrett" <Gar...@ma...>, David Burken <db...@pr...>
Cc: OSSIM Developers <oss...@li...>
Subject: JsonCPP re-amalgamated in OSSIM

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

All,

I re-added the amalgamated form of jsoncpp to ossim and related repos. That removes the dependency on an external library that wasn't available as a simple "apt install" for ubuntu systems, and likely was a pain for other systems as well. That necessitated building the library from source and adding the infrastructure to find the includes and lib -- an unnecessary complication. We used to use the amalgamated form (i.e., the .h and .cpp included as part of the OSSIM build) until someone complained of licensing. I see that JsonCPP now shares the same MIT license as OSSIM, and specifically states:


Copyright (c) 2007-2010 Baptiste Lepilleur and The JsonCpp Authors

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
So that should no longer be a problem. JsonCPP provides the tools to create this amalgamated form, so this follows the intent of the authors.

Oscar

[OSSIM] JsonCPP re-amalgamated in OSSIM

[Oscar K. <osc...@ya...>]

All,
I re-added the amalgamated form of jsoncpp to ossim and related repos. That removes the dependency on an external library that wasn't available as a simple "apt install" for ubuntu systems, and likely was a pain for other systems as well. That necessitated building the library from source and adding the infrastructure to find the includes and lib -- an unnecessary complication. We used to use the amalgamated form (i.e., the .h and .cpp included as part of the OSSIM build) until someone complained of licensing. I see that JsonCPP now shares the same MIT license as OSSIM, and specifically states:
Copyright (c) 2007-2010 Baptiste Lepilleur and The JsonCpp Authors

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.So that should no longer be a problem. JsonCPP provides the tools to create this amalgamated form, so this follows the intent of the authors.
Oscar

[OSSIM] Adjustment parameters

[felicia m. <fel...@gm...>]

Hi, everybody! 
I'm a student and I'm doing some research on the OSSIM library. In particular I'm studying orthorectification with OrfeoToolBox but I'm not able to calculate the Adjustment Parameters used to fit the sensor model. I would like to have some information on how they are calculated. 
Thank you and congratulations for your work
Felicia

Inviato da Posta per Windows 10

Re: [OSSIM] OSSIM Input Data

[David B. <db...@gm...>]

Hi Dennis,

If you're referring to the data used by this git module:

https://github.com/ossimlabs/ossim-batch-test

I suspect you'll not get it as it's riddled with non-releasable data. 
You'd have to reach out to Radiant Solutions guys for that. They are on 
the mailing list, but quiet:-)

The way ossim-batch-test works though it is pretty easy to set up you're 
on test. The simplest of all takes no input data as it just checks the 
configuration. Just committed it. See:

https://github.com/ossimlabs/ossim-batch-test/blob/dev/config-test.kwl

For instance if you're satisfied with your ossim preferences / config 
setup you can do
// Dump ossim preferences:
ossim-info --config

// Check the plugins:
ossim-info --plugins

// Here are my environment variables:
OSSIM_PREFS_FILE=/usr/local/ossim/share/ossim/ossim-site-preferences
OSSIM_BATCH_TEST_DATA=/data1/test/data
OSSIM_BATCH_TEST_RESULTS=/data1/test/results/linux

// If you like the results save it to the "expected results" dir. "-a" 
for accept all test:
ossim-batch-test -a config-test.kwl

// Then is you do, this will catch any config/plugin changes:
ossim-batch-test config-test.kwl

So you can do the same thing with image data. I like to test:
ossim-info -d -i -p <image>

Also the histogram, if one pixel changes in an output of say 
ossim-chipper you'll see it.

Sorry not much help but maybe a start.

Take care,
Dave


On 12/19/18 4:31 PM, Milechin, Dennis wrote:
>
> Hello,
>
> I am hoping to get access to the OSSIM input data for 
> ‘ossim-batch-tests’ program.
>
> Thank you,
>
> Dennis
>
> _________________________________________________________
>
> Dennis Milechin, P.E.
>
> Scientific Programmer/Analyst
>
> Research Computing Services | IS&T | Boston University |
>
> (617)-353-5985 | mil...@bu... <mailto:mil...@bu...> | rcs.bu.edu 
> | he...@sc... <mailto:he...@sc...>
>
>
>
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer

Re: [OSSIM] Linking issue on reg plugin

[Jon S. <sel...@gm...>]

Take a look at this to see if it will meet your needs:

https://www.orfeo-toolbox.org/CookBook/recipes/residual_registration.html

Developed for satellite images but uses a .geom file for georefererencing
and calculating image adjustments.

On Thu, Dec 20, 2018, 7:00 PM Mike Finnessy <mik...@gm... wrote:

> Just saw this older post...bummer.  I don't know if you guys can provide
> context for why it was retired?
>
> *Re: [OSSIM] (no subject)
> <https://sourceforge.net/p/ossim/mailman/message/36015211/>*
> From: Oscar Kramer <oscar.kramer@di...> - 2017-08-28 13:15:35
> *Attachments:* image001.png
> <https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/1/>
>  image002.png
> <https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/2/>
>  Message as HTML
> <https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/3/>
>
> Prakash,
>
> Nearly two years ago we migrated OSSIM 1.8.20 from SVN to git and tagged
> that 1.9. The items to be moved were prioritized by perceived need and some
> packages didn't make it over. One of those was the ossim-plugins/reg. There
> is in fact a different ossim-plugins/reg in github which was intended to
> replace the old one, but that has not materialized.
>
> You are welcome to explore the old reg plugin (containing
> ossimImageCorrelator) here <http://download.osgeo.org/ossim/source/latest/>;.
> But keep in mind that the code there is way behind, and was never
> thoroughly tested. It will probably be a nontrivial effort to get that up
> and running for your needs.
>
> Oscar
>
>
> On Wed, Dec 19, 2018 at 7:36 PM Mike Finnessy <mik...@gm...>
> wrote:
>
>> HI,
>>
>> I'm in need of performing imagery co-registration and came across your
>> product.  I desire to be a first time user, and see if the reg plugin will
>> meet our needs.  It looks like in order to use that particular plugin I
>> need to build rather than using the linux packages that are out there.  I'm
>> currently working on building a docker image pulling from ubuntu:18.04,
>> building and installing opencv (3.2.0), building and installing ossim-core
>> and ossim-plugins.  Right now everything appears to install correctly and I
>> am able to use the ossim core functionality as well as the potrace plugin
>> (which is the only other plugin I have installed.  Here is the build I am
>> using which I shamelessly borrowed from
>> https://github.com/johntut/ossim-gis:
>>
>> ENV OSSIM_DEV_HOME=/usr/local/src/ossim
>>
>>
>> ENV OSSIM_BUILD_DIR=$OSSIM_DEV_HOME/build \
>>
>>     OSSIM_DEPENDENCIES=/usr
>>
>>
>> #WORKDIR $OSSIM_DEV_HOME
>>
>> RUN git clone https://github.com/ossimlabs/ossim.git $OSSIM_DEV_HOME && \
>>
>>     cd $OSSIM_DEV_HOME && \
>>
>>     git checkout tags/Juno-2.6.1
>>
>> #    git checkout master
>>
>> #RUN wget https://github.com/ossimlabs/ossim/archive/Juno-2.6.1.zip
>>
>>
>> RUN git clone https://github.com/ossimlabs/ossim-plugins.git
>> $OSSIM_DEV_HOME/ossim-plugins && \
>>
>>     cd $OSSIM_DEV_HOME/ossim-plugins && \
>>
>>     git checkout tags/Juno-2.6.1
>>
>> #    git checkout master
>>
>> #RUN wget
>>
>>
>> RUN mkdir $OSSIM_BUILD_DIR
>>
>> WORKDIR $OSSIM_BUILD_DIR
>>
>>
>> # Make and install ossim.
>>
>>
>> RUN cmake .. \
>>
>>     -DOSSIM_LIBRARY=$OSSIM_BUILD_DIR/lib/libossim.so \
>>
>>     -DOSSIM_INCLUDE_DIR=$OSSIM_DEV_HOME/include \
>>
>>     -DBUILD_OSSIM_TESTS=OFF
>>
>>
>> RUN make && make install && ldconfig
>>
>>
>> # Make and install plugins.
>>
>>
>> RUN mkdir $OSSIM_DEV_HOME/ossim-plugins/build
>>
>> WORKDIR $OSSIM_DEV_HOME/ossim-plugins/build
>>
>>
>> RUN cmake .. \
>>
>>     -DOSSIM_INSTALL_PREFIX=/usr/local/ \
>>
>>     -DCMAKE_MODULE_PATH=$OSSIM_DEV_HOME/cmake/CMakeModules/ \
>>
>>     -DBUILD_GDAL_PLUGIN=OFF \
>>
>>     -DBUILD_MRSID_PLUGIN=OFF \
>>
>>     -DBUILD_PDAL_PLUGIN=OFF \
>>
>>     -DBUILD_KAKADU_PLUGIN=OFF \
>>
>>     -DBUILD_CNES_PLUGIN=OFF \
>>
>>     -DBUILD_POTRACE_PLUGIN=ON \
>>
>>     -DBUILD_REG_PLUGIN=ON
>>
>>
>> RUN make && make install
>>
>>
>> RUN echo /usr/local/lib/ossim/plugins/ >
>> /etc/ld.so.conf.d/ossim-plugins.conf && ldconfig
>>
>>
>> #RUN useradd -ms /bin/bash ossimuser
>>
>> #USER ossimuser
>>
>> #WORKDIR /home/ossimuser
>>
>>
>> # Set up the preferences file
>>
>> RUN echo 'plugin.file1:
>> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so' >
>> ~/ossim_preferences
>>
>> RUN echo 'plugin.file2:
>> /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so' >>
>> ~/ossim_preferences
>>
>> #ENV OSSIM_PREFS_FILE=/home/ossimuser/ossim_preferences
>>
>> ENV OSSIM_PREFS_FILE=/root/ossim_preferences
>>
>>
>>
>> Now for the issue.  I think there is a linking issue which I just can't
>> seem to put my finger on and hoping you can help?
>>
>>
>> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# ossim-info
>> --plugins
>>
>> ossimDynamicLibrary:60  Failed to load library:
>> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so
>>
>> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined symbol:
>> _ZN12ossimRegTool19initProcessingChainEv
>>
>> Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>>
>> DESCRIPTION:
>>
>> Potrace Tool plugin
>>
>>
>> CLASSES SUPPORTED
>>
>>      ossimPotraceTool
>>
>>
>> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# nm -D
>> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so | grep
>> _ZN12ossimRegTool19initProcessingChainEv
>>                  U _ZN12ossimRegTool19initProcessingChainEv
>>
>> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# export
>> LD_DEBUG=files
>> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# ossim-info
>> --plugins
>> 23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
>> dynamically loaded by /usr/local/lib/libossim.so.1 [0]
>> 23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
>> generating link map
>> 23:   dynamic: 0x00007f1f344bed10  base: 0x00007f1f342b4000   size:
>> 0x000000000020b270
>> 23:     entry: 0x00007f1f342b9c80  phdr: 0x00007f1f342b4040  phnum:
>>             7
>> 23:
>> 23: /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: error: symbol
>> lookup error: undefined symbol: _ZN12ossimRegTool19initProcessingChainEv
>> (fatal)
>> 23:
>> 23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
>> destroying link map
>> ossimDynamicLibrary:60  Failed to load library:
>> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so
>> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined symbol:
>> _ZN12ossimRegTool19initProcessingChainEv
>> 23:
>> 23: file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
>> dynamically loaded by /usr/local/lib/libossim.so.1 [0]
>> 23: file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
>> generating link map
>> 23:   dynamic: 0x00007f1f344beca0  base: 0x00007f1f342a1000   size:
>> 0x000000000021e710
>> 23:     entry: 0x00007f1f342a8fc0  phdr: 0x00007f1f342a1040  phnum:
>>             7
>> 23:
>> 23:
>> 23: calling init: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>> 23:
>> 23: opening file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>> [0]; direct_opencount=1
>> 23:
>> Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>> DESCRIPTION:
>> Potrace Tool plugin
>>
>> CLASSES SUPPORTED
>> ossimPotraceTool
>>
>> Thanks for any help you can provide!
>>
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>

Re: [OSSIM] Linking issue on reg plugin

[David B. <db...@gm...>]

Hi Mike,

The ossim-plugins/reg plugin is now very old and unfortunately hasn't 
been worked on in a long time that I know of. I would refer you to Dave 
Hicks' registration work. It was a great start, but also has not been 
worked in a while. I think the registration code works provided you have 
tie points. The autonomous tie point generation / auto reg goal was 
never reached.

I'd start with this doc:

http://download.osgeo.org/ossim/docs/pdfs/GeoCell_Metric_Exploitation__030513.pdf

I think you would want to look at the opencv plugin:

https://github.com/ossimlabs/ossim-plugins/tree/dev/opencv


Take care,
Dave



On 12/20/18 7:00 PM, Mike Finnessy wrote:
> Just saw this older post...bummer.  I don't know if you guys can 
> provide context for why it was retired?
>
> *Re: [OSSIM] (no subject) 
> <https://sourceforge.net/p/ossim/mailman/message/36015211/>*
> From: Oscar Kramer <oscar.kramer@di...> - 2017-08-28 13:15:35
> *Attachments:* image001.png 
> <https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/1/> 
> image002.png 
> <https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/2/> 
> Message as HTML 
> <https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/3/>
> Prakash,
>
> Nearly two years ago we migrated OSSIM 1.8.20 from SVN to git and tagged
> that 1.9. The items to be moved were prioritized by perceived need and some
> packages didn't make it over. One of those was the ossim-plugins/reg. There
> is in fact a different ossim-plugins/reg in github which was intended to
> replace the old one, but that has not materialized.
>
> You are welcome to explore the old reg plugin (containing
> ossimImageCorrelator) here <http://download.osgeo.org/ossim/source/latest/>  <http://download.osgeo.org/ossim/source/latest/%3E>;.
> But keep in mind that the code there is way behind, and was never
> thoroughly tested. It will probably be a nontrivial effort to get that up
> and running for your needs.
>
> Oscar
>
>
> On Wed, Dec 19, 2018 at 7:36 PM Mike Finnessy <mik...@gm... 
> <mailto:mik...@gm...>> wrote:
>
>     HI,
>
>     I'm in need of performing imagery co-registration and came across
>     your product.  I desire to be a first time user, and see if the
>     reg plugin will meet our needs.  It looks like in order to use
>     that particular plugin I need to build rather than using the linux
>     packages that are out there.  I'm currently working on building a
>     docker image pulling from ubuntu:18.04, building and installing
>     opencv (3.2.0), building and installing ossim-core and
>     ossim-plugins.  Right now everything appears to install correctly
>     and I am able to use the ossim core functionality as well as the
>     potrace plugin (which is the only other plugin I have installed. 
>     Here is the build I am using which I shamelessly borrowed from
>     https://github.com/johntut/ossim-gis:
>
>     ENV OSSIM_DEV_HOME=/usr/local/src/ossim
>
>
>     ENV OSSIM_BUILD_DIR=$OSSIM_DEV_HOME/build \
>
>     OSSIM_DEPENDENCIES=/usr
>
>
>     #WORKDIR $OSSIM_DEV_HOME
>
>     RUN git clone https://github.com/ossimlabs/ossim.git
>     $OSSIM_DEV_HOME && \
>
>     cd $OSSIM_DEV_HOME && \
>
>     git checkout tags/Juno-2.6.1
>
>     #git checkout master
>
>     #RUN wget https://github.com/ossimlabs/ossim/archive/Juno-2.6.1.zip
>
>
>     RUN git clone https://github.com/ossimlabs/ossim-plugins.git
>     $OSSIM_DEV_HOME/ossim-plugins && \
>
>     cd $OSSIM_DEV_HOME/ossim-plugins && \
>
>     git checkout tags/Juno-2.6.1
>
>     #git checkout master
>
>     #RUN wget
>
>
>     RUN mkdir $OSSIM_BUILD_DIR
>
>     WORKDIR $OSSIM_BUILD_DIR
>
>
>     # Make and install ossim.
>
>
>     RUN cmake .. \
>
>     -DOSSIM_LIBRARY=$OSSIM_BUILD_DIR/lib/libossim.so \
>
>     -DOSSIM_INCLUDE_DIR=$OSSIM_DEV_HOME/include \
>
>     -DBUILD_OSSIM_TESTS=OFF
>
>
>     RUN make && make install && ldconfig
>
>
>     # Make and install plugins.
>
>
>     RUN mkdir $OSSIM_DEV_HOME/ossim-plugins/build
>
>     WORKDIR $OSSIM_DEV_HOME/ossim-plugins/build
>
>
>     RUN cmake .. \
>
>     -DOSSIM_INSTALL_PREFIX=/usr/local/ \
>
>     -DCMAKE_MODULE_PATH=$OSSIM_DEV_HOME/cmake/CMakeModules/ \
>
>     -DBUILD_GDAL_PLUGIN=OFF \
>
>     -DBUILD_MRSID_PLUGIN=OFF \
>
>     -DBUILD_PDAL_PLUGIN=OFF \
>
>     -DBUILD_KAKADU_PLUGIN=OFF \
>
>     -DBUILD_CNES_PLUGIN=OFF \
>
>     -DBUILD_POTRACE_PLUGIN=ON \
>
>     -DBUILD_REG_PLUGIN=ON
>
>
>     RUN make && make install
>
>
>     RUN echo /usr/local/lib/ossim/plugins/ >
>     /etc/ld.so.conf.d/ossim-plugins.conf && ldconfig
>
>
>     #RUN useradd -ms /bin/bash ossimuser
>
>     #USER ossimuser
>
>     #WORKDIR /home/ossimuser
>
>
>     # Set up the preferences file
>
>     RUNecho 'plugin.file1:
>     /usr/local/lib/ossim/plugins/libossim_reg_plugin.so'>
>     ~/ossim_preferences
>
>     RUNecho 'plugin.file2:
>     /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so'>>
>     ~/ossim_preferences
>
>     #ENV OSSIM_PREFS_FILE=/home/ossimuser/ossim_preferences
>
>     ENV OSSIM_PREFS_FILE=/root/ossim_preferences
>
>
>
>     Now for the issue.  I think there is a linking issue which I just
>     can't seem to put my finger on and hoping you can help?
>
>
>     root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build#
>     ossim-info --plugins
>
>     ossimDynamicLibrary:60 Failed to load library:
>     /usr/local/lib/ossim/plugins/libossim_reg_plugin.so
>
>     /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined
>     symbol: _ZN12ossimRegTool19initProcessingChainEv
>
>     Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>
>     DESCRIPTION:
>
>     Potrace Tool plugin
>
>
>     CLASSES SUPPORTED
>
>      ossimPotraceTool
>
>     root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# nm -D
>     /usr/local/lib/ossim/plugins/libossim_reg_plugin.so | grep
>     _ZN12ossimRegTool19initProcessingChainEv
>                      U _ZN12ossimRegTool19initProcessingChainEv
>
>     root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# export
>     LD_DEBUG=files
>     root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build#
>     ossim-info --plugins
>     23:file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0]; 
>     dynamically loaded by /usr/local/lib/libossim.so.1 [0]
>     23:file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0]; 
>     generating link map
>     23:dynamic: 0x00007f1f344bed10  base: 0x00007f1f342b4000   size:
>     0x000000000020b270
>     23:  entry: 0x00007f1f342b9c80  phdr: 0x00007f1f342b4040  phnum: 
>                     7
>     23:
>     23:/usr/local/lib/ossim/plugins/libossim_reg_plugin.so: error:
>     symbol lookup error: undefined symbol:
>     _ZN12ossimRegTool19initProcessingChainEv (fatal)
>     23:
>     23:file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0]; 
>     destroying link map
>     ossimDynamicLibrary:60  Failed to load library:
>     /usr/local/lib/ossim/plugins/libossim_reg_plugin.so
>     /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined
>     symbol: _ZN12ossimRegTool19initProcessingChainEv
>     23:
>     23:file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>     [0];  dynamically loaded by /usr/local/lib/libossim.so.1 [0]
>     23:file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>     [0];  generating link map
>     23:dynamic: 0x00007f1f344beca0  base: 0x00007f1f342a1000   size:
>     0x000000000021e710
>     23:  entry: 0x00007f1f342a8fc0  phdr: 0x00007f1f342a1040  phnum: 
>                     7
>     23:
>     23:
>     23:calling init:
>     /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>     23:
>     23:opening
>     file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
>     direct_opencount=1
>     23:
>     Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>     DESCRIPTION:
>     Potrace Tool plugin
>
>     CLASSES SUPPORTED
>     ossimPotraceTool
>
>     Thanks for any help you can provide!
>
>
>
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer

Re: [OSSIM] Linking issue on reg plugin

[Mike F. <mik...@gm...>]

Just saw this older post...bummer.  I don't know if you guys can provide
context for why it was retired?

*Re: [OSSIM] (no subject)
<https://sourceforge.net/p/ossim/mailman/message/36015211/>*
From: Oscar Kramer <oscar.kramer@di...> - 2017-08-28 13:15:35
*Attachments:* image001.png
<https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/1/>
 image002.png
<https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/2/>
 Message as HTML
<https://sourceforge.net/p/ossim/mailman/attachment/CAGFB8KPd0RatzJ_TddhUYwH4iYKqHDg1TVk3qv4v%2BAtWw3CnBA%40mail.gmail.com/3/>

Prakash,

Nearly two years ago we migrated OSSIM 1.8.20 from SVN to git and tagged
that 1.9. The items to be moved were prioritized by perceived need and some
packages didn't make it over. One of those was the ossim-plugins/reg. There
is in fact a different ossim-plugins/reg in github which was intended to
replace the old one, but that has not materialized.

You are welcome to explore the old reg plugin (containing
ossimImageCorrelator) here <http://download.osgeo.org/ossim/source/latest/>;.
But keep in mind that the code there is way behind, and was never
thoroughly tested. It will probably be a nontrivial effort to get that up
and running for your needs.

Oscar


On Wed, Dec 19, 2018 at 7:36 PM Mike Finnessy <mik...@gm...>
wrote:

> HI,
>
> I'm in need of performing imagery co-registration and came across your
> product.  I desire to be a first time user, and see if the reg plugin will
> meet our needs.  It looks like in order to use that particular plugin I
> need to build rather than using the linux packages that are out there.  I'm
> currently working on building a docker image pulling from ubuntu:18.04,
> building and installing opencv (3.2.0), building and installing ossim-core
> and ossim-plugins.  Right now everything appears to install correctly and I
> am able to use the ossim core functionality as well as the potrace plugin
> (which is the only other plugin I have installed.  Here is the build I am
> using which I shamelessly borrowed from
> https://github.com/johntut/ossim-gis:
>
> ENV OSSIM_DEV_HOME=/usr/local/src/ossim
>
>
> ENV OSSIM_BUILD_DIR=$OSSIM_DEV_HOME/build \
>
>     OSSIM_DEPENDENCIES=/usr
>
>
> #WORKDIR $OSSIM_DEV_HOME
>
> RUN git clone https://github.com/ossimlabs/ossim.git $OSSIM_DEV_HOME && \
>
>     cd $OSSIM_DEV_HOME && \
>
>     git checkout tags/Juno-2.6.1
>
> #    git checkout master
>
> #RUN wget https://github.com/ossimlabs/ossim/archive/Juno-2.6.1.zip
>
>
> RUN git clone https://github.com/ossimlabs/ossim-plugins.git
> $OSSIM_DEV_HOME/ossim-plugins && \
>
>     cd $OSSIM_DEV_HOME/ossim-plugins && \
>
>     git checkout tags/Juno-2.6.1
>
> #    git checkout master
>
> #RUN wget
>
>
> RUN mkdir $OSSIM_BUILD_DIR
>
> WORKDIR $OSSIM_BUILD_DIR
>
>
> # Make and install ossim.
>
>
> RUN cmake .. \
>
>     -DOSSIM_LIBRARY=$OSSIM_BUILD_DIR/lib/libossim.so \
>
>     -DOSSIM_INCLUDE_DIR=$OSSIM_DEV_HOME/include \
>
>     -DBUILD_OSSIM_TESTS=OFF
>
>
> RUN make && make install && ldconfig
>
>
> # Make and install plugins.
>
>
> RUN mkdir $OSSIM_DEV_HOME/ossim-plugins/build
>
> WORKDIR $OSSIM_DEV_HOME/ossim-plugins/build
>
>
> RUN cmake .. \
>
>     -DOSSIM_INSTALL_PREFIX=/usr/local/ \
>
>     -DCMAKE_MODULE_PATH=$OSSIM_DEV_HOME/cmake/CMakeModules/ \
>
>     -DBUILD_GDAL_PLUGIN=OFF \
>
>     -DBUILD_MRSID_PLUGIN=OFF \
>
>     -DBUILD_PDAL_PLUGIN=OFF \
>
>     -DBUILD_KAKADU_PLUGIN=OFF \
>
>     -DBUILD_CNES_PLUGIN=OFF \
>
>     -DBUILD_POTRACE_PLUGIN=ON \
>
>     -DBUILD_REG_PLUGIN=ON
>
>
> RUN make && make install
>
>
> RUN echo /usr/local/lib/ossim/plugins/ >
> /etc/ld.so.conf.d/ossim-plugins.conf && ldconfig
>
>
> #RUN useradd -ms /bin/bash ossimuser
>
> #USER ossimuser
>
> #WORKDIR /home/ossimuser
>
>
> # Set up the preferences file
>
> RUN echo 'plugin.file1:
> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so' > ~/ossim_preferences
>
> RUN echo 'plugin.file2:
> /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so' >>
> ~/ossim_preferences
>
> #ENV OSSIM_PREFS_FILE=/home/ossimuser/ossim_preferences
>
> ENV OSSIM_PREFS_FILE=/root/ossim_preferences
>
>
>
> Now for the issue.  I think there is a linking issue which I just can't
> seem to put my finger on and hoping you can help?
>
>
> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# ossim-info
> --plugins
>
> ossimDynamicLibrary:60  Failed to load library:
> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so
>
> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined symbol:
> _ZN12ossimRegTool19initProcessingChainEv
>
> Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
>
> DESCRIPTION:
>
> Potrace Tool plugin
>
>
> CLASSES SUPPORTED
>
>      ossimPotraceTool
>
>
> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# nm -D
> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so | grep
> _ZN12ossimRegTool19initProcessingChainEv
>                  U _ZN12ossimRegTool19initProcessingChainEv
>
> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# export
> LD_DEBUG=files
> root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# ossim-info
> --plugins
> 23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
> dynamically loaded by /usr/local/lib/libossim.so.1 [0]
> 23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
> generating link map
> 23:   dynamic: 0x00007f1f344bed10  base: 0x00007f1f342b4000   size:
> 0x000000000020b270
> 23:     entry: 0x00007f1f342b9c80  phdr: 0x00007f1f342b4040  phnum:
>             7
> 23:
> 23: /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: error: symbol
> lookup error: undefined symbol: _ZN12ossimRegTool19initProcessingChainEv
> (fatal)
> 23:
> 23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
> destroying link map
> ossimDynamicLibrary:60  Failed to load library:
> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so
> /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined symbol:
> _ZN12ossimRegTool19initProcessingChainEv
> 23:
> 23: file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
> dynamically loaded by /usr/local/lib/libossim.so.1 [0]
> 23: file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
> generating link map
> 23:   dynamic: 0x00007f1f344beca0  base: 0x00007f1f342a1000   size:
> 0x000000000021e710
> 23:     entry: 0x00007f1f342a8fc0  phdr: 0x00007f1f342a1040  phnum:
>             7
> 23:
> 23:
> 23: calling init: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
> 23:
> 23: opening file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
> [0]; direct_opencount=1
> 23:
> Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
> DESCRIPTION:
> Potrace Tool plugin
>
> CLASSES SUPPORTED
> ossimPotraceTool
>
> Thanks for any help you can provide!
>

[OSSIM] Linking issue on reg plugin

[Mike F. <mik...@gm...>]

HI,

I'm in need of performing imagery co-registration and came across your
product.  I desire to be a first time user, and see if the reg plugin will
meet our needs.  It looks like in order to use that particular plugin I
need to build rather than using the linux packages that are out there.  I'm
currently working on building a docker image pulling from ubuntu:18.04,
building and installing opencv (3.2.0), building and installing ossim-core
and ossim-plugins.  Right now everything appears to install correctly and I
am able to use the ossim core functionality as well as the potrace plugin
(which is the only other plugin I have installed.  Here is the build I am
using which I shamelessly borrowed from https://github.com/johntut/ossim-gis
:

ENV OSSIM_DEV_HOME=/usr/local/src/ossim


ENV OSSIM_BUILD_DIR=$OSSIM_DEV_HOME/build \

    OSSIM_DEPENDENCIES=/usr


#WORKDIR $OSSIM_DEV_HOME

RUN git clone https://github.com/ossimlabs/ossim.git $OSSIM_DEV_HOME && \

    cd $OSSIM_DEV_HOME && \

    git checkout tags/Juno-2.6.1

#    git checkout master

#RUN wget https://github.com/ossimlabs/ossim/archive/Juno-2.6.1.zip


RUN git clone https://github.com/ossimlabs/ossim-plugins.git
$OSSIM_DEV_HOME/ossim-plugins && \

    cd $OSSIM_DEV_HOME/ossim-plugins && \

    git checkout tags/Juno-2.6.1

#    git checkout master

#RUN wget


RUN mkdir $OSSIM_BUILD_DIR

WORKDIR $OSSIM_BUILD_DIR


# Make and install ossim.


RUN cmake .. \

    -DOSSIM_LIBRARY=$OSSIM_BUILD_DIR/lib/libossim.so \

    -DOSSIM_INCLUDE_DIR=$OSSIM_DEV_HOME/include \

    -DBUILD_OSSIM_TESTS=OFF


RUN make && make install && ldconfig


# Make and install plugins.


RUN mkdir $OSSIM_DEV_HOME/ossim-plugins/build

WORKDIR $OSSIM_DEV_HOME/ossim-plugins/build


RUN cmake .. \

    -DOSSIM_INSTALL_PREFIX=/usr/local/ \

    -DCMAKE_MODULE_PATH=$OSSIM_DEV_HOME/cmake/CMakeModules/ \

    -DBUILD_GDAL_PLUGIN=OFF \

    -DBUILD_MRSID_PLUGIN=OFF \

    -DBUILD_PDAL_PLUGIN=OFF \

    -DBUILD_KAKADU_PLUGIN=OFF \

    -DBUILD_CNES_PLUGIN=OFF \

    -DBUILD_POTRACE_PLUGIN=ON \

    -DBUILD_REG_PLUGIN=ON


RUN make && make install


RUN echo /usr/local/lib/ossim/plugins/ >
/etc/ld.so.conf.d/ossim-plugins.conf && ldconfig


#RUN useradd -ms /bin/bash ossimuser

#USER ossimuser

#WORKDIR /home/ossimuser


# Set up the preferences file

RUN echo 'plugin.file1: /usr/local/lib/ossim/plugins/libossim_reg_plugin.so'
> ~/ossim_preferences

RUN echo 'plugin.file2:
/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so' >>
~/ossim_preferences

#ENV OSSIM_PREFS_FILE=/home/ossimuser/ossim_preferences

ENV OSSIM_PREFS_FILE=/root/ossim_preferences



Now for the issue.  I think there is a linking issue which I just can't
seem to put my finger on and hoping you can help?


root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# ossim-info
--plugins

ossimDynamicLibrary:60  Failed to load library:
/usr/local/lib/ossim/plugins/libossim_reg_plugin.so

/usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined symbol:
_ZN12ossimRegTool19initProcessingChainEv

Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so

DESCRIPTION:

Potrace Tool plugin


CLASSES SUPPORTED

     ossimPotraceTool


root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# nm -D
/usr/local/lib/ossim/plugins/libossim_reg_plugin.so | grep
_ZN12ossimRegTool19initProcessingChainEv
                 U _ZN12ossimRegTool19initProcessingChainEv

root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# export
LD_DEBUG=files
root@a6d4309de7b7:/usr/local/src/ossim/ossim-plugins/build# ossim-info
--plugins
23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
dynamically loaded by /usr/local/lib/libossim.so.1 [0]
23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
generating link map
23:   dynamic: 0x00007f1f344bed10  base: 0x00007f1f342b4000   size:
0x000000000020b270
23:     entry: 0x00007f1f342b9c80  phdr: 0x00007f1f342b4040  phnum:
          7
23:
23: /usr/local/lib/ossim/plugins/libossim_reg_plugin.so: error: symbol
lookup error: undefined symbol: _ZN12ossimRegTool19initProcessingChainEv
(fatal)
23:
23: file=/usr/local/lib/ossim/plugins/libossim_reg_plugin.so [0];
destroying link map
ossimDynamicLibrary:60  Failed to load library:
/usr/local/lib/ossim/plugins/libossim_reg_plugin.so
/usr/local/lib/ossim/plugins/libossim_reg_plugin.so: undefined symbol:
_ZN12ossimRegTool19initProcessingChainEv
23:
23: file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
dynamically loaded by /usr/local/lib/libossim.so.1 [0]
23: file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so [0];
generating link map
23:   dynamic: 0x00007f1f344beca0  base: 0x00007f1f342a1000   size:
0x000000000021e710
23:     entry: 0x00007f1f342a8fc0  phdr: 0x00007f1f342a1040  phnum:
          7
23:
23:
23: calling init: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
23:
23: opening file=/usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
[0]; direct_opencount=1
23:
Plugin: /usr/local/lib/ossim/plugins/libossim_potrace_plugin.so
DESCRIPTION:
Potrace Tool plugin

CLASSES SUPPORTED
ossimPotraceTool

Thanks for any help you can provide!

[OSSIM] OSSIM Input Data

[Milechin, D. <mil...@bu...>]

Hello,

I am hoping to get access to the OSSIM input data for 'ossim-batch-tests' program.

Thank you,

Dennis
_________________________________________________________
Dennis Milechin, P.E.
Scientific Programmer/Analyst
Research Computing Services | IS&T | Boston University |
(617)-353-5985 | mil...@bu...<mailto:mil...@bu...> | rcs.bu.edu | he...@sc...<mailto:he...@sc...>

Re: [OSSIM] Weird behaviour when reading tiff files (geographic referencing)

[Roberta R. <rob...@un...>]

Hi Garrett,

now everything works fine!

Thank you again for all the support!!

Cheers,

Roberta
--------------------------------------------------------------------------------
Roberta Ravanelli, *PhD *
Geodesy and Geomatics Division
University of Rome "La Sapienza"
Via Eudossiana, 18 - 00184 Rome Italy
E-mail rob...@un...



Il giorno dom 23 set 2018 alle ore 02:46 Garrett Potts <
gar...@gm...> ha scritto:

> Hello:
>
> Shoot!  I had it still checked out locally and never pushed!   Sorry!
> Try it now
>
>
> Take care
>
> Garrett
>
>
> On Sep 22, 2018, at 5:53 PM, Roberta Ravanelli <
> rob...@un...> wrote:
>
> Thank you again, but now Ossim does not even build:
>
>
> */home/roberta/library_sources/ossim/ossim/src/support_data/ossimGeoTiff.cpp:
> In member function ‘bool ossimGeoTiff::addImageGeometry(ossimKeywordlist&,
> const char*) const’:*
> */home/roberta/library_sources/ossim/ossim/src/support_data/ossimGeoTiff.cpp:1711:26:
> error: assignment of member ‘ossimGeoTiff::theAngularUnits’ in read-only
> object*
> *          theAngularUnits = ANGULAR_DEGREE;*
> [ 59%] Building CXX object
> ossim/src/CMakeFiles/ossim.dir/support_data/ossimRpfFrameFileIndexSubsection.cpp.o
> [ 59%] Building CXX object
> ossim/src/CMakeFiles/ossim.dir/support_data/ossimFfL5.cpp.o
> ossim/src/CMakeFiles/ossim.dir/build.make:20438: set di istruzioni per
> l'obiettivo
> "ossim/src/CMakeFiles/ossim.dir/support_data/ossimGeoTiff.cpp.o" non
> riuscito
> make[2]: ***
> [ossim/src/CMakeFiles/ossim.dir/support_data/ossimGeoTiff.cpp.o] Errore 1
> make[2]: *** Attesa per i processi non terminati....
> CMakeFiles/Makefile2:144: set di istruzioni per l'obiettivo
> "ossim/src/CMakeFiles/ossim.dir/all" non riuscito
> make[1]: *** [ossim/src/CMakeFiles/ossim.dir/all] Errore 2
> Makefile:127: set di istruzioni per l'obiettivo "all" non riuscito
> make: *** [all] Errore 2
>
>
> Bests,
>
> Roberta
>
>
> --------------------------------------------------------------------------------
> Roberta Ravanelli, *PhD *
> Geodesy and Geomatics Division
> University of Rome "La Sapienza"
> Via Eudossiana, 18 - 00184 Rome Italy
> E-mail rob...@un...
>
>
>
> Il giorno sab 22 set 2018 alle ore 22:53 Garrett Potts <
> gar...@gm...> ha scritto:
>
>> Hello:
>>
>> I added a check to see if the angular units is not set then if the model
>> type is geographic then default it to DEGREES.   I just checked in the code.
>>
>>
>> Let me know if that works out
>>
>>
>> Take care
>>
>> Garrett
>>
>>
>> On Sep 22, 2018, at 1:33 PM, Roberta Ravanelli <
>> rob...@un...> wrote:
>>
>> Hi Garrett,
>>
>> the problem occurs with all the SRTM tiles that I have in my pc.
>>
>> I try to explain better my situation: we are trying to resume the
>> development of the OSSIM DATE plugin that Martina has implented during her
>> GSoCs.
>> The bug happens at very beginning of the workflow, when we try to
>> retrieve the heights of the grid points (line 354 of
>> https://github.com/martidi/opencv_dsm/blob/imageStack/apps/ossim-opencv.cpp
>> file).
>>
>> In particular, the program remains stuck within the while loop of the
>> *ossimImageElevationDatabase::createCell* method (line 127 of
>> https://github.com/ossimlabs/ossim/blob/dev/src/elevation/ossimImageElevationDatabase.cpp:
>> for an unknown reason Ossim cannot read the metadata of the SRTM tiles. For
>> instance, you can see my shell output below:
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_37_04.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_39_05.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_40_04.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_59_08.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_22_03.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_42_05.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_39_03.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_38_04.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_38_03.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_40_05.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_39_04.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>>
>> file scansionato
>> /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_37_04.tif
>>
>> WARNING ossimGeoTiff::addImageGeometry:
>>
>> Not coded yet for unit type:  0
>>
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>>
>> and so on forever...
>>
>>
>>
>> Here you can see all the calls that have brought the program to the
>> warning messages:
>>
>> Thread 1 "ossim-DATE-plug" hit Breakpoint 1, 0x00007ffff6988720 in
>> ossimGeoTiff::addImageGeometry(ossimKeywordlist&, char const*) const@plt
>> ()
>>
>>    from /home/roberta/library_sources/ossim/build/lib/libossim.so.1
>>
>> (gdb) bt
>>
>> #0  0x00007ffff6988720 in
>> ossimGeoTiff::addImageGeometry(ossimKeywordlist&, char const*) const@plt
>> ()
>>
>>    from /home/roberta/library_sources/ossim/build/lib/libossim.so.1
>>
>> #1  0x00007ffff704bba7 in ossimTiffProjectionFactory::createProjection (
>>
>>     this=0x6d3860, handler=0x6dcac0)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/projection/ossimTiffProjectionFactory.cpp:99
>>
>> #2  0x00007ffff70f1308 in
>> ossimProjectionFactoryRegistry::createProjection (
>>
>>     this=0x7ffff7b6cbc0
>> <ossimProjectionFactoryRegistry::instance()::inst>,
>>
>>     handler=0x6dcac0)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/projection/ossimProjectionFactoryRegistry.cpp:81
>>
>> #3  0x00007ffff6c6fe50 in ossimImageGeometryFactory::createProjection (
>>
>>     this=0x6d3780, handler=0x6dcac0)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageGeometryFactory.cpp:134
>>
>> #4  0x00007ffff6c6fb37 in ossimImageGeometryFactory::extendGeometry (
>>
>>     this=0x6d3780, handler=0x6dcac0)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageGeometryFactory.cpp:87
>>
>> #5  0x00007ffff6d4a65b in ossimImageGeometryRegistry::extendGeometry (
>>
>>     this=0x6d3720, handler=0x6dcac0)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageGeometryR---Type
>> <return> to continue, or q <return> to quit---
>>
>> egistry.cpp:34
>>
>> #6  0x00007ffff6c0b332 in ossimImageHandler::getImageGeometry
>> (this=0x6dcac0)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageHandler.cpp:712
>>
>> #7  0x00007ffff6bb0e9c in ossimImageElevationHandler::open
>> (this=0x6dc490,
>>
>>     file=...)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationHandler.cpp:76
>>
>> #8  0x00007ffff6ba3de8 in ossimImageElevationDatabase::createCell (
>>
>>     this=0x6d44e0, gpt=...)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationDatabase.cpp:136
>>
>> #9  0x00007ffff6ba4395 in
>> ossimImageElevationDatabase::getOrCreateCellHandler (
>>
>>     this=0x6d44e0, gpt=...)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationDatabase.cpp:258
>>
>> #10 0x00007ffff6ba3b62 in ossimImageElevationDatabase::getHeightAboveMSL (
>>
>>     this=0x6d44e0, gpt=...)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationDatabase.cpp:95
>>
>> #11 0x00007ffff6bb52c2 in ossimElevManager::getHeightAboveMSL (
>>
>>     this=0x7ffff79e3240 <ossimElevManager::instance()::inst>, gpt=...)
>>
>>     at
>> /home/roberta/library_sources/ossim/ossim/src/elevation/ossimElevManager.---Type
>> <return> to continue, or q <return> to quit---
>>
>> cpp:146
>>
>> #12 0x0000000000419b94 in main (argc=10, argv=0x7fffffffdc18)
>>
>>     at
>> /home/roberta/library_sources/ossim/opencv_dsm/apps/ossim-opencv.cpp:354
>>
>>
>>
>> I do not understand what is happening! Maybe now the problems depends on
>> my pc? But this seems strange to me, since before the fix the program was
>> working (reading a wrong georeferencing, but at least it arrived to the
>> end).
>>
>> Thank you for all the help!
>>
>> Roberta
>>
>> --------------------------------------------------------------------------------
>> Roberta Ravanelli, *PhD *
>> Geodesy and Geomatics Division
>> University of Rome "La Sapienza"
>> Via Eudossiana, 18 - 00184 Rome Italy
>> E-mail rob...@un...
>>
>>
>>
>> Il giorno sab 22 set 2018 alle ore 15:12 Garrett Potts <
>> gar...@gm...> ha scritto:
>>
>>> Hello Roberta:
>>>
>>>
>>> Seems that the error message means it couldn’t determine the angular
>>> units.   Could I get a sample or a link from where you downloaded the image?
>>>
>>>
>>> Take care
>>>
>>>
>>> Garrett
>>>
>>>
>>> On Sep 21, 2018, at 3:57 PM, Roberta Ravanelli <
>>> rob...@un...> wrote:
>>>
>>> Thank you very much for the very fast fix, but now I get the following
>>> warning when I call the method
>>> ossimElevManager::instance()->getHeightAboveMSL(world_point);
>>>
>>> WARNING ossimGeoTiff::addImageGeometry:
>>> Not coded yet for unit type:  0
>>>
>>> Any hint?
>>>
>>> Thank you again!
>>>
>>> Roberta
>>>
>>>
>>> --------------------------------------------------------------------------------
>>> Roberta Ravanelli, *PhD *
>>> Geodesy and Geomatics Division
>>> University of Rome "La Sapienza"
>>> Via Eudossiana, 18 - 00184 Rome Italy
>>> E-mail rob...@un...
>>>
>>>
>>>
>>> Il giorno ven 21 set 2018 alle ore 21:00 David Burken <db...@gm...>
>>> ha scritto:
>>>
>>>> Thanks Garrett, look good now...
>>>>
>>>>
>>>> On 9/21/18 1:49 PM, Garrett Potts wrote:
>>>>
>>>> Hello All:
>>>>
>>>>
>>>> The fix has been checked into the dev baseline.
>>>>
>>>>
>>>> Take care
>>>>
>>>> Garrett
>>>>
>>>>
>>>> On Sep 21, 2018, at 9:03 AM, David Burken <db...@gm...> wrote:
>>>>
>>>> Hi Roberta,
>>>>
>>>> Good catch...
>>>>
>>>> Garrett, Roberta is correct, you're not picking up the raster type,
>>>> i.e. point, area and you're off by 1/2 pixel.
>>>>
>>>> $ ossim-info -d srtm_47_04.tif
>>>> tiff.image0.raster_type:  pixel_is_area
>>>> tiff.image0.model_pixel_scale:  """0.000833333333333333
>>>> 0.000833333333333333 0 """
>>>> tiff.image0.model_tie_point:  """0 0 0 49.999583817611 45.0004168845861
>>>> 0 """
>>>>
>>>> // Bad:
>>>> < image0.geometry.tie_point_lat:  45.0004168845861
>>>> < image0.geometry.tie_point_lon:  49.999583817611
>>>> ---
>>>> // Good:
>>>> > image0.geometry.tie_point_lat:  45.0000002179194
>>>> > image0.geometry.tie_point_lon:  50.0000004842777
>>>>
>>>> You can download some samples at:
>>>>
>>>> http://srtm.csi.cgiar.org/SELECTION/listImages.asp
>>>>
>>>> Take care,
>>>> Dave
>>>>
>>>>
>>>>
>>>> On 9/20/18 4:34 PM, Roberta Ravanelli wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I would like to update my Ossim installation from an old version
>>>> installed in an old pc (Ubuntu 12.04, libgeotiff 2, opencv 2) to a newer
>>>> version in a more recent pc (Ubuntu 16.04, libgeotiff 5, opencv 4).
>>>>
>>>> I've actually managed to compile and run Ossim in the newer pc, but
>>>> I've noticed a different behaviour between the two versions when reading
>>>> tiff files.
>>>> Specifically, if the tiff has a geographic georeferencing (lon/lat),
>>>> there is a wrong shift of a half pixel in the coordinate of the upper left
>>>> coordinate (the tiepoint, as it is called in the ossimImageGeometry object).
>>>>
>>>> Below an example on a SRTM v4_1 tile (srtm_39_03.tif):
>>>>
>>>> *OLDER VERSION (right: UL as in the .tfw file)*
>>>> type: ossimImageGeometry
>>>>   No transform defined. Using identity transform.
>>>>   m_projection:
>>>> // ossimMapProjection::print
>>>> type:  ossimEquDistCylProjection
>>>> major_axis:  6378137.000000000000000
>>>> minor_axis:  6356752.314199999906123
>>>> origin_latitude:  0.000000000000000
>>>> central_meridian:  0.000000000000000
>>>> origin: ( 0.000000000000000, 0.000000000000000, 0.000, WGE )
>>>> datum:  WGE
>>>> meters_per_pixel_x:  92.6625433148566
>>>> meters_per_pixel_y:  92.6625433148566
>>>> false_easting_northing: (0,0)
>>>> false_easting_northing_units: meters
>>>> pcs_code: 4326
>>>> tie_point_xy:* (10.0000002905424,50.0000003631855)*
>>>> tie_point_units: degrees
>>>> pixel_scale_xy: (0.000833333333333333,0.000833333333333333)
>>>> pixel_scale_units: degrees
>>>> ossimErrorStatusInterface::print
>>>> theErrorStatus:         0
>>>> theErrorStatus string:  OSSIM_OK
>>>> m_decimationFactors[0]: ( 1.000000000000000, 1.000000000000000 )
>>>> m_imageSize: ( 6001, 6001 )
>>>> m_targetRrds: 0
>>>>
>>>>
>>>> *Newer version (WRONG: UL as in the .hdr file)*
>>>> Type: ossimImageGeometry
>>>>   No transform defined. Using identity transform.
>>>>   m_projection:
>>>> // ossimMapProjection::print
>>>> type:  ossimEquDistCylProjection
>>>> major_axis:  6378137.000000000000000
>>>> minor_axis:  6356752.314199999906123
>>>> origin_latitude:  0.000000000000000
>>>> central_meridian:  0.000000000000000
>>>> origin: ( 0.000000000000000, 0.000000000000000, 0.000, WGE )
>>>> datum:  WGE
>>>> meters_per_pixel_x:  92.6625433148566
>>>> meters_per_pixel_y:  92.6625433148566
>>>> false_easting_northing: (0,0)
>>>> false_easting_northing_units: meters
>>>> pcs_code: 4326
>>>> tie_point_xy: *(9.99958362387572,50.0004170298522)*
>>>> tie_point_units: degrees
>>>> pixel_scale_xy: (0.000833333333333333,0.000833333333333333)
>>>> pixel_scale_units: degrees
>>>> ossimErrorStatusInterface::print
>>>> theErrorStatus:         0
>>>> theErrorStatus string:  OSSIM_OK
>>>> m_decimationFactors[0]: ( 1.000000000000000, 1.000000000000000 )
>>>> m_imageSize: ( 6001, 6001 )
>>>> m_targetRrds: 0
>>>>
>>>>
>>>> I would like to know if such a different behaviour may depend on the
>>>> changes performed in Ossim (for instance, I've noticed that the
>>>> ossimGeoTiff class is changed a lot beetween the two verions) or maybe
>>>> it is caused by the changes in the dependencies (maybe libgeotiff?)
>>>>
>>>> Can you give me a hint, since I have to abandon the oldest pc?
>>>>
>>>> Thank you very much!
>>>>
>>>> Roberta
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Roberta Ravanelli, *PhD *
>>>> Geodesy and Geomatics Division
>>>> University of Rome "La Sapienza"
>>>> Via Eudossiana, 18 - 00184 Rome Italy
>>>> E-mail rob...@un...
>>>>
>>>>
>>>>
>>>> _______________________________________________www.ossim.org
>>>> Ossim-developer mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/ossim-developer
>>>>
>>>>
>>>> _______________________________________________
>>>> www.ossim.org
>>>> Ossim-developer mailing list
>>>> Oss...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>> www.ossim.org
>>> Ossim-developer mailing list
>>> Oss...@li...
>>> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>>>
>>>
>>> _______________________________________________
>> www.ossim.org
>> Ossim-developer mailing list
>> Oss...@li...
>> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>>
>>
>> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer
>
>
>

Re: [OSSIM] Weird behaviour when reading tiff files (geographic referencing)

[Garrett P. <gar...@gm...>]

Hello:

Shoot!  I had it still checked out locally and never pushed!   Sorry!   Try it now


Take care

Garrett


> On Sep 22, 2018, at 5:53 PM, Roberta Ravanelli <rob...@un...> wrote:
> 
> Thank you again, but now Ossim does not even build:
> 
> /home/roberta/library_sources/ossim/ossim/src/support_data/ossimGeoTiff.cpp: In member function ‘bool ossimGeoTiff::addImageGeometry(ossimKeywordlist&, const char*) const’:
> /home/roberta/library_sources/ossim/ossim/src/support_data/ossimGeoTiff.cpp:1711:26: error: assignment of member ‘ossimGeoTiff::theAngularUnits’ in read-only object
>           theAngularUnits = ANGULAR_DEGREE;
> [ 59%] Building CXX object ossim/src/CMakeFiles/ossim.dir/support_data/ossimRpfFrameFileIndexSubsection.cpp.o
> [ 59%] Building CXX object ossim/src/CMakeFiles/ossim.dir/support_data/ossimFfL5.cpp.o
> ossim/src/CMakeFiles/ossim.dir/build.make:20438: set di istruzioni per l'obiettivo "ossim/src/CMakeFiles/ossim.dir/support_data/ossimGeoTiff.cpp.o" non riuscito
> make[2]: *** [ossim/src/CMakeFiles/ossim.dir/support_data/ossimGeoTiff.cpp.o] Errore 1
> make[2]: *** Attesa per i processi non terminati....
> CMakeFiles/Makefile2:144: set di istruzioni per l'obiettivo "ossim/src/CMakeFiles/ossim.dir/all" non riuscito
> make[1]: *** [ossim/src/CMakeFiles/ossim.dir/all] Errore 2
> Makefile:127: set di istruzioni per l'obiettivo "all" non riuscito
> make: *** [all] Errore 2
> 
> 
> Bests,
> 
> Roberta
> 
> --------------------------------------------------------------------------------
> Roberta Ravanelli, PhD 
> Geodesy and Geomatics Division   
> University of Rome "La Sapienza"
> Via Eudossiana, 18 - 00184 Rome Italy
> E-mail rob...@un... <mailto:rob...@un...>
> 
> 
> Il giorno sab 22 set 2018 alle ore 22:53 Garrett Potts <gar...@gm... <mailto:gar...@gm...>> ha scritto:
> Hello:
> 
> I added a check to see if the angular units is not set then if the model type is geographic then default it to DEGREES.   I just checked in the code.
> 
> 
> Let me know if that works out
> 
> 
> Take care
> 
> Garrett
> 
> 
>> On Sep 22, 2018, at 1:33 PM, Roberta Ravanelli <rob...@un... <mailto:rob...@un...>> wrote:
>> 
>> Hi Garrett,
>> 
>> the problem occurs with all the SRTM tiles that I have in my pc.
>> 
>> I try to explain better my situation: we are trying to resume the development of the OSSIM DATE plugin that Martina has implented during her GSoCs.
>> The bug happens at very beginning of the workflow, when we try to retrieve the heights of the grid points (line 354 of https://github.com/martidi/opencv_dsm/blob/imageStack/apps/ossim-opencv.cpp <https://github.com/martidi/opencv_dsm/blob/imageStack/apps/ossim-opencv.cpp> file).
>> 
>> In particular, the program remains stuck within the while loop of the ossimImageElevationDatabase::createCell method (line 127 of  https://github.com/ossimlabs/ossim/blob/dev/src/elevation/ossimImageElevationDatabase.cpp <https://github.com/ossimlabs/ossim/blob/dev/src/elevation/ossimImageElevationDatabase.cpp>: for an unknown reason Ossim cannot read the metadata of the SRTM tiles. For instance, you can see my shell output below:
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_37_04.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_39_05.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_40_04.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_59_08.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_22_03.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_42_05.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_39_03.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_38_04.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_38_03.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_40_05.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_39_04.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> file scansionato /home/roberta/library_sources/ossim/data/elevation/srtm/v4_1/srtm_37_04.tif
>> WARNING ossimGeoTiff::addImageGeometry:
>> Not coded yet for unit type:  0
>> Upper Left and Low Right ( nan, nan, nan, WGE ), ( nan, nan, nan, WGE )
>> 
>> and so on forever...
>> 
>> 
>> Here you can see all the calls that have brought the program to the warning messages:
>> 
>> Thread 1 "ossim-DATE-plug" hit Breakpoint 1, 0x00007ffff6988720 in ossimGeoTiff::addImageGeometry(ossimKeywordlist&, char const*) const@plt ()
>>    from /home/roberta/library_sources/ossim/build/lib/libossim.so.1
>> (gdb) bt
>> #0  0x00007ffff6988720 in ossimGeoTiff::addImageGeometry(ossimKeywordlist&, char const*) const@plt ()
>>    from /home/roberta/library_sources/ossim/build/lib/libossim.so.1
>> #1  0x00007ffff704bba7 in ossimTiffProjectionFactory::createProjection (
>>     this=0x6d3860, handler=0x6dcac0)
>>     at /home/roberta/library_sources/ossim/ossim/src/projection/ossimTiffProjectionFactory.cpp:99
>> #2  0x00007ffff70f1308 in ossimProjectionFactoryRegistry::createProjection (
>>     this=0x7ffff7b6cbc0 <ossimProjectionFactoryRegistry::instance()::inst>, 
>>     handler=0x6dcac0)
>>     at /home/roberta/library_sources/ossim/ossim/src/projection/ossimProjectionFactoryRegistry.cpp:81
>> #3  0x00007ffff6c6fe50 in ossimImageGeometryFactory::createProjection (
>>     this=0x6d3780, handler=0x6dcac0)
>>     at /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageGeometryFactory.cpp:134
>> #4  0x00007ffff6c6fb37 in ossimImageGeometryFactory::extendGeometry (
>>     this=0x6d3780, handler=0x6dcac0)
>>     at /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageGeometryFactory.cpp:87
>> #5  0x00007ffff6d4a65b in ossimImageGeometryRegistry::extendGeometry (
>>     this=0x6d3720, handler=0x6dcac0)
>>     at /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageGeometryR---Type <return> to continue, or q <return> to quit---
>> egistry.cpp:34
>> #6  0x00007ffff6c0b332 in ossimImageHandler::getImageGeometry (this=0x6dcac0)
>>     at /home/roberta/library_sources/ossim/ossim/src/imaging/ossimImageHandler.cpp:712
>> #7  0x00007ffff6bb0e9c in ossimImageElevationHandler::open (this=0x6dc490, 
>>     file=...)
>>     at /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationHandler.cpp:76
>> #8  0x00007ffff6ba3de8 in ossimImageElevationDatabase::createCell (
>>     this=0x6d44e0, gpt=...)
>>     at /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationDatabase.cpp:136
>> #9  0x00007ffff6ba4395 in ossimImageElevationDatabase::getOrCreateCellHandler (
>>     this=0x6d44e0, gpt=...)
>>     at /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationDatabase.cpp:258
>> #10 0x00007ffff6ba3b62 in ossimImageElevationDatabase::getHeightAboveMSL (
>>     this=0x6d44e0, gpt=...)
>>     at /home/roberta/library_sources/ossim/ossim/src/elevation/ossimImageElevationDatabase.cpp:95
>> #11 0x00007ffff6bb52c2 in ossimElevManager::getHeightAboveMSL (
>>     this=0x7ffff79e3240 <ossimElevManager::instance()::inst>, gpt=...)
>>     at /home/roberta/library_sources/ossim/ossim/src/elevation/ossimElevManager.---Type <return> to continue, or q <return> to quit---
>> cpp:146
>> #12 0x0000000000419b94 in main (argc=10, argv=0x7fffffffdc18)
>>     at /home/roberta/library_sources/ossim/opencv_dsm/apps/ossim-opencv.cpp:354
>> 
>> 
>> I do not understand what is happening! Maybe now the problems depends on my pc? But this seems strange to me, since before the fix the program was working (reading a wrong georeferencing, but at least it arrived to the end).
>> 
>> Thank you for all the help!
>> 
>> Roberta
>> --------------------------------------------------------------------------------
>> Roberta Ravanelli, PhD 
>> Geodesy and Geomatics Division   
>> University of Rome "La Sapienza"
>> Via Eudossiana, 18 - 00184 Rome Italy
>> E-mail rob...@un... <mailto:rob...@un...>
>> 
>> 
>> Il giorno sab 22 set 2018 alle ore 15:12 Garrett Potts <gar...@gm... <mailto:gar...@gm...>> ha scritto:
>> Hello Roberta:
>> 
>> 
>> Seems that the error message means it couldn’t determine the angular units.   Could I get a sample or a link from where you downloaded the image?
>> 
>> 
>> Take care
>> 
>> 
>> Garrett
>> 
>> 
>>> On Sep 21, 2018, at 3:57 PM, Roberta Ravanelli <rob...@un... <mailto:rob...@un...>> wrote:
>>> 
>>> Thank you very much for the very fast fix, but now I get the following warning when I call the method ossimElevManager::instance()->getHeightAboveMSL(world_point);
>>> 
>>> WARNING ossimGeoTiff::addImageGeometry:
>>> Not coded yet for unit type:  0
>>> 
>>> Any hint?
>>> 
>>> Thank you again!
>>> 
>>> Roberta
>>> 
>>> --------------------------------------------------------------------------------
>>> Roberta Ravanelli, PhD 
>>> Geodesy and Geomatics Division   
>>> University of Rome "La Sapienza"
>>> Via Eudossiana, 18 - 00184 Rome Italy
>>> E-mail rob...@un... <mailto:rob...@un...>
>>> 
>>> 
>>> Il giorno ven 21 set 2018 alle ore 21:00 David Burken <db...@gm... <mailto:db...@gm...>> ha scritto:
>>> Thanks Garrett, look good now...
>>> 
>>> 
>>> On 9/21/18 1:49 PM, Garrett Potts wrote:
>>>> Hello All:
>>>> 
>>>> 
>>>> The fix has been checked into the dev baseline.
>>>> 
>>>> 
>>>> Take care
>>>> 
>>>> Garrett
>>>> 
>>>> 
>>>>> On Sep 21, 2018, at 9:03 AM, David Burken <db...@gm... <mailto:db...@gm...>> wrote:
>>>>> 
>>>>> Hi Roberta,
>>>>> 
>>>>> Good catch...
>>>>> 
>>>>> Garrett, Roberta is correct, you're not picking up the raster type, i.e. point, area and you're off by 1/2 pixel.
>>>>> 
>>>>> $ ossim-info -d srtm_47_04.tif
>>>>> tiff.image0.raster_type:  pixel_is_area
>>>>> tiff.image0.model_pixel_scale:  """0.000833333333333333 0.000833333333333333 0 """
>>>>> tiff.image0.model_tie_point:  """0 0 0 49.999583817611 45.0004168845861 0 """
>>>>> 
>>>>> // Bad:
>>>>> < image0.geometry.tie_point_lat:  45.0004168845861
>>>>> < image0.geometry.tie_point_lon:  49.999583817611
>>>>> ---
>>>>> // Good:
>>>>> > image0.geometry.tie_point_lat:  45.0000002179194
>>>>> > image0.geometry.tie_point_lon:  50.0000004842777
>>>>> 
>>>>> You can download some samples at:
>>>>> 
>>>>> http://srtm.csi.cgiar.org/SELECTION/listImages.asp <http://srtm.csi.cgiar.org/SELECTION/listImages.asp>
>>>>> 
>>>>> Take care,
>>>>> Dave
>>>>> 
>>>>> 
>>>>> 
>>>>> On 9/20/18 4:34 PM, Roberta Ravanelli wrote:
>>>>>> Hi all, 
>>>>>> 
>>>>>> I would like to update my Ossim installation from an old version installed in an old pc (Ubuntu 12.04, libgeotiff 2, opencv 2) to a newer version in a more recent pc (Ubuntu 16.04, libgeotiff 5, opencv 4).
>>>>>> 
>>>>>> I've actually managed to compile and run Ossim in the newer pc, but I've noticed a different behaviour between the two versions when reading tiff files.
>>>>>> Specifically, if the tiff has a geographic georeferencing (lon/lat), there is a wrong shift of a half pixel in the coordinate of the upper left coordinate (the tiepoint, as it is called in the ossimImageGeometry object).
>>>>>> 
>>>>>> Below an example on a SRTM v4_1 tile (srtm_39_03.tif):
>>>>>> 
>>>>>> OLDER VERSION (right: UL as in the .tfw file)
>>>>>> type: ossimImageGeometry
>>>>>>   No transform defined. Using identity transform.
>>>>>>   m_projection: 
>>>>>> // ossimMapProjection::print
>>>>>> type:  ossimEquDistCylProjection
>>>>>> major_axis:  6378137.000000000000000
>>>>>> minor_axis:  6356752.314199999906123
>>>>>> origin_latitude:  0.000000000000000
>>>>>> central_meridian:  0.000000000000000
>>>>>> origin: ( 0.000000000000000, 0.000000000000000, 0.000, WGE )
>>>>>> datum:  WGE
>>>>>> meters_per_pixel_x:  92.6625433148566
>>>>>> meters_per_pixel_y:  92.6625433148566
>>>>>> false_easting_northing: (0,0)
>>>>>> false_easting_northing_units: meters
>>>>>> pcs_code: 4326
>>>>>> tie_point_xy: (10.0000002905424,50.0000003631855)
>>>>>> tie_point_units: degrees
>>>>>> pixel_scale_xy: (0.000833333333333333,0.000833333333333333)
>>>>>> pixel_scale_units: degrees
>>>>>> ossimErrorStatusInterface::print
>>>>>> theErrorStatus:         0
>>>>>> theErrorStatus string:  OSSIM_OK
>>>>>> m_decimationFactors[0]: ( 1.000000000000000, 1.000000000000000 )
>>>>>> m_imageSize: ( 6001, 6001 )
>>>>>> m_targetRrds: 0
>>>>>> 
>>>>>> 
>>>>>> Newer version (WRONG: UL as in the .hdr file)
>>>>>> Type: ossimImageGeometry
>>>>>>   No transform defined. Using identity transform.
>>>>>>   m_projection: 
>>>>>> // ossimMapProjection::print
>>>>>> type:  ossimEquDistCylProjection
>>>>>> major_axis:  6378137.000000000000000
>>>>>> minor_axis:  6356752.314199999906123
>>>>>> origin_latitude:  0.000000000000000
>>>>>> central_meridian:  0.000000000000000
>>>>>> origin: ( 0.000000000000000, 0.000000000000000, 0.000, WGE )
>>>>>> datum:  WGE
>>>>>> meters_per_pixel_x:  92.6625433148566
>>>>>> meters_per_pixel_y:  92.6625433148566
>>>>>> false_easting_northing: (0,0)
>>>>>> false_easting_northing_units: meters
>>>>>> pcs_code: 4326
>>>>>> tie_point_xy: (9.99958362387572,50.0004170298522)
>>>>>> tie_point_units: degrees
>>>>>> pixel_scale_xy: (0.000833333333333333,0.000833333333333333)
>>>>>> pixel_scale_units: degrees
>>>>>> ossimErrorStatusInterface::print
>>>>>> theErrorStatus:         0
>>>>>> theErrorStatus string:  OSSIM_OK
>>>>>> m_decimationFactors[0]: ( 1.000000000000000, 1.000000000000000 )
>>>>>> m_imageSize: ( 6001, 6001 )
>>>>>> m_targetRrds: 0
>>>>>> 
>>>>>> 
>>>>>> I would like to know if such a different behaviour may depend on the changes performed in Ossim (for instance, I've noticed that the ossimGeoTiff class is changed a lot beetween the two verions) or maybe it is caused by the changes in the dependencies (maybe libgeotiff?)
>>>>>> 
>>>>>> Can you give me a hint, since I have to abandon the oldest pc?
>>>>>> 
>>>>>> Thank you very much!
>>>>>> 
>>>>>> Roberta
>>>>>> 
>>>>>> --------------------------------------------------------------------------------
>>>>>> Roberta Ravanelli, PhD 
>>>>>> Geodesy and Geomatics Division   
>>>>>> University of Rome "La Sapienza"
>>>>>> Via Eudossiana, 18 - 00184 Rome Italy
>>>>>> E-mail rob...@un... <mailto:rob...@un...>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> www.ossim.org <http://www.ossim.org/>
>>>>>> Ossim-developer mailing list
>>>>>> Oss...@li... <mailto:Oss...@li...>
>>>>>> https://lists.sourceforge.net/lists/listinfo/ossim-developer <https://lists.sourceforge.net/lists/listinfo/ossim-developer>
>>>>> 
>>>>> _______________________________________________
>>>>> www.ossim.org <http://www.ossim.org/>
>>>>> Ossim-developer mailing list
>>>>> Oss...@li... <mailto:Oss...@li...>
>>>>> https://lists.sourceforge.net/lists/listinfo/ossim-developer <https://lists.sourceforge.net/lists/listinfo/ossim-developer>
>>>> 
>>> 
>>> _______________________________________________
>>> www.ossim.org <http://www.ossim.org/>
>>> Ossim-developer mailing list
>>> Oss...@li... <mailto:Oss...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/ossim-developer <https://lists.sourceforge.net/lists/listinfo/ossim-developer>
>> 
>> _______________________________________________
>> www.ossim.org <http://www.ossim.org/>
>> Ossim-developer mailing list
>> Oss...@li... <mailto:Oss...@li...>
>> https://lists.sourceforge.net/lists/listinfo/ossim-developer <https://lists.sourceforge.net/lists/listinfo/ossim-developer>
> 
> _______________________________________________
> www.ossim.org
> Ossim-developer mailing list
> Oss...@li...
> https://lists.sourceforge.net/lists/listinfo/ossim-developer