You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(204) |
Jul
(85) |
Aug
(211) |
Sep
(145) |
Oct
(41) |
Nov
(114) |
Dec
(142) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(188) |
Feb
(98) |
Mar
(69) |
Apr
(72) |
May
(93) |
Jun
(119) |
Jul
(129) |
Aug
(80) |
Sep
(110) |
Oct
(72) |
Nov
(85) |
Dec
(145) |
2007 |
Jan
(246) |
Feb
(89) |
Mar
(105) |
Apr
(94) |
May
(116) |
Jun
(248) |
Jul
(110) |
Aug
(144) |
Sep
(118) |
Oct
(92) |
Nov
(96) |
Dec
(168) |
2008 |
Jan
(100) |
Feb
(86) |
Mar
(92) |
Apr
(145) |
May
(71) |
Jun
(122) |
Jul
(97) |
Aug
(90) |
Sep
(76) |
Oct
(54) |
Nov
(51) |
Dec
(44) |
2009 |
Jan
(55) |
Feb
(38) |
Mar
(86) |
Apr
(123) |
May
(111) |
Jun
(116) |
Jul
(107) |
Aug
(107) |
Sep
(86) |
Oct
(54) |
Nov
(63) |
Dec
(78) |
2010 |
Jan
(103) |
Feb
(76) |
Mar
(117) |
Apr
(218) |
May
(106) |
Jun
(170) |
Jul
(77) |
Aug
(61) |
Sep
(69) |
Oct
(109) |
Nov
(67) |
Dec
(135) |
2011 |
Jan
(87) |
Feb
(49) |
Mar
(43) |
Apr
(77) |
May
(85) |
Jun
(81) |
Jul
(89) |
Aug
(109) |
Sep
(56) |
Oct
(96) |
Nov
(81) |
Dec
(41) |
2012 |
Jan
(84) |
Feb
(20) |
Mar
(70) |
Apr
(46) |
May
(34) |
Jun
(65) |
Jul
(50) |
Aug
(19) |
Sep
(20) |
Oct
(40) |
Nov
(35) |
Dec
(91) |
2013 |
Jan
(47) |
Feb
(95) |
Mar
(61) |
Apr
(40) |
May
(32) |
Jun
(30) |
Jul
(73) |
Aug
(52) |
Sep
(21) |
Oct
(24) |
Nov
(20) |
Dec
(29) |
2014 |
Jan
(9) |
Feb
(48) |
Mar
(13) |
Apr
|
May
(34) |
Jun
(31) |
Jul
(46) |
Aug
(21) |
Sep
(7) |
Oct
(5) |
Nov
(9) |
Dec
(21) |
2015 |
Jan
(14) |
Feb
(10) |
Mar
(47) |
Apr
(39) |
May
(23) |
Jun
(15) |
Jul
(17) |
Aug
(12) |
Sep
(15) |
Oct
(15) |
Nov
(30) |
Dec
(11) |
2016 |
Jan
|
Feb
(1) |
Mar
(39) |
Apr
(6) |
May
(12) |
Jun
(10) |
Jul
(16) |
Aug
(13) |
Sep
(7) |
Oct
(3) |
Nov
(4) |
Dec
(2) |
2017 |
Jan
(7) |
Feb
(5) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(7) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
|
2018 |
Jan
(3) |
Feb
(6) |
Mar
(3) |
Apr
|
May
(14) |
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(13) |
Oct
|
Nov
|
Dec
(6) |
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Roberta R. <rob...@un...> - 2018-09-22 21:54:13
|
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 > > > |
From: Garrett P. <gar...@gm...> - 2018-09-22 20:54:16
|
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... > https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: Roberta R. <rob...@un...> - 2018-09-22 18:04:50
|
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 > > > |
From: Garrett P. <gar...@gm...> - 2018-09-22 13:12:51
|
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... > https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: Roberta R. <rob...@un...> - 2018-09-21 20:28:36
|
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 > > > > |
From: David B. <db...@gm...> - 2018-09-21 19:00:26
|
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 >> >> 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 >>> Ossim-developer mailing list >>> Oss...@li... >>> https://lists.sourceforge.net/lists/listinfo/ossim-developer >> >> _______________________________________________ >> www.ossim.org <http://www.ossim.org> >> Ossim-developer mailing list >> Oss...@li... >> https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: Garrett P. <gar...@gm...> - 2018-09-21 17:49:38
|
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 <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 > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: Garrett P. <gar...@gm...> - 2018-09-21 14:27:49
|
Hello Dave: Cool! Will look at it and add a bug ticket Thank you 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 <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 > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: David B. <db...@gm...> - 2018-09-21 13:03:47
|
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... > <mailto:rob...@un...> > > > > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: Roberta R. <rob...@un...> - 2018-09-20 21:04:23
|
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... |
From: rachmat m. <mau...@gm...> - 2018-09-02 08:10:57
|
I personally not activate jpeg12 plugin but somehow it appears there. Plugins that i change to 'ON' are : Gdal, geopdf, cnes, hdf5, opencv, potrace, sqlite, webplugin On Sat, 1 Sep 2018, 05:06 Oscar Kramer, <osc...@ya...> wrote: > Do you need that specific plugin? I have never built it. I just tried and > got the same error. Apparently I have never enabled the build for that > plugin. I couldn't find the library using google either. I suggest simply > setting an environment variable (or variable in your cmake build script) > called BUILD_JPEG12_PLUGIN=OFF and rerun you cmake command. Actually, > that should have been the default so maybe you explicitly set it to "ON"? > > Oscar > > On Friday, August 31, 2018, 4:28:23 PM EDT, rachmat maulana < > mau...@gm...> wrote: > > > Yes i have read it, the thing is i dont know how to install jpeg12 sdk in > my system > > On Fri, 31 Aug 2018, 22:24 Oscar Kramer, <osc...@ya...> wrote: > > Did you see the response I gave to Raniero last year? You need the JPEG12 > SDK installed on your system if you need that plugin. > On Friday, August 31, 2018, 11:18:43 AM EDT, maulanarachmat < > Mau...@gm...> wrote: > > > I have the same problem as this, have you figure out how to solve this? > thank > you > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > > |
From: Oscar K. <osc...@ya...> - 2018-08-31 22:06:15
|
Do you need that specific plugin? I have never built it. I just tried and got the same error. Apparently I have never enabled the build for that plugin. I couldn't find the library using google either. I suggest simply setting an environment variable (or variable in your cmake build script) called BUILD_JPEG12_PLUGIN=OFF and rerun you cmake command. Actually, that should have been the default so maybe you explicitly set it to "ON"? Oscar On Friday, August 31, 2018, 4:28:23 PM EDT, rachmat maulana <mau...@gm...> wrote: Yes i have read it, the thing is i dont know how to install jpeg12 sdk in my system On Fri, 31 Aug 2018, 22:24 Oscar Kramer, <osc...@ya...> wrote: Did you see the response I gave to Raniero last year? You need the JPEG12 SDK installed on your system if you need that plugin. On Friday, August 31, 2018, 11:18:43 AM EDT, maulanarachmat <Mau...@gm...> wrote: I have the same problem as this, have you figure out how to solve this? thank you -- Sent from: http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ www.ossim.org Ossim-developer mailing list Oss...@li... https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: rachmat m. <mau...@gm...> - 2018-08-31 20:28:30
|
Yes i have read it, the thing is i dont know how to install jpeg12 sdk in my system On Fri, 31 Aug 2018, 22:24 Oscar Kramer, <osc...@ya...> wrote: > Did you see the response I gave to Raniero last year? You need the JPEG12 > SDK installed on your system if you need that plugin. > On Friday, August 31, 2018, 11:18:43 AM EDT, maulanarachmat < > Mau...@gm...> wrote: > > > I have the same problem as this, have you figure out how to solve this? > thank > you > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: Oscar K. <osc...@ya...> - 2018-08-31 15:24:11
|
Did you see the response I gave to Raniero last year? You need the JPEG12 SDK installed on your system if you need that plugin. On Friday, August 31, 2018, 11:18:43 AM EDT, maulanarachmat <Mau...@gm...> wrote: I have the same problem as this, have you figure out how to solve this? thank you -- Sent from: http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ www.ossim.org Ossim-developer mailing list Oss...@li... https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: maulanarachmat <Mau...@gm...> - 2018-08-31 03:45:05
|
I have the same problem as this, have you figure out how to solve this? thank you -- Sent from: http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html |
From: David B. <db...@gm...> - 2018-07-31 11:31:57
|
Hi, That's not a standard DTED layout and that would be your issue. Once you move to correct tree structure you should be good. Typical DTED tree: $(OSSIM_DATA)/elevation/dted/level2/e114/n22.dt2 $(OSSIM_DATA)/elevation/dted/level2/e121/n29.dt2 $(OSSIM_DATA)/elevation/dted/level2/e030/n46.dt2 You should be able to do "ossim-info -d -i -p n46_e030_1arc_v3.dt2 // There is some documentation here: https://trac.osgeo.org/ossim/wiki/ossimElevationSetup // The template is more current: // I've added support for "terraform"(w081n27_TFRM.dt2) in a single directory. https://github.com/ossimlabs/ossim/blob/dev/share/ossim/templates/ossim_preferences_template Hope that helps, Dave On 07/30/2018 12:05 PM, temerson wrote: > Hello Dave, > > I'm new to ossim and have been going through the code. After reading through > the associated instructions on elevation setup and reading through this > thread, I continue to have problems getting the elevation files to be > recognized. Most likely I'm doing something wrong, but could sure use a > couple of tips. The following files have been downloaded from the USGS into > my > > $(OSSIM_DATA)/elevation/dted/level2 directory. > > n22_e114_1arc_v3.dt2 n29_e121_1arc_v3.dt2 n46_e030_1arc_v3.dt2 > > When trying to run the ossim-info command, I get the results with tracing > and a few print statements I put in. Thank you for any guidance on what I'm > doing wrong. > > > > ossim-info -P ossim_preferences_template -T ossim --height 46.4880345 > 30.7509579 > > DEBUG ossimInit::initializeElevation(): Entered... > DEBUG: ossimGeoidManager::loadState(), entering... > ossimGeoidEgm96::open Entered... > ossimGeoidEgm96::open Grid > file:/home/ubuntu/temerson/src/Debug/share/ossim/geoids/egm96.grd > Opened geoid grid: > /home/ubuntu/temerson/src/Debug/share/ossim/geoids/egm96.grd > DEBUG: ossimGeoidManager::loadState() > Added geoid egm 96: > /home/ubuntu/temerson/src/Debug/share/ossim/geoids/egm96.grd > DEBUG: ossimGeoidManager::loadState(), returning... > DEBUG ossimElevSource::ossimElevSource: entering... > DEBUG: > theComputeStatsFlag: false > DEBUG ossimElevSource::ossimElevSource: returning... > DEBUG ossimElevManager::loadState: Entered... > DEBUG ossimElevManager::loadState: > Looking for key: elevation_manager.elevation_source0 > DEBUG ossimElevSource::ossimElevSource: entering... > DEBUG: > theComputeStatsFlag: false > DEBUG ossimElevSource::ossimElevSource: returning... > TCE: ossimDtedElevationDatabase::loadState Entering > TCE: ossimDtedElevationDatabase::inside if > TCE: ossimDtedElevationDatabase::inside 2 if > TCE: ossimDtedElevationDatabase:: before result > ossimDtedElevationDatabase::open entered ... > dir: /home/ubuntu/temerson/workflow/elevation/dted/level2 > ossimDtedElevationDatabase::open result:true > DEBUG ossimElevManager::loadState: > adding elevation database: ossimDtedElevationDatabase: > /home/ubuntu/temerson/workflow/elevation/dted/level2 > DEBUG ossimInit::initializeElevation(): leaving... > ossim preferences file: ossim_preferences_template > Version: 1.9.0 20180724 > ossimInit::initialize(parser): leaving... > ossimInfo::initialize(ossimArgumentParser&) entered... > m_kwl: > height: (46.4880345,30.7509579,0,WGE) > > ossimInfo::initialize(ossimArgumentParser&) exit result = true > ossimInfo::execute() entered... > Map size: 1 > TCE: getHeightAboveMSL: Entering > TCE: getHeightAboveMSL: After isSourceEnabled > TCE: getHeightAboveMSL: inside else > TCE: getOrCreateCellHandler latd=46.488034, lond=30.750958, height=0.000000 > TCE: getOrCreateCellHandler 2 result.valid=0 > TCE: getHeightAboveMSL: height = -nan > TCE: getHeightAboveMSL: Entering > TCE: getHeightAboveMSL: After isSourceEnabled > TCE: getHeightAboveMSL: inside else > TCE: getOrCreateCellHandler latd=46.488034, lond=30.750958, height=0.000000 > TCE: getOrCreateCellHandler 1 result.valid=0 > TCE: getHeightAboveMSL: height = -nan > TCE: getHeightAboveEllipsoid: height = -nan > Did not find cell for point: ( 46.488034499999998, 30.750957900000000, > 0.000, WGE ) > MSL to ellipsoid delta: nan > Height above MSL: nan > Height above ellipsoid: nan > Geoid value: 27.646661040072836 > KEY_COUNT: 1 > consumedKeys: 1 > ossimInfo::execute() exited... > > > > > > -- > Sent from: http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: temerson <tem...@di...> - 2018-07-30 16:05:12
|
Hello Dave, I'm new to ossim and have been going through the code. After reading through the associated instructions on elevation setup and reading through this thread, I continue to have problems getting the elevation files to be recognized. Most likely I'm doing something wrong, but could sure use a couple of tips. The following files have been downloaded from the USGS into my $(OSSIM_DATA)/elevation/dted/level2 directory. n22_e114_1arc_v3.dt2 n29_e121_1arc_v3.dt2 n46_e030_1arc_v3.dt2 When trying to run the ossim-info command, I get the results with tracing and a few print statements I put in. Thank you for any guidance on what I'm doing wrong. ossim-info -P ossim_preferences_template -T ossim --height 46.4880345 30.7509579 DEBUG ossimInit::initializeElevation(): Entered... DEBUG: ossimGeoidManager::loadState(), entering... ossimGeoidEgm96::open Entered... ossimGeoidEgm96::open Grid file:/home/ubuntu/temerson/src/Debug/share/ossim/geoids/egm96.grd Opened geoid grid: /home/ubuntu/temerson/src/Debug/share/ossim/geoids/egm96.grd DEBUG: ossimGeoidManager::loadState() Added geoid egm 96: /home/ubuntu/temerson/src/Debug/share/ossim/geoids/egm96.grd DEBUG: ossimGeoidManager::loadState(), returning... DEBUG ossimElevSource::ossimElevSource: entering... DEBUG: theComputeStatsFlag: false DEBUG ossimElevSource::ossimElevSource: returning... DEBUG ossimElevManager::loadState: Entered... DEBUG ossimElevManager::loadState: Looking for key: elevation_manager.elevation_source0 DEBUG ossimElevSource::ossimElevSource: entering... DEBUG: theComputeStatsFlag: false DEBUG ossimElevSource::ossimElevSource: returning... TCE: ossimDtedElevationDatabase::loadState Entering TCE: ossimDtedElevationDatabase::inside if TCE: ossimDtedElevationDatabase::inside 2 if TCE: ossimDtedElevationDatabase:: before result ossimDtedElevationDatabase::open entered ... dir: /home/ubuntu/temerson/workflow/elevation/dted/level2 ossimDtedElevationDatabase::open result:true DEBUG ossimElevManager::loadState: adding elevation database: ossimDtedElevationDatabase: /home/ubuntu/temerson/workflow/elevation/dted/level2 DEBUG ossimInit::initializeElevation(): leaving... ossim preferences file: ossim_preferences_template Version: 1.9.0 20180724 ossimInit::initialize(parser): leaving... ossimInfo::initialize(ossimArgumentParser&) entered... m_kwl: height: (46.4880345,30.7509579,0,WGE) ossimInfo::initialize(ossimArgumentParser&) exit result = true ossimInfo::execute() entered... Map size: 1 TCE: getHeightAboveMSL: Entering TCE: getHeightAboveMSL: After isSourceEnabled TCE: getHeightAboveMSL: inside else TCE: getOrCreateCellHandler latd=46.488034, lond=30.750958, height=0.000000 TCE: getOrCreateCellHandler 2 result.valid=0 TCE: getHeightAboveMSL: height = -nan TCE: getHeightAboveMSL: Entering TCE: getHeightAboveMSL: After isSourceEnabled TCE: getHeightAboveMSL: inside else TCE: getOrCreateCellHandler latd=46.488034, lond=30.750958, height=0.000000 TCE: getOrCreateCellHandler 1 result.valid=0 TCE: getHeightAboveMSL: height = -nan TCE: getHeightAboveEllipsoid: height = -nan Did not find cell for point: ( 46.488034499999998, 30.750957900000000, 0.000, WGE ) MSL to ellipsoid delta: nan Height above MSL: nan Height above ellipsoid: nan Geoid value: 27.646661040072836 KEY_COUNT: 1 consumedKeys: 1 ossimInfo::execute() exited... -- Sent from: http://osgeo-org.1560.x6.nabble.com/Ossim-developer-f3764496.html |
From: David B. <db...@gm...> - 2018-07-10 12:09:16
|
Not sure. I don't think the name matters. I have to head in and will check back tonight. I think the order was: - Oscar renamed the method. - You reverted the info code. I have to run. Talk to you later, Dave On Tue, Jul 10, 2018 at 6:30 AM, Garrett Potts <gar...@gm...> wrote: > Hello Dave: > > Was wondering that too. Should we replace the method with the one you > gave a link for? > > > Take care > > Garrett > > > On Jul 10, 2018, at 5:18 AM, Oscar Kramer via Ossim-developer < > oss...@li...> wrote: > > Dave, > > What about the ossimKeywordlist::toJson() method that is there now? > > > On Monday, July 9, 2018, 6:31:29 PM EDT, David Burken <db...@gm...> > wrote: > > > Hi guys, > > The ossimKeywordlist::writeJsonToStream() was in a pull request I > submitted that got merged into dev but then reverted. It might be too hard > to resurrect it at this point. > > // It's in this branch but it's hard to follow now as it has commits post > the pull request. > > https://github.com/ossimlabs/ossim/tree/drb-20171108 > > // This has the json method: > https://github.com/ossimlabs/ossim/blob/2b8ba787a4f375e4e40e6eac722dca > e309fb4054/src/base/ossimKeywordlist.cpp > > Take care, > Dave > > > > On Mon, Jul 9, 2018 at 10:31 AM, Oscar Kramer <oscar.kramer@ > radiantsolutions.com> wrote: > > JR, > > I'm forwarding your email to the list as this is something we need working > in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() > method recently. The fact that you are getting a "method not found" error > at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. > Did you build OSSIM from source? Do you see that method in > ossimKeywordlist.cpp? > > Whether it actually works or not, I don't know. I let Dave defend that... > > Oscar > > > > <http://www.radiantsolutions.com/> > > Oscar L Kramer > Senior Software Engineer > +1.321.821.1139 office > oscar.kramer@radiantsolutions. com <osc...@ra...> > > On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm...> > wrote: > > Hey JR: > > Been on vacation. Just got back today. Will look at your information > this week. > > > Take care > > Garrett > > > On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Raul.Marquez@radiantsolutions > .com <Rau...@ra...>> wrote: > > Hey guys, > > Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist > in JSON form and having some issues. Can you let me know if I’m doing > anything wrong? Pretty much giving it a few key,value pairs, initializing > it and calling getImageInfo. I get back the kwl and I can transform it > into a string with strdup but I want it in JSON format. I noticed that it > has a toJSON method but I keep getting a no matching function or call for > it. DISCLAIMER: I suck at c++ > > Any help is much appreciated. > > -JR > > > > std::string key; > std::string value; > std::string value2; > ossimKeywordlist kwl; > > key = "build_date"; > value = "true"; > kwl.addPair( key, value ); > > key = "image_file"; > value2 = "/home/rmarquez/Downloads/imag es/17MAR20054817-P1BS-05659936 > 2010_01_P004.NTF"; > kwl.addPair( key, value2 ); > > key = "geometry_info"; > kwl.addPair( key, value ); > > key = "image_info"; > kwl.addPair( key, value ); > > key = "metadata"; > kwl.addPair( key, value ); > > // Make the info object. > ossimInfo* oi = new ossimInfo(); > > // Pass options in: > ossimTool* ot = dynamic_cast<ossimTool*>(oi); > if ( ot ) > { > ot->initialize( kwl ); > } > > oi->getImageInfo( "/home/rmarquez/Downloads/imag > es/17MAR20054817-P1BS-05659936 2010_01_P004.NTF", false, false, false, > true, false, false, kwl); > > > //const char* val = strdup(kwl.toString()); > > std::ostream os( NULL ); > const std::string rootTag="info"; > cout << "TEST: " << kwl.toJSON(&os,&rootTag); > > > > > <image001.png> <http://www.radiantsolutions.com/> > *Raul Marquez Jr* > Software Developer | OTD > 571-721-3593 office > Raul.Marquez@radiantsolutions. com <Rau...@ra...> > <image002.png> <https://twitter.com/radiant_maxar> <image003.png> > <https://www.linkedin.com/company/radiant-solutions/> > > > > This electronic communication and any attachments may contain confidential > and proprietary information of Radiant Solutions, Inc. If you are not the > intended recipient, or an agent or employee responsible for delivering this > communication to the intended recipient, or if you have received this > communication in error, please do not print, copy, retransmit, disseminate > or otherwise use the information. Please indicate to the sender that you > have received this communication in error, and delete the copy you received. > > > Radiant Solutions reserves the right to monitor any electronic > communication sent or received by its employees, agents or representatives. > > > > > ------------------------------ ------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ______________________________ _________________ > www.ossim.org > Ossim-developer mailing list > Ossim-developer@lists. sourceforge.net > <Oss...@li...> > https://lists.sourceforge.net/ lists/listinfo/ossim-developer > <https://lists.sourceforge.net/lists/listinfo/ossim-developer> > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > > > |
From: David B. <db...@gm...> - 2018-07-10 11:28:50
|
I remember now you renamed that to be consistent with your json code. It looks the same I think. In the info code you should be able to do format: json. I think that got merged out... On Tue, Jul 10, 2018 at 5:18 AM, Oscar Kramer <osc...@ya...> wrote: > Dave, > > What about the ossimKeywordlist::toJson() method that is there now? > > > On Monday, July 9, 2018, 6:31:29 PM EDT, David Burken <db...@gm...> > wrote: > > > Hi guys, > > The ossimKeywordlist::writeJsonToStream() was in a pull request I > submitted that got merged into dev but then reverted. It might be too hard > to resurrect it at this point. > > // It's in this branch but it's hard to follow now as it has commits post > the pull request. > > https://github.com/ossimlabs/ossim/tree/drb-20171108 > > // This has the json method: > https://github.com/ossimlabs/ossim/blob/2b8ba787a4f375e4e40e6eac722dca > e309fb4054/src/base/ossimKeywordlist.cpp > > Take care, > Dave > > > > On Mon, Jul 9, 2018 at 10:31 AM, Oscar Kramer <oscar.kramer@ > radiantsolutions.com> wrote: > > JR, > > I'm forwarding your email to the list as this is something we need working > in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() > method recently. The fact that you are getting a "method not found" error > at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. > Did you build OSSIM from source? Do you see that method in > ossimKeywordlist.cpp? > > Whether it actually works or not, I don't know. I let Dave defend that... > > Oscar > > > > <http://www.radiantsolutions.com/> > > Oscar L Kramer > Senior Software Engineer > +1.321.821.1139 office > oscar.kramer@radiantsolutions. com <osc...@ra...> > > On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm...> > wrote: > > Hey JR: > > Been on vacation. Just got back today. Will look at your information > this week. > > > Take care > > Garrett > > > On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Raul.Marquez@radiantsolutions > .com <Rau...@ra...>> wrote: > > Hey guys, > > Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist > in JSON form and having some issues. Can you let me know if I’m doing > anything wrong? Pretty much giving it a few key,value pairs, initializing > it and calling getImageInfo. I get back the kwl and I can transform it > into a string with strdup but I want it in JSON format. I noticed that it > has a toJSON method but I keep getting a no matching function or call for > it. DISCLAIMER: I suck at c++ > > Any help is much appreciated. > > -JR > > > > std::string key; > std::string value; > std::string value2; > ossimKeywordlist kwl; > > key = "build_date"; > value = "true"; > kwl.addPair( key, value ); > > key = "image_file"; > value2 = "/home/rmarquez/Downloads/imag es/17MAR20054817-P1BS-05659936 > 2010_01_P004.NTF"; > kwl.addPair( key, value2 ); > > key = "geometry_info"; > kwl.addPair( key, value ); > > key = "image_info"; > kwl.addPair( key, value ); > > key = "metadata"; > kwl.addPair( key, value ); > > // Make the info object. > ossimInfo* oi = new ossimInfo(); > > // Pass options in: > ossimTool* ot = dynamic_cast<ossimTool*>(oi); > if ( ot ) > { > ot->initialize( kwl ); > } > > oi->getImageInfo( "/home/rmarquez/Downloads/imag > es/17MAR20054817-P1BS-05659936 2010_01_P004.NTF", false, false, false, > true, false, false, kwl); > > > //const char* val = strdup(kwl.toString()); > > std::ostream os( NULL ); > const std::string rootTag="info"; > cout << "TEST: " << kwl.toJSON(&os,&rootTag); > > > > > <image001.png> <http://www.radiantsolutions.com/> > *Raul Marquez Jr* > Software Developer | OTD > 571-721-3593 office > Raul.Marquez@radiantsolutions. com <Rau...@ra...> > <image002.png> <https://twitter.com/radiant_maxar> <image003.png> > <https://www.linkedin.com/company/radiant-solutions/> > > > > This electronic communication and any attachments may contain confidential > and proprietary information of Radiant Solutions, Inc. If you are not the > intended recipient, or an agent or employee responsible for delivering this > communication to the intended recipient, or if you have received this > communication in error, please do not print, copy, retransmit, disseminate > or otherwise use the information. Please indicate to the sender that you > have received this communication in error, and delete the copy you received. > > > Radiant Solutions reserves the right to monitor any electronic > communication sent or received by its employees, agents or representatives. > > > > > ------------------------------ ------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ______________________________ _________________ > www.ossim.org > Ossim-developer mailing list > Ossim-developer@lists. sourceforge.net > <Oss...@li...> > https://lists.sourceforge.net/ lists/listinfo/ossim-developer > <https://lists.sourceforge.net/lists/listinfo/ossim-developer> > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: Garrett P. <gar...@gm...> - 2018-07-10 10:31:06
|
Hello Dave: Was wondering that too. Should we replace the method with the one you gave a link for? Take care Garrett > On Jul 10, 2018, at 5:18 AM, Oscar Kramer via Ossim-developer <oss...@li...> wrote: > > Dave, > > What about the ossimKeywordlist::toJson() method that is there now? > > > On Monday, July 9, 2018, 6:31:29 PM EDT, David Burken <db...@gm...> wrote: > > > Hi guys, > > The ossimKeywordlist::writeJsonToStream() was in a pull request I submitted that got merged into dev but then reverted. It might be too hard to resurrect it at this point. > > // It's in this branch but it's hard to follow now as it has commits post the pull request. > > https://github.com/ossimlabs/ossim/tree/drb-20171108 <https://github.com/ossimlabs/ossim/tree/drb-20171108> > > // This has the json method: > https://github.com/ossimlabs/ossim/blob/2b8ba787a4f375e4e40e6eac722dcae309fb4054/src/base/ossimKeywordlist.cpp <https://github.com/ossimlabs/ossim/blob/2b8ba787a4f375e4e40e6eac722dcae309fb4054/src/base/ossimKeywordlist.cpp> > > Take care, > Dave > > > > On Mon, Jul 9, 2018 at 10:31 AM, Oscar Kramer <osc...@ra... <mailto:osc...@ra...>> wrote: > JR, > > I'm forwarding your email to the list as this is something we need working in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() method recently. The fact that you are getting a "method not found" error at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. Did you build OSSIM from source? Do you see that method in ossimKeywordlist.cpp? > > Whether it actually works or not, I don't know. I let Dave defend that... > > Oscar > > > > <http://www.radiantsolutions.com/> > Oscar L Kramer > Senior Software Engineer > +1.321.821.1139 office <> > oscar.kramer@radiantsolutions. com <mailto:osc...@ra...> > > On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm... <mailto:gar...@gm...>> wrote: > Hey JR: > > Been on vacation. Just got back today. Will look at your information this week. > > > Take care > > Garrett > > >> On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Raul.Marquez@radiantsolutions .com <mailto:Rau...@ra...>> wrote: >> >> Hey guys, >> >> Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist in JSON form and having some issues. Can you let me know if I’m doing anything wrong? Pretty much giving it a few key,value pairs, initializing it and calling getImageInfo. I get back the kwl and I can transform it into a string with strdup but I want it in JSON format. I noticed that it has a toJSON method but I keep getting a no matching function or call for it. DISCLAIMER: I suck at c++ >> >> Any help is much appreciated. >> >> -JR >> >> >> >> std::string key; >> std::string value; >> std::string value2; >> ossimKeywordlist kwl; >> >> key = "build_date"; >> value = "true"; >> kwl.addPair( key, value ); >> >> key = "image_file"; >> value2 = "/home/rmarquez/Downloads/imag es/17MAR20054817-P1BS-05659936 2010_01_P004.NTF"; >> kwl.addPair( key, value2 ); >> >> key = "geometry_info"; >> kwl.addPair( key, value ); >> >> key = "image_info"; >> kwl.addPair( key, value ); >> >> key = "metadata"; >> kwl.addPair( key, value ); >> >> // Make the info object. >> ossimInfo* oi = new ossimInfo(); >> >> // Pass options in: >> ossimTool* ot = dynamic_cast<ossimTool*>(oi); >> if ( ot ) >> { >> ot->initialize( kwl ); >> } >> >> oi->getImageInfo( "/home/rmarquez/Downloads/imag es/17MAR20054817-P1BS-05659936 2010_01_P004.NTF", false, false, false, true, false, false, kwl); >> >> >> //const char* val = strdup(kwl.toString()); >> >> std::ostream os( NULL ); >> const std::string rootTag="info"; >> cout << "TEST: " << kwl.toJSON(&os,&rootTag); >> >> >> >> <image001.png> <http://www.radiantsolutions.com/> >> Raul Marquez Jr >> Software Developer | OTD >> 571-721-3593 office <> >> Raul.Marquez@radiantsolutions. com <mailto:Rau...@ra...> >> <image002.png> <https://twitter.com/radiant_maxar> <image003.png> <https://www.linkedin.com/company/radiant-solutions/> >> >> >> >> This electronic communication and any attachments may contain confidential and proprietary information of Radiant Solutions, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. >> >> Radiant Solutions reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. > > > > ------------------------------ ------------------------------ ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot> > ______________________________ _________________ > www.ossim.org <http://www.ossim.org/> > Ossim-developer mailing list > Ossim-developer@lists. sourceforge.net <mailto:Oss...@li...> > https://lists.sourceforge.net/ lists/listinfo/ossim-developer <https://lists.sourceforge.net/lists/listinfo/ossim-developer> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot> > _______________________________________________ > 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> > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: Oscar K. <osc...@ya...> - 2018-07-10 09:18:35
|
Dave, What about the ossimKeywordlist::toJson() method that is there now? On Monday, July 9, 2018, 6:31:29 PM EDT, David Burken <db...@gm...> wrote: Hi guys, The ossimKeywordlist::writeJsonToStream() was in a pull request I submitted that got merged into dev but then reverted. It might be too hard to resurrect it at this point. // It's in this branch but it's hard to follow now as it has commits post the pull request. https://github.com/ossimlabs/ossim/tree/drb-20171108 // This has the json method: https://github.com/ossimlabs/ossim/blob/2b8ba787a4f375e4e40e6eac722dcae309fb4054/src/base/ossimKeywordlist.cpp Take care,Dave On Mon, Jul 9, 2018 at 10:31 AM, Oscar Kramer <osc...@ra...> wrote: JR, I'm forwarding your email to the list as this is something we need working in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() method recently. The fact that you are getting a "method not found" error at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. Did you build OSSIM from source? Do you see that method in ossimKeywordlist.cpp? Whether it actually works or not, I don't know. I let Dave defend that... Oscar | | Oscar L Kramer Senior Software Engineer +1.321.821.1139 office oscar.kramer@radiantsolutions. com | | On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm...> wrote: Hey JR: Been on vacation. Just got back today. Will look at your information this week. Take care Garrett On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Raul.Marquez@radiantsolutions .com> wrote: Hey guys, Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist in JSON form and having some issues. Can you let me know if I’m doing anything wrong? Pretty much giving it a few key,value pairs, initializing it and calling getImageInfo. I get back the kwl and I can transform it into a string with strdup but I want it in JSON format. I noticed that it has a toJSON method but I keep getting a no matching function or call for it. DISCLAIMER: I suck at c++ Any help is much appreciated. -JR std::string key; std::string value; std::string value2; ossimKeywordlist kwl; key = "build_date"; value = "true"; kwl.addPair( key, value ); key = "image_file"; value2 = "/home/rmarquez/Downloads/imag es/17MAR20054817-P1BS-05659936 2010_01_P004.NTF"; kwl.addPair( key, value2 ); key = "geometry_info"; kwl.addPair( key, value ); key = "image_info"; kwl.addPair( key, value ); key = "metadata"; kwl.addPair( key, value ); // Make the info object. ossimInfo* oi = new ossimInfo(); // Pass options in: ossimTool* ot = dynamic_cast<ossimTool*>(oi); if ( ot ) { ot->initialize( kwl ); } oi->getImageInfo( "/home/rmarquez/Downloads/imag es/17MAR20054817-P1BS-05659936 2010_01_P004.NTF", false, false, false, true, false, false, kwl); //const char* val = strdup(kwl.toString()); std::ostream os( NULL ); const std::string rootTag="info"; cout << "TEST: " << kwl.toJSON(&os,&rootTag); | <image001.png> | Raul Marquez Jr Software Developer | OTD 571-721-3593 office Raul.Marquez@radiantsolutions. com | | | | <image002.png> <image003.png> | This electronic communication and any attachments may contain confidential and proprietary information of Radiant Solutions, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. Radiant Solutions reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. ------------------------------ ------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ______________________________ _________________ www.ossim.org Ossim-developer mailing list Ossim-developer@lists. sourceforge.net https://lists.sourceforge.net/ lists/listinfo/ossim-developer ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ www.ossim.org Ossim-developer mailing list Oss...@li... https://lists.sourceforge.net/lists/listinfo/ossim-developer |
From: David B. <db...@gm...> - 2018-07-09 22:31:09
|
Hi guys, The ossimKeywordlist::writeJsonToStream() was in a pull request I submitted that got merged into dev but then reverted. It might be too hard to resurrect it at this point. // It's in this branch but it's hard to follow now as it has commits post the pull request. https://github.com/ossimlabs/ossim/tree/drb-20171108 // This has the json method: https://github.com/ossimlabs/ossim/blob/2b8ba787a4f375e4e40e6eac722dcae309fb4054/src/base/ossimKeywordlist.cpp Take care, Dave On Mon, Jul 9, 2018 at 10:31 AM, Oscar Kramer < osc...@ra...> wrote: > JR, > > I'm forwarding your email to the list as this is something we need working > in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() > method recently. The fact that you are getting a "method not found" error > at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. > Did you build OSSIM from source? Do you see that method in > ossimKeywordlist.cpp? > > Whether it actually works or not, I don't know. I let Dave defend that... > > Oscar > > > > <http://www.radiantsolutions.com/> > > Oscar L Kramer > Senior Software Engineer > +1.321.821.1139 office <//+1.321.821.1139> > osc...@ra... > > On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm...> > wrote: > >> Hey JR: >> >> Been on vacation. Just got back today. Will look at your information >> this week. >> >> >> Take care >> >> Garrett >> >> >> On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Raul.Marquez@radiantsolutions >> .com> wrote: >> >> Hey guys, >> >> Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist >> in JSON form and having some issues. Can you let me know if I’m doing >> anything wrong? Pretty much giving it a few key,value pairs, initializing >> it and calling getImageInfo. I get back the kwl and I can transform it >> into a string with strdup but I want it in JSON format. I noticed that it >> has a toJSON method but I keep getting a no matching function or call for >> it. DISCLAIMER: I suck at c++ >> >> Any help is much appreciated. >> >> -JR >> >> >> >> std::string key; >> std::string value; >> std::string value2; >> ossimKeywordlist kwl; >> >> key = "build_date"; >> value = "true"; >> kwl.addPair( key, value ); >> >> key = "image_file"; >> value2 = "/home/rmarquez/Downloads/images/17MAR20054817-P1BS-05659936 >> 2010_01_P004.NTF"; >> kwl.addPair( key, value2 ); >> >> key = "geometry_info"; >> kwl.addPair( key, value ); >> >> key = "image_info"; >> kwl.addPair( key, value ); >> >> key = "metadata"; >> kwl.addPair( key, value ); >> >> // Make the info object. >> ossimInfo* oi = new ossimInfo(); >> >> // Pass options in: >> ossimTool* ot = dynamic_cast<ossimTool*>(oi); >> if ( ot ) >> { >> ot->initialize( kwl ); >> } >> >> oi->getImageInfo( "/home/rmarquez/Downloads/imag >> es/17MAR20054817-P1BS-056599362010_01_P004.NTF", false, false, false, >> true, false, false, kwl); >> >> >> //const char* val = strdup(kwl.toString()); >> >> std::ostream os( NULL ); >> const std::string rootTag="info"; >> cout << "TEST: " << kwl.toJSON(&os,&rootTag); >> >> >> >> >> <image001.png> <http://www.radiantsolutions.com/> >> *Raul Marquez Jr* >> Software Developer | OTD >> 571-721-3593 office <//571-721-3593> >> Rau...@ra... >> <image002.png> <https://twitter.com/radiant_maxar> <image003.png> >> <https://www.linkedin.com/company/radiant-solutions/> >> >> >> >> This electronic communication and any attachments may contain >> confidential and proprietary information of Radiant Solutions, Inc. If you >> are not the intended recipient, or an agent or employee responsible for >> delivering this communication to the intended recipient, or if you have >> received this communication in error, please do not print, copy, >> retransmit, disseminate or otherwise use the information. Please indicate >> to the sender that you have received this communication in error, and >> delete the copy you received. >> >> Radiant Solutions reserves the right to monitor any electronic >> communication sent or received by its employees, agents or representatives. >> >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > > |
From: Marquez, R. <Rau...@ra...> - 2018-07-09 15:41:16
|
Hey Oscar, Garrett helped me out a bit. I had to remove the & symbol. Ultimately it came out to the below code. I should probably add some try,catches in there. My original ostream wasn’t working since it was empty. I guess I could have used it as long as I find out how to put my kwl into it. Using a string stream works though which is what I want since I call out.str() on it after all that. Looking into the ImageStager stuff now but I’ve pinged Garrett on slack. Thanks! -JR // Make the info object. ossimInfo* oi = new ossimInfo(); // Pass options in: ossimTool* ot = dynamic_cast<ossimTool*>(oi); if ( ot ) { ot->initialize( kwl ); } oi->getImageInfo( "/home/rmarquez/Downloads/images/17MAR20054817-P1BS-056599362010_01_P004.NTF", false, false, false, true, false, false, kwl); std::stringstream out; const std::string rootTag="info"; kwl.toJSON(out,rootTag); From: Oscar Kramer [mailto:osc...@ra...] Sent: Monday, July 09, 2018 10:31 AM To: OSSIM <oss...@li...> Cc: Marquez, Raul <Rau...@ra...> Subject: Re: OSSIM help JR, I'm forwarding your email to the list as this is something we need working in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() method recently. The fact that you are getting a "method not found" error at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. Did you build OSSIM from source? Do you see that method in ossimKeywordlist.cpp? Whether it actually works or not, I don't know. I let Dave defend that... Oscar [https://digitalglobe-marketing.s3.amazonaws.com/files/signature/radiantsolutions-sig-logo.png]<http://www.radiantsolutions.com/> Oscar L Kramer Senior Software Engineer +1.321.821.1139 office<tel://+1.321.821.1139> osc...@ra...<mailto:osc...@ra...> On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm...<mailto:gar...@gm...>> wrote: Hey JR: Been on vacation. Just got back today. Will look at your information this week. Take care Garrett On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Rau...@ra...<mailto:Rau...@ra...>> wrote: Hey guys, Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist in JSON form and having some issues. Can you let me know if I’m doing anything wrong? Pretty much giving it a few key,value pairs, initializing it and calling getImageInfo. I get back the kwl and I can transform it into a string with strdup but I want it in JSON format. I noticed that it has a toJSON method but I keep getting a no matching function or call for it. DISCLAIMER: I suck at c++ Any help is much appreciated. -JR std::string key; std::string value; std::string value2; ossimKeywordlist kwl; key = "build_date"; value = "true"; kwl.addPair( key, value ); key = "image_file"; value2 = "/home/rmarquez/Downloads/images/17MAR20054817-P1BS-056599362010_01_P004.NTF"; kwl.addPair( key, value2 ); key = "geometry_info"; kwl.addPair( key, value ); key = "image_info"; kwl.addPair( key, value ); key = "metadata"; kwl.addPair( key, value ); // Make the info object. ossimInfo* oi = new ossimInfo(); // Pass options in: ossimTool* ot = dynamic_cast<ossimTool*>(oi); if ( ot ) { ot->initialize( kwl ); } oi->getImageInfo( "/home/rmarquez/Downloads/images/17MAR20054817-P1BS-056599362010_01_P004.NTF", false, false, false, true, false, false, kwl); //const char* val = strdup(kwl.toString()); std::ostream os( NULL ); const std::string rootTag="info"; cout << "TEST: " << kwl.toJSON(&os,&rootTag); <image001.png><http://www.radiantsolutions.com/> Raul Marquez Jr Software Developer | OTD 571-721-3593 office<tel://571-721-3593> Rau...@ra...<mailto:Rau...@ra...> <image002.png><https://twitter.com/radiant_maxar> <image003.png><https://www.linkedin.com/company/radiant-solutions/> This electronic communication and any attachments may contain confidential and proprietary information of Radiant Solutions, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. Radiant Solutions reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. This electronic communication and any attachments may contain confidential and proprietary information of Radiant Solutions, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. Radiant Solutions reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. |
From: Oscar K. <osc...@ra...> - 2018-07-09 14:57:21
|
JR, I'm forwarding your email to the list as this is something we need working in OSSIM. I believe Dave Burken implemented the ossimKeywordlist::toJson() method recently. The fact that you are getting a "method not found" error at runtime (I presume) sounds like you're linking with the wrong OSSIM lib. Did you build OSSIM from source? Do you see that method in ossimKeywordlist.cpp? Whether it actually works or not, I don't know. I let Dave defend that... Oscar <http://www.radiantsolutions.com/> Oscar L Kramer Senior Software Engineer +1.321.821.1139 office <//+1.321.821.1139> osc...@ra... On Sun, Jul 8, 2018 at 7:56 PM, Garrett Potts <gar...@gm...> wrote: > Hey JR: > > Been on vacation. Just got back today. Will look at your information > this week. > > > Take care > > Garrett > > > On Jul 5, 2018, at 10:37 AM, Marquez, Raul <Raul.Marquez@ > radiantsolutions.com> wrote: > > Hey guys, > > Was hoping to get some OSSIM help. I’m trying to get the ossimKeywordlist > in JSON form and having some issues. Can you let me know if I’m doing > anything wrong? Pretty much giving it a few key,value pairs, initializing > it and calling getImageInfo. I get back the kwl and I can transform it > into a string with strdup but I want it in JSON format. I noticed that it > has a toJSON method but I keep getting a no matching function or call for > it. DISCLAIMER: I suck at c++ > > Any help is much appreciated. > > -JR > > > > std::string key; > std::string value; > std::string value2; > ossimKeywordlist kwl; > > key = "build_date"; > value = "true"; > kwl.addPair( key, value ); > > key = "image_file"; > value2 = "/home/rmarquez/Downloads/images/17MAR20054817-P1BS- > 056599362010_01_P004.NTF"; > kwl.addPair( key, value2 ); > > key = "geometry_info"; > kwl.addPair( key, value ); > > key = "image_info"; > kwl.addPair( key, value ); > > key = "metadata"; > kwl.addPair( key, value ); > > // Make the info object. > ossimInfo* oi = new ossimInfo(); > > // Pass options in: > ossimTool* ot = dynamic_cast<ossimTool*>(oi); > if ( ot ) > { > ot->initialize( kwl ); > } > > oi->getImageInfo( "/home/rmarquez/Downloads/images/17MAR20054817-P1BS-056599362010_01_P004.NTF", > false, false, false, true, false, false, kwl); > > > //const char* val = strdup(kwl.toString()); > > std::ostream os( NULL ); > const std::string rootTag="info"; > cout << "TEST: " << kwl.toJSON(&os,&rootTag); > > > > > <image001.png> <http://www.radiantsolutions.com/> > *Raul Marquez Jr* > Software Developer | OTD > 571-721-3593 office <//571-721-3593> > Rau...@ra... > <image002.png> <https://twitter.com/radiant_maxar> <image003.png> > <https://www.linkedin.com/company/radiant-solutions/> > > > > This electronic communication and any attachments may contain confidential > and proprietary information of Radiant Solutions, Inc. If you are not the > intended recipient, or an agent or employee responsible for delivering this > communication to the intended recipient, or if you have received this > communication in error, please do not print, copy, retransmit, disseminate > or otherwise use the information. Please indicate to the sender that you > have received this communication in error, and delete the copy you received. > > > Radiant Solutions reserves the right to monitor any electronic > communication sent or received by its employees, agents or representatives. > > > |
From: Oscar K. <osc...@ya...> - 2018-05-16 15:03:10
|
Alas, no -- at least not that I'm aware of. Your best bet is to search first for the base keyword in caps (e.g, "ADJUSTMENT", "DISTORTION", etc.). I can tell you that the adjustments are read and loaded in ossim/src/base/ossimAdjustableParameterInterface.cpp's loadAdjustments(). That class is a base-class for ossimSensorModel. The lens distortion is handled by ossim/src/projection/ossimRadialDecentLensDistortion.cpp. Oscar On Wednesday, May 16, 2018, 10:48:55 AM EDT, Guillaume Drolet <dro...@gm...> wrote: Forgot to ask: Is there a document that defines what all the variables in Ossim geometry (.geom) files mean (e.g. adjustment_0.*, distortion.*)? Cheers. 2018-05-15 17:46 GMT-04:00 Guillaume Drolet <dro...@gm...>: Oscar, The 1 arcsec DEM has been smoothed using a gaussian filter, hence its smooth look compared with the 100m DEM. The elevation profiles are for a diagonal that goes from the lower left corner of the image to its upper right corner. Re Summit, as far as I know, Summit is never involved in the aerotriangulation process. Aerotriangulation is performed as one of the first steps prior to calculating the affine transformation matrices in DVP (i.e. the variables in the PAR file). Also, the TIN used in Summit to orthorectify the image (the one thats "almost" perfectly lined up with the road network and the Google Earth image) has much less points than the TIN referenced in the DVP PAR file (i.e. the .tgl file). At this point, I suspect that either 1) Summit uses more information from the DVP PAR file compared with Ossim, e.g. affine transformation matrices, or 2) Ossim derives transformation matrix coefficients using the Applanix sensor model, which may not be fully compatible with the UltraCamD camera. In any case, I will do as you suggested and try to gather more details about the complete workchain from image acquisition to creation of the DVP PAR file. I may post more information in this thread if need be. Thanks a lot for your help, Guillaume 2018-05-14 16:03 GMT-04:00 Oscar Kramer <osc...@ya...>: Guillaume, RE the DEMS: weird that the 1 arcsec (~30m) is smoother than the 100m DEM. I don't know where in that plot your image falls, but there are areas of significant bias that could explain the scale difference observed. RE the Summit code: I have a feeling that your testing is incestuous. Perhaps you are using data that was triangulated with Summit using the reference image as ground truth, and then using the same model to project to the same ground truth. There is no way to explain the perfect alignment to the reference image otherwise. It would be a freak of statistical nature to have it line up out of the box like that. Check the chain of custody of that data set in your organization to see exactly what processing was done to it. Sorry I can't be of more help. I don't have the time to dive into a difficult problem like this. Good luck,Oscar On Monday, May 14, 2018, 1:33:19 PM EDT, Guillaume Drolet <dro...@gm...> wrote: Salut Oscar, thanks for your help! I added more info in your email below. I am not a photogrammetry expert so I surely do not understand all the details behind the orthorectification process. G 2018-05-14 10:19 GMT-04:00 Oscar Kramer <osc...@ya...>: Salut Guillaume, Can you give us a little bit of background to help you solve the problem? I am not familiar with DVP, PAR nor Summit. DVP is a photogrammetry software used, among other things, to build stereoscopic models for pairs of aerial photographs. I don't know if it also performs aero-triangulation.It is now discontinued and was replaced, in my organization, with Summit (http://www.datem.com/summit-e volution/). PAR files are model files created by DVP and contain interior and exterior orientation parameters. Summit can orthorectify an aerial photograph using only the raw image, the corresponding DVP model file (.par), and a triangular interpolated network (TIN) file. I don't know if it can also use a DEM since I don't work with Summit. In case you didn't have a look at the PAR file I put in Dropbox, here's the content of it: .GLOBAL $DATE 03-03-2008 $TIME 15:56:18 $DESCR OPK -> DVP ... $TYPE OPK $FSCALE00 2.50000000000000e+004 $FILE00 M:\Dvp\Images\JD07137\opt\rgb\ JD07137_12007.tif $VERSION 5.5 .DESCR .INTERIOR $FCAM00 C:\Projet\G1918\UltraCamD.cam $PARAFFINE00 9.00000000000000e-003 1.55854062294791e-018 -5.15700000000000e+001 8.13151629364128e-020 -9.00000000000000e-003 3.34800000000000e+001 $PARINVAFF00 1.11111111111111e+002 1.92412422586162e-014 5.73000000000000e+003 -1.01965198758660e-014 -1.11111111111111e+002 3.72000000000000e+003 $PARM00 1 -5.15700000000000e+001 3.34800000000000e+001 0.00000000000000e+000 0.00000000000000e+000 1.42108547152020e-014 -7.10542735760100e-015 1.42108547152020e-014 -1.42108547152020e-014 $PARM00 1 -5.15700000000000e+001 3.34800000000000e+001 0.00000000000000e+000 0.00000000000000e+000 1.42108547152020e-014 -7.10542735760100e-015 1.42108547152020e-014 -1.42108547152020e-014 $PARM00 2 5.19300000000000e+001 3.34800000000000e+001 1.15000000000000e+004 0.00000000000000e+000 7.10542735760100e-015 7.10542735760100e-015 0.00000000000000e+000 -1.42108547152020e-014 $PARM00 3 5.19300000000000e+001 -3.40200000000000e+001 1.15000000000000e+004 7.50000000000000e+003 -7.10542735760100e-015 1.42108547152020e-014 0.00000000000000e+000 0.00000000000000e+000 $PARM00 4 -5.15700000000000e+001 -3.40200000000000e+001 0.00000000000000e+000 7.50000000000000e+003 -7.10542735760100e-015 0.00000000000000e+000 1.42108547152020e-014 0.00000000000000e+000 $DATE 03-03-2008 $TIME 15:56:18 $FOC00 1.01400000000000e+002 .RELATIVE .ABSOLUE .RELEVEMENT .EXTERNE .CORRECTION .CALIBRAGE .TIN $TGLNAME M:\Dvp\Mne\JD07137\TGL\JD07137 _12007.tgl .INDEX .LISTMODELES .CORRECTION .CAMCOR00 $NAME UltraCamD $DATE $TYPE 1 $FOCAL 1.01400000000000e+002 $PPA 0.00000000000000e+000 0.00000000000000e+000 $PPS 0.00000000000000e+000 0.00000000000000e+000 $XP_OFFSET 0.00000000000000e+000 $YP_OFFSET 0.00000000000000e+000 $PIXELSIZE 9.00000000000000e+000 $DISTORTION_TYPE 0 .EXTERIOR $DATE 03-03-2008 $TIME 15:56:18 $XYZ00 2.62237954000000e+005 5.40876598900000e+006 2.51442300000000e+003 $OPK00 -2.24520000000000e-002 -2.24683000000000e+000 8.90675920000000e+001 .END Iobtained a document explaining part of what this file contains. Here are parameter-specific informations: $PARAFFINE00: contains the affine transformation parameters (a to f) to go from image coordinates to photo coordinates. Transformation equations are as follows: X_photo = a * X_image + b * Y_image + c Y_photo = d * X_image + e * Y_image + f $PARINVAFF0: : contains the inverse affine transformation parameters (A to F) to go from photo coordinates to image coordinates. Transformation equations are as: X_image = A * X_photo + B * Y_photo + C Y_image = D * X_photo + E * Y_photo + F In DVP, origin of image coordinates system is upper left corner. $XYZ00, $OPK00: exterior orientation parameters. The order of rotations in DVP is Omege, Phi and Kappa. $TGLNAME: this is a DVP generated TIN file. It's a binary file I can't read with my tools. However, I have a shapefile version of it (elevation points). It looks like DVP also used information from the file UltraCamD.cam (variable $FCAM00 above in the file), maybe to derive the coefficient of the affine transformation ($PARAFFINE00, $PARINVAFF0, $PARM00 in the file above)? I managed to get the UltraCamD.cam file used in DVP. Here's its content if that can help: SYSTEMAP CAMC120 101.400 -51.750 1 33.750 1 -999999.999 0 -999999.999 0 51.750 1 33.750 1 -999999.999 0 -999999.999 0 -999999.999 0 -999999.999 0 -999999.999 0 -999999.999 0 -51.750 1 -33.750 1 -999999.999 0 -999999.999 0 51.750 1 -33.750 1 1 1 -0.180 0.270 4 0.0000000e+000 0.0000000e+000 0.0000000e+000 0.0000000e+000 I also have a calibration report for the camera but it's a pdf and doesn't contain tabular data for distortion values, only plots. Here it is: https://www.dropbox.com/s/hm7s r2tpy6c6f2g/Calib-Report_0034_ V70_short.pdf?dl=0 Also, what is the ground truth background you are comparing to on the mosaics you provided? It's a Google satellite map (OpenLayers QGIS plugin) as well as the road network (white lines, 1:20K) produced by my organization (Ministry of forests) and used for forest planning, etc. There are many things that can be an issue. You pointed out rotation matrices. Perhaps the Applanix model if performing the rotations in a different order (though I would expect a much bigger discrepancy in that case). Also perhaps Summit can read DVP distortion parameters. Where would Summit read distortion values from? Could they be the $PARM00 variables in the PAR file above? As I mentioned, Summit uses only the information contained in the PAR file and a TIN to create the orthoimage. RE the 100m v 30 arcsec DEM results. I don't know what to make of that. Indeed, the 100 m DEM seems to have a big scale error as if there was a significant elevation bias. Did you compare the DEMs to see if there is in fact a bias between the two? I created a profile plot that compares the two DEMs (red: 1arc, blue: 100m): https://www.dropbox.com/s/8wid xe4lyx657wi/DEM_1arc_vs_100m. png?dl=0 Note how the 1arc DEM has been smoothed. Not sure though if this is a problem since the TIN used by Summit was created with a very low point density (see below). What DEM did the Summit results use? For Summit, the registration to "truth" for that image is nearly perfect. Was this using the raw camera parameters straight off the platform? Or was the model corrected (using the Summit s/w perhaps)? Summit uses only the PAR file and a TIN. I don't know how Summit uses the information but what I know is that there hasn't been further processing performed on the resulting image after Summit created it. Here's an image showing the topography (black lines) and elevation points (white) used to create the TIN used by Summit: https://www.dropbox.com/s/jivu 6xnaws9tnyn/topography.png?dl= 0 The orange layer in the background is the 1arc DEM and the orthoimage is the one created by Summit. Note the low elevation points density used to create the TIN used by Summit. Thanks for helping me with this. I hope this additional information will be helpful. G Oscar On Monday, May 14, 2018, 8:15:10 AM EDT, Guillaume Drolet <dro...@gm...> wrote: Hi, I try to orthorectify aerial photos from the Ultracam D camera. I have a raw image and a model file (.par) from the DVP software. I copy some of the information from the model file into an Applanix exterior orientation file. The variables I copy from the model file into the Applanix exterior orientation file are: ID, EVENT, EASTING, NORTHING, ORTHOM_HEIGHT, OMEGA, PHI, KAPPA, LAT, LONG I use metadata found in the raw image Tiff tags to write a camera file: NOTE: I set distortion values to zero since I don't have this information. sensor: UCD-SU-1-0034 focal_length: 101.400 principal_point: -0.180 0.270 image_size: 11500.0 7500.0 pixel_size: 0.009 d1: 1 0 d2: 2 0 d3: 3 0 d4: 4 0 d5: 5 0 d6: 6 0 d7: 7 0 d8: 8 0 d9: 9 0 d10: 10 0 d11: 11 0 d12: 12 0 d13: 13 0 d14: 14 0 d15: 15 0 d16: 16 0 d17: 17 0 d18: 18 0 d19: 19 0 d20: 20 0 d21: 21 0 d22: 22 0 d23: 23 0 d24: 24 0 d25: 25 0 d26: 26 0 d27: 27 0 d28: 28 0 d29: 29 0 d30: 30 0 distortion_units: microns Finally, I use the camera and Applanix files to create a geometry file (.geom) using ossim-applanix2ogeom. When I then run ossim-orthoigen, I don't get results as good as if I use theSummitsoftware to create the orthoimage, feeding it only the raw image and model file. With ossim, the result gets better if I use a 1arc DEM instead of a 100m-DEM but still, it is not as good as when doing it in Summit. I suspect Summit might use more info from the DVP model file which I don't include in my workflow (maybe the rotation matrix?). I would be very grateful if anyone comes up with suggestions that could help achieve results with Ossim that are as good as those obtained using Summit (maybe, for example, by adding more info from the model file into my workflow? I would really like to be able to process my images with ossim: I don't have access to Summit and so I need to rely on other people to do it for me (which isn't always possible). Here are links to images and files that I hope will help you come up with suggestions: raw image: https://www.dropbox.com/s/ s9jdwzsp3a20dpt/JD07137_12007. TIF?dl=0 DVP model file: https://www.dropbox.com/s/ eh32r7563a8ll6w/JD07137_12007. par?dl=0 geometry file: https://www.dropbox.com/s/ 1qo9kw5fdcsniq1/JD07137_12007. geom?dl=0 PNG of orthoimage created with Ossim using a 100m DEM: https://www.dropbox.com/s/ zzm40kqo9js4mig/dem_100m.png? dl=0 PNG of orthoimage created with Ossim using a 1arc DEM: https://www.dropbox.com/s/ 0x7k4rjbziqb9pp/dem_1arc.png? dl=0 PNG of orthoimage created with Summit: https://www.dropbox.com/s/ l8q2qpufq3pkior/summit_TIN. png?dl=0 Thanks a lot for your help, Guillaume ------------------------------ ------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ ______________________________ ___________ www.ossim.org Ossim-developer mailing list Ossim-developer@lists. sourceforge.net https://lists.sourceforge.net/ lists/listinfo/ossim-developer |