Doug, One other point, my NTF's were compressed using JPEG2000 and I used the following technique to setup processing stages. I've extracted this from my batch script so I shouldn't leave out any missing pieces. I've also ( I believe, please correct me if not) optimized the interleaving/tiling/blocksize parameters for speed.
--Eric mkdir 00_original 01_uncompressed 02_toa 03_ortho etc.. move original WVO2.NTF, WV02.TIL, WV02.IMD metadata files to root folder above 00_x dirs set GDAL_CACHEMAX=1024 set GDAL_SWATH_SIZE=1073741824 set GDAL_NUM_THREADS=2 # uncompress NITF to NITF (TIF won't work for opticalcalibration) gdal_translate -of NITF -co "ICORDS=G" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" %basename%.NTF 01_uncompressed\%basename%.NTF # Shuffle files move WV02.NTF 00_original move 01_uncompressed\WV02.NTF . #OpticalCalibration call otbcli_OpticalCalibration -in %basename%.NTF -level toa -ram 1024 -out "%basename%_TOAREF_FLOAT.TIF?&gdal:co:INTERLEAVE=BAND&gdal:co:TILED=YES&gdal:co:BLOCKXSIZE=256&gdal:co:BLOCKYSIZE=256" #Create compressed version of TOAREF for future use (classification) gdal_translate -ot uint16 -scale 0.0 1.0 0 65535 -co "COMPRESS=PACKBITS" -co "INTERLEAVE=BAND" -co "TILED=YES" %basename%_TOAREF_FLOAT.TIF %basename%_TOAREF.TIF #Orthorectify 16-bits->16-bits gdalwarp -to "RPC_DEM=%dem%" -co "INTERLEAVE=BAND" -co "TILED=YES" -tr 0.000021457672119140625 0.000021457672119140625 -rpc -et 0 -overwrite -wo "WRITE_FLUSH=YES" -wo "OPTIMIZE_SIZE=YES" -multi -r cubic -dstnodata 0 -wm 1024 -of GTiff %basename%_TOAREF.TIF %basename%_ORTHO16.TIF #Compress and downsample to 8-bits gdal_translate -of GTiff -ot Byte -scale 0 65535 0 255 -co "COMPRESS=PACKBITS" -co "INTERLEAVE=BAND" -co "TILED=YES" %basename%_ORTHO16.TIF %basename%_ORTHO.TIF On Fri, Feb 20, 2015 at 11:37 AM, Doug Creel <[email protected]> wrote: > With that tip in mind, I did get one step in the right direction. > > Steps: > Used otbcli_orthorectification NTF to create TIF (readImageInfo did not > recognize sensor or RPC no matter how I renamed/revised the metadata files > until converted to TIF) > Extracting the RPB/IMD file from NTF tar to the main directory and renamed > to match TIF. > Extracted the TIL file from the NTF tar to the main directory, renamed to > match TIF, and revised filename parameter within to match TIF. > Obcli_ReadImageInfo on the TIF's TIL shows the RpcModel as > ossimQuickbirdMetaData, while the same command on the NITF's TIL shows the > RpcModel as ossimRpcModel. > > Its not 100% yet, since the sensor type isn't recognized yet in > otbcli_opticalcalibration, but at least ossim knows the model type. Testing > continues.... > > On Thu, Feb 19, 2015 at 3:21 PM, Eric Wenger <[email protected]> > wrote: > >> Doug, >> >> One issue I have had with these images is case-sensitivity in the >> filename. OTB looks in the metadata files -- IMD maybe -- and finds the >> NTF filename in ALL CAPS. If it isn't all caps on your filesystem with >> exactly the name in the IMD/RPC/TIL etc. files, ossim won't detect the >> sensor. >> >> --Eric >> >> On Thu, Feb 19, 2015 at 8:30 AM, Doug Creel <[email protected]> >> wrote: >> >>> Dear All- >>> I have been following the cookbook process for preparing raw NTFs >>> of Worldview 2 and QuickBird2 but have run into a problem. >>> http://otbcb.readthedocs.org/en/latest/recipes/optpreproc.html >>> >>> C:\>otbcli_OpticalCalibration -in C:\test\QB\TestQB02-M1BS.NTF -out >>> C:\test\QB02-M1BS.tif -level toc >>> 2015 Feb 19 08:26:04 : Application.logger (INFO) >>> File: C:\test\QB02-M1BS.NTF >>> Sensor unknown! >>> Additional parameters are necessary, please provide them (cf. >>> documentation)! >>> ERROR: Missing mandatory parameter: acqui.gainbias 0 >>> ERROR: Troubles loading parameter, please check your line argument... >>> >>> Ossim does not recognize the sensor type and will not allow >>> OpticalCalibration or assign the correct RPC for Orthorectification. >>> I have checked otbcli_ReadImageInfo and the sensor type is blank with >>> the generic type. >>> >>> numberbands: 4 >>> sensor: >>> id: >>> time: >>> type: ossimRpcModel. >>> >>> However, using GDALINFO, the sensor type is recognized: >>> >>> NITF_ISORCE=QB02 >>> NITF_PIAIMC_SENSNAME=QB02 >>> NITF_STDIDC_MISSION=QB02 >>> >>> The images are NTF with the tar file containing the IMD, TIL, and the >>> rest of the metadata. I have also extracted the IMD and TIL to the same >>> folder as the NTF and renamed to match but the sensor type still isn't >>> read. >>> >>> I'm hoping this is an easy fix on my end since its happening with all of >>> my NTFs. >>> >>> Thanks everyone- >>> >>> -- >>> -- >>> Check the OTB FAQ at >>> http://www.orfeo-toolbox.org/FAQ.html >>> >>> You received this message because you are subscribed to the Google >>> Groups "otb-users" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/otb-users?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "otb-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> -- >> Check the OTB FAQ at >> http://www.orfeo-toolbox.org/FAQ.html >> >> You received this message because you are subscribed to the Google >> Groups "otb-users" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/otb-users?hl=en >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "otb-users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/otb-users/jURdeyMYVIc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > -- > Check the OTB FAQ at > http://www.orfeo-toolbox.org/FAQ.html > > You received this message because you are subscribed to the Google > Groups "otb-users" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/otb-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "otb-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- Check the OTB FAQ at http://www.orfeo-toolbox.org/FAQ.html You received this message because you are subscribed to the Google Groups "otb-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/otb-users?hl=en --- You received this message because you are subscribed to the Google Groups "otb-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
