Hello, extended filename key "geom" is also interesting to associate .geom to image data http://wiki.orfeo-toolbox.org/index.php/ExtendedFileName
I agree with that "On second thought, I think having this as an OTB application would be nice : from any input file in sensor model geometry, we could generate a GeoTIFF/NITF with standard RPC tags, that approximate the sensor model." I think the inverse processing is also interesting (from Geotiff with Nitf RPC model embedded to ossim nitf rpc model) 2014-01-30 Julien Malik <[email protected]>: > > On 01/19/2014 03:44 PM, Telepinu wrote: > > > Dear fellow colleagues, > I have been developing an automated image processing system for satellite > imagery. > So far I developed band registration, and gereferencing using a base image > using feature points, similar to Homologous Points Extraction. > I use OpenCV and GDAL libraries. I use SRTM DEM. > > Currently I succesfully geolocate images; but I want to *orthorectify*images. > Unfortunately we do not have a sensor model. > I want to learn that: > > - Using Orfeo, can I produce a generic sensor model or shall I compute > them for each image? > > > OTB knows about a generic RPC sensor model that can attached to any > supported input file format. > This is represented by the "geom" file that the "GenerateRPCSensorModel" > creates. > > If your image is "myimage.tif", then put the geom file created by > GenerateRPCSensorModel next to it, and rename it "myimage.geom". > Then the OTB orthorectification application will recognize it and will be > able to orthorectify your image. > > > > - How can I embed RPC file computed by Generate a RPC sensor model? Is > is straight forward? > > > I assume you mean transforming the RPC coefficient in the ouput ".geom" > file into standard GeoTIFF tags. > This is possible of course, but there is nothing in OTB to do that right > now. > This would be a nice feature to add in OTB, since it would make the RPC > coefficient computed with OTB available to other software in a standardized > way. > > This shall be quite simple to implement, using the GDAL API (it would then > be also available for the NITF format). > If you come up with a piece of code that does the job, even a prototype, I > hope you can open source it. > We could then use it as a support for implementing the functionnality in > OTB. > > On second thought, I think having this as an OTB application would be nice > : from any input file in sensor model geometry, we could generate a > GeoTIFF/NITF with standard RPC tags, that approximate the sensor model. > > > Julien > > > > -- > -- > 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/groups/opt_out. > -- -- 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/groups/opt_out.
