SAR imagery managing

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

SAR imagery managing

Martina Di Rita
Hi everybody, 

I would like to know how can I handle SAR imagery within OSSIM.

I'm trying to test 2 kind of SAR images: RADARSAT and TerraSAR. So far I manage to correctly use ossim-info on RADARSAT imagery (that are .tif file), instead I have some problem in doing that with TerraSAR imagery (that are not .tif rather .xml and .cos).

Furthermore I tried  to use ossim-chipper --op ortho (my final goal is to orthorectify these images): on TerraSAR it doesn't work, on RADARSAT I'm not sure if it correctly merges the 2 image bands in order to compute the amplitude to orthorectify.

Anyone knows how to do this?

Any further suggestion about using SAR imagery within OSSIM is welcome.

Thank you for your kind support, 

Martina 

--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone ++39 0644585087
E-mail [hidden email]

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
www.ossim.org
Ossim-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/ossim-developer
Reply | Threaded
Open this post in threaded view
|

Re: SAR imagery managing

DBurken@Radiantblue.com
Hi Martina,

First thing, you need a plugin.

In svn:
ossim_plugins/ossim

In git:
ossim_plugins/cnes

Then see if you are picking up the correct model.  Do ossim-info on your data.  We can take it from there...

Take care,
Dave


On 11/24/2015 06:57 AM, Martina Di Rita wrote:
Hi everybody, 

I would like to know how can I handle SAR imagery within OSSIM.

I'm trying to test 2 kind of SAR images: RADARSAT and TerraSAR. So far I manage to correctly use ossim-info on RADARSAT imagery (that are .tif file), instead I have some problem in doing that with TerraSAR imagery (that are not .tif rather .xml and .cos).

Furthermore I tried  to use ossim-chipper --op ortho (my final goal is to orthorectify these images): on TerraSAR it doesn't work, on RADARSAT I'm not sure if it correctly merges the 2 image bands in order to compute the amplitude to orthorectify.

Anyone knows how to do this?

Any further suggestion about using SAR imagery within OSSIM is welcome.

Thank you for your kind support, 

Martina 

--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone ++39 0644585087
E-mail [hidden email]


------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
www.ossim.org
Ossim-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/ossim-developer
Reply | Threaded
Open this post in threaded view
|

Re: SAR imagery managing

Martina Di Rita
Hi Dave, 

I have the plug-in you are referring to.

Ossim-info gives me back for an image the following:


image0.band0.max_value:  32767
image0.band0.min_value:  -32767
image0.band0.null_value:  -32768
image0.driver:  ossim_tiff
image0.entry:  0
image0.geometry.decimal_degrees_per_pixel_lat:  9.01937579124763e-06
image0.geometry.decimal_degrees_per_pixel_lon:  8.95975281779772e-06
image0.geometry.decimations:  (1,1)
image0.geometry.gsd:  (1,1)
image0.geometry.image_size:  (13784,8713)
image0.geometry.ll_lat:  -0.078581311581282
image0.geometry.ll_lon:  -73.4887436072343
image0.geometry.lr_lat:  -0.0785945141898716
image0.geometry.lr_lon:  -73.3652512194458
image0.geometry.meters_per_pixel_x:  1
image0.geometry.meters_per_pixel_y:  1
image0.geometry.projection.central_meridian:  -69
image0.geometry.projection.datum:  WGE
image0.geometry.projection.elevation_lookup_flag:  0
image0.geometry.projection.ellipse_code:  WE
image0.geometry.projection.ellipse_epsg_code:  7030
image0.geometry.projection.ellipse_name:  WGS 84
image0.geometry.projection.false_easting_northing:  (500000,0)
image0.geometry.projection.false_easting_northing_units:  meters
image0.geometry.projection.hemisphere:  N
image0.geometry.projection.major_axis:  6378137
image0.geometry.projection.minor_axis:  6356752.3142
image0.geometry.projection.origin_latitude:  0
image0.geometry.projection.original_map_units:  meters
image0.geometry.projection.pcs_code:  32619
image0.geometry.projection.pixel_scale_units:  meters
image0.geometry.projection.pixel_scale_xy:  (1,1)
image0.geometry.projection.srs_name:  EPSG:32619
image0.geometry.projection.tie_point_units:  meters
image0.geometry.projection.tie_point_xy:  (0.5,-0.5)
image0.geometry.projection.type:  ossimUtmProjection
image0.geometry.projection.zone:  19
image0.geometry.target_rrds:  0
image0.geometry.tie_point_lat:  -4.5096879326155e-06
image0.geometry.tie_point_lon:  -73.4887394050139
image0.geometry.type:  ossimImageGeometry
image0.geometry.ul_lat:  -4.5096879326155e-06
image0.geometry.ul_lon:  -73.4887394050139
image0.geometry.ur_lat:  -4.51044561415067e-06
image0.geometry.ur_lon:  -73.3652471319262
image0.lr_x:  13783
image0.lr_y:  8712
image0.number_decimation_levels:  1
image0.number_input_bands:  1
image0.number_lines:  8713
image0.number_output_bands:  1
image0.number_samples:  13784
image0.radiometry:  16-bit signed
image0.type:  ossimTiffTileSource
image0.ul_x:  0
image0.ul_y:  0
number_entries:  1

And for the other:

image0.band0.max_value:  46340
image0.band0.min_value:  0
image0.band0.null_value:  -32768
image0.band1.max_value:  46340
image0.band1.min_value:  0
image0.band1.null_value:  -32768
image0.driver:  ossim_tiff
image0.entry:  0
image0.geometry.decimal_degrees_per_pixel_lat:  1.85605672011629e-05
image0.geometry.decimal_degrees_per_pixel_lon:  2.33485577161292e-05
image0.geometry.decimations:  (1,1)
image0.geometry.gsd:  (1.93985453061563,1.93985453061563)
image0.geometry.image_size:  (13784,8713)
image0.geometry.ll_lat:  46.8529948426282
image0.geometry.ll_lon:  -71.5537768588526
image0.geometry.lr_lat:  46.8212011291366
image0.geometry.lr_lon:  -71.2329526512783
image0.geometry.meters_per_pixel_x:  1.93985453061563
image0.geometry.meters_per_pixel_y:  1.93985453061563
image0.geometry.projection.ground_points:  (47.014684071854,-71.5197728745253,192.947050529092,WGE) (46.9829294968971,-71.1979597602826,192.947060531786,WGE) (46.8211906932396,-71.2329430206385,192.947059996729,WGE) (46.8529844089776,-71.5537671714541,192.947049994789,WGE)
image0.geometry.projection.image_points:  (0.5,0.5) (13783.5,0.5) (13783.5,8712.5) (0.5,8712.5)
image0.geometry.projection.type:  ossimBilinearProjection
image0.geometry.target_rrds:  0
image0.geometry.tie_point_lat:  47.0146945040848
image0.geometry.tie_point_lon:  -71.5197825978
image0.geometry.type:  ossimImageGeometry
image0.geometry.ul_lat:  47.0146945040848
image0.geometry.ul_lon:  -71.5197825978
image0.geometry.ur_lat:  46.9829399313742
image0.geometry.ur_lon:  -71.1979694267986
image0.lr_x:  13783
image0.lr_y:  8712
image0.number_decimation_levels:  1
image0.number_input_bands:  2
image0.number_lines:  8713
image0.number_output_bands:  2
image0.number_samples:  13784
image0.radiometry:  16-bit signed
image0.type:  ossimTiffTileSource
image0.ul_x:  0
image0.ul_y:  0
number_entries:  1



How can I proceed?



2015-11-24 14:11 GMT+01:00 [hidden email] <[hidden email]>:
Hi Martina,

First thing, you need a plugin.

In svn:
ossim_plugins/ossim

In git:
ossim_plugins/cnes

Then see if you are picking up the correct model.  Do ossim-info on your data.  We can take it from there...

Take care,
Dave



On 11/24/2015 06:57 AM, Martina Di Rita wrote:
Hi everybody, 

I would like to know how can I handle SAR imagery within OSSIM.

I'm trying to test 2 kind of SAR images: RADARSAT and TerraSAR. So far I manage to correctly use ossim-info on RADARSAT imagery (that are .tif file), instead I have some problem in doing that with TerraSAR imagery (that are not .tif rather .xml and .cos).

Furthermore I tried  to use ossim-chipper --op ortho (my final goal is to orthorectify these images): on TerraSAR it doesn't work, on RADARSAT I'm not sure if it correctly merges the 2 image bands in order to compute the amplitude to orthorectify.

Anyone knows how to do this?

Any further suggestion about using SAR imagery within OSSIM is welcome.

Thank you for your kind support, 

Martina 

--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone <a href="tel:%2B%2B39%200644585087" value="+390644585087" target="_blank">++39 0644585087
E-mail [hidden email]




--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone ++39 0644585087
E-mail [hidden email]

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
www.ossim.org
Ossim-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/ossim-developer
Reply | Threaded
Open this post in threaded view
|

Re: SAR imagery managing

Martina Di Rita
It seems that is not picking up the correct model...

Anyway, it is ossible to use ossim-chipper --op ortho on SAR imagery?

Martina

2015-11-25 12:27 GMT+01:00 Martina Di Rita <[hidden email]>:
Hi Dave, 

I have the plug-in you are referring to.

Ossim-info gives me back for an image the following:


image0.band0.max_value:  32767
image0.band0.min_value:  -32767
image0.band0.null_value:  -32768
image0.driver:  ossim_tiff
image0.entry:  0
image0.geometry.decimal_degrees_per_pixel_lat:  9.01937579124763e-06
image0.geometry.decimal_degrees_per_pixel_lon:  8.95975281779772e-06
image0.geometry.decimations:  (1,1)
image0.geometry.gsd:  (1,1)
image0.geometry.image_size:  (13784,8713)
image0.geometry.ll_lat:  -0.078581311581282
image0.geometry.ll_lon:  -73.4887436072343
image0.geometry.lr_lat:  -0.0785945141898716
image0.geometry.lr_lon:  -73.3652512194458
image0.geometry.meters_per_pixel_x:  1
image0.geometry.meters_per_pixel_y:  1
image0.geometry.projection.central_meridian:  -69
image0.geometry.projection.datum:  WGE
image0.geometry.projection.elevation_lookup_flag:  0
image0.geometry.projection.ellipse_code:  WE
image0.geometry.projection.ellipse_epsg_code:  7030
image0.geometry.projection.ellipse_name:  WGS 84
image0.geometry.projection.false_easting_northing:  (500000,0)
image0.geometry.projection.false_easting_northing_units:  meters
image0.geometry.projection.hemisphere:  N
image0.geometry.projection.major_axis:  6378137
image0.geometry.projection.minor_axis:  6356752.3142
image0.geometry.projection.origin_latitude:  0
image0.geometry.projection.original_map_units:  meters
image0.geometry.projection.pcs_code:  32619
image0.geometry.projection.pixel_scale_units:  meters
image0.geometry.projection.pixel_scale_xy:  (1,1)
image0.geometry.projection.srs_name:  EPSG:32619
image0.geometry.projection.tie_point_units:  meters
image0.geometry.projection.tie_point_xy:  (0.5,-0.5)
image0.geometry.projection.type:  ossimUtmProjection
image0.geometry.projection.zone:  19
image0.geometry.target_rrds:  0
image0.geometry.tie_point_lat:  -4.5096879326155e-06
image0.geometry.tie_point_lon:  -73.4887394050139
image0.geometry.type:  ossimImageGeometry
image0.geometry.ul_lat:  -4.5096879326155e-06
image0.geometry.ul_lon:  -73.4887394050139
image0.geometry.ur_lat:  -4.51044561415067e-06
image0.geometry.ur_lon:  -73.3652471319262
image0.lr_x:  13783
image0.lr_y:  8712
image0.number_decimation_levels:  1
image0.number_input_bands:  1
image0.number_lines:  8713
image0.number_output_bands:  1
image0.number_samples:  13784
image0.radiometry:  16-bit signed
image0.type:  ossimTiffTileSource
image0.ul_x:  0
image0.ul_y:  0
number_entries:  1

And for the other:

image0.band0.max_value:  46340
image0.band0.min_value:  0
image0.band0.null_value:  -32768
image0.band1.max_value:  46340
image0.band1.min_value:  0
image0.band1.null_value:  -32768
image0.driver:  ossim_tiff
image0.entry:  0
image0.geometry.decimal_degrees_per_pixel_lat:  1.85605672011629e-05
image0.geometry.decimal_degrees_per_pixel_lon:  2.33485577161292e-05
image0.geometry.decimations:  (1,1)
image0.geometry.gsd:  (1.93985453061563,1.93985453061563)
image0.geometry.image_size:  (13784,8713)
image0.geometry.ll_lat:  46.8529948426282
image0.geometry.ll_lon:  -71.5537768588526
image0.geometry.lr_lat:  46.8212011291366
image0.geometry.lr_lon:  -71.2329526512783
image0.geometry.meters_per_pixel_x:  1.93985453061563
image0.geometry.meters_per_pixel_y:  1.93985453061563
image0.geometry.projection.ground_points:  (47.014684071854,-71.5197728745253,192.947050529092,WGE) (46.9829294968971,-71.1979597602826,192.947060531786,WGE) (46.8211906932396,-71.2329430206385,192.947059996729,WGE) (46.8529844089776,-71.5537671714541,192.947049994789,WGE)
image0.geometry.projection.image_points:  (0.5,0.5) (13783.5,0.5) (13783.5,8712.5) (0.5,8712.5)
image0.geometry.projection.type:  ossimBilinearProjection
image0.geometry.target_rrds:  0
image0.geometry.tie_point_lat:  47.0146945040848
image0.geometry.tie_point_lon:  -71.<a href="tel:5197825978" value="+15197825978" target="_blank">5197825978
image0.geometry.type:  ossimImageGeometry
image0.geometry.ul_lat:  47.0146945040848
image0.geometry.ul_lon:  -71.<a href="tel:5197825978" value="+15197825978" target="_blank">5197825978
image0.geometry.ur_lat:  46.9829399313742
image0.geometry.ur_lon:  -71.1979694267986
image0.lr_x:  13783
image0.lr_y:  8712
image0.number_decimation_levels:  1
image0.number_input_bands:  2
image0.number_lines:  8713
image0.number_output_bands:  2
image0.number_samples:  13784
image0.radiometry:  16-bit signed
image0.type:  ossimTiffTileSource
image0.ul_x:  0
image0.ul_y:  0
number_entries:  1



How can I proceed?



2015-11-24 14:11 GMT+01:00 [hidden email] <[hidden email]>:
Hi Martina,

First thing, you need a plugin.

In svn:
ossim_plugins/ossim

In git:
ossim_plugins/cnes

Then see if you are picking up the correct model.  Do ossim-info on your data.  We can take it from there...

Take care,
Dave



On 11/24/2015 06:57 AM, Martina Di Rita wrote:
Hi everybody, 

I would like to know how can I handle SAR imagery within OSSIM.

I'm trying to test 2 kind of SAR images: RADARSAT and TerraSAR. So far I manage to correctly use ossim-info on RADARSAT imagery (that are .tif file), instead I have some problem in doing that with TerraSAR imagery (that are not .tif rather .xml and .cos).

Furthermore I tried  to use ossim-chipper --op ortho (my final goal is to orthorectify these images): on TerraSAR it doesn't work, on RADARSAT I'm not sure if it correctly merges the 2 image bands in order to compute the amplitude to orthorectify.

Anyone knows how to do this?

Any further suggestion about using SAR imagery within OSSIM is welcome.

Thank you for your kind support, 

Martina 

--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone <a href="tel:%2B%2B39%200644585087" value="+390644585087" target="_blank">++39 0644585087
E-mail [hidden email]




--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone <a href="tel:%2B%2B39%200644585087" value="+390644585087" target="_blank">++39 0644585087
E-mail [hidden email]



--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone ++39 0644585087
E-mail [hidden email]

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
www.ossim.org
Ossim-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/ossim-developer
Reply | Threaded
Open this post in threaded view
|

Re: SAR imagery managing

DBurken@Radiantblue.com
Hi Martina,

Yeah I saw that.  The metadata parsing is tricky for that stuff.  Do a full dump with trace and send to me direct(off the list):

ossim-info -T ossim -d -i -p <your-tif>

Take care,
Dave


On 11/26/2015 06:36 AM, Martina Di Rita wrote:
It seems that is not picking up the correct model...

Anyway, it is ossible to use ossim-chipper --op ortho on SAR imagery?

Martina

2015-11-25 12:27 GMT+01:00 Martina Di Rita <[hidden email]>:
Hi Dave, 

I have the plug-in you are referring to.

Ossim-info gives me back for an image the following:


image0.band0.max_value:  32767
image0.band0.min_value:  -32767
image0.band0.null_value:  -32768
image0.driver:  ossim_tiff
image0.entry:  0
image0.geometry.decimal_degrees_per_pixel_lat:  9.01937579124763e-06
image0.geometry.decimal_degrees_per_pixel_lon:  8.95975281779772e-06
image0.geometry.decimations:  (1,1)
image0.geometry.gsd:  (1,1)
image0.geometry.image_size:  (13784,8713)
image0.geometry.ll_lat:  -0.078581311581282
image0.geometry.ll_lon:  -73.4887436072343
image0.geometry.lr_lat:  -0.0785945141898716
image0.geometry.lr_lon:  -73.3652512194458
image0.geometry.meters_per_pixel_x:  1
image0.geometry.meters_per_pixel_y:  1
image0.geometry.projection.central_meridian:  -69
image0.geometry.projection.datum:  WGE
image0.geometry.projection.elevation_lookup_flag:  0
image0.geometry.projection.ellipse_code:  WE
image0.geometry.projection.ellipse_epsg_code:  7030
image0.geometry.projection.ellipse_name:  WGS 84
image0.geometry.projection.false_easting_northing:  (500000,0)
image0.geometry.projection.false_easting_northing_units:  meters
image0.geometry.projection.hemisphere:  N
image0.geometry.projection.major_axis:  6378137
image0.geometry.projection.minor_axis:  6356752.3142
image0.geometry.projection.origin_latitude:  0
image0.geometry.projection.original_map_units:  meters
image0.geometry.projection.pcs_code:  32619
image0.geometry.projection.pixel_scale_units:  meters
image0.geometry.projection.pixel_scale_xy:  (1,1)
image0.geometry.projection.srs_name:  EPSG:32619
image0.geometry.projection.tie_point_units:  meters
image0.geometry.projection.tie_point_xy:  (0.5,-0.5)
image0.geometry.projection.type:  ossimUtmProjection
image0.geometry.projection.zone:  19
image0.geometry.target_rrds:  0
image0.geometry.tie_point_lat:  -4.5096879326155e-06
image0.geometry.tie_point_lon:  -73.4887394050139
image0.geometry.type:  ossimImageGeometry
image0.geometry.ul_lat:  -4.5096879326155e-06
image0.geometry.ul_lon:  -73.4887394050139
image0.geometry.ur_lat:  -4.51044561415067e-06
image0.geometry.ur_lon:  -73.3652471319262
image0.lr_x:  13783
image0.lr_y:  8712
image0.number_decimation_levels:  1
image0.number_input_bands:  1
image0.number_lines:  8713
image0.number_output_bands:  1
image0.number_samples:  13784
image0.radiometry:  16-bit signed
image0.type:  ossimTiffTileSource
image0.ul_x:  0
image0.ul_y:  0
number_entries:  1

And for the other:

image0.band0.max_value:  46340
image0.band0.min_value:  0
image0.band0.null_value:  -32768
image0.band1.max_value:  46340
image0.band1.min_value:  0
image0.band1.null_value:  -32768
image0.driver:  ossim_tiff
image0.entry:  0
image0.geometry.decimal_degrees_per_pixel_lat:  1.85605672011629e-05
image0.geometry.decimal_degrees_per_pixel_lon:  2.33485577161292e-05
image0.geometry.decimations:  (1,1)
image0.geometry.gsd:  (1.93985453061563,1.93985453061563)
image0.geometry.image_size:  (13784,8713)
image0.geometry.ll_lat:  46.8529948426282
image0.geometry.ll_lon:  -71.5537768588526
image0.geometry.lr_lat:  46.8212011291366
image0.geometry.lr_lon:  -71.2329526512783
image0.geometry.meters_per_pixel_x:  1.93985453061563
image0.geometry.meters_per_pixel_y:  1.93985453061563
image0.geometry.projection.ground_points:  (47.014684071854,-71.5197728745253,192.947050529092,WGE) (46.9829294968971,-71.1979597602826,192.947060531786,WGE) (46.8211906932396,-71.2329430206385,192.947059996729,WGE) (46.8529844089776,-71.5537671714541,192.947049994789,WGE)
image0.geometry.projection.image_points:  (0.5,0.5) (13783.5,0.5) (13783.5,8712.5) (0.5,8712.5)
image0.geometry.projection.type:  ossimBilinearProjection
image0.geometry.target_rrds:  0
image0.geometry.tie_point_lat:  47.0146945040848
image0.geometry.tie_point_lon:  -71.<a moz-do-not-send="true" href="tel:5197825978" value="&#43;15197825978" target="_blank">5197825978
image0.geometry.type:  ossimImageGeometry
image0.geometry.ul_lat:  47.0146945040848
image0.geometry.ul_lon:  -71.<a moz-do-not-send="true" href="tel:5197825978" value="&#43;15197825978" target="_blank">5197825978
image0.geometry.ur_lat:  46.9829399313742
image0.geometry.ur_lon:  -71.1979694267986
image0.lr_x:  13783
image0.lr_y:  8712
image0.number_decimation_levels:  1
image0.number_input_bands:  2
image0.number_lines:  8713
image0.number_output_bands:  2
image0.number_samples:  13784
image0.radiometry:  16-bit signed
image0.type:  ossimTiffTileSource
image0.ul_x:  0
image0.ul_y:  0
number_entries:  1



How can I proceed?



2015-11-24 14:11 GMT+01:00 [hidden email] <[hidden email]>:
Hi Martina,

First thing, you need a plugin.

In svn:
ossim_plugins/ossim

In git:
ossim_plugins/cnes

Then see if you are picking up the correct model.  Do ossim-info on your data.  We can take it from there...

Take care,
Dave



On 11/24/2015 06:57 AM, Martina Di Rita wrote:
Hi everybody, 

I would like to know how can I handle SAR imagery within OSSIM.

I'm trying to test 2 kind of SAR images: RADARSAT and TerraSAR. So far I manage to correctly use ossim-info on RADARSAT imagery (that are .tif file), instead I have some problem in doing that with TerraSAR imagery (that are not .tif rather .xml and .cos).

Furthermore I tried  to use ossim-chipper --op ortho (my final goal is to orthorectify these images): on TerraSAR it doesn't work, on RADARSAT I'm not sure if it correctly merges the 2 image bands in order to compute the amplitude to orthorectify.

Anyone knows how to do this?

Any further suggestion about using SAR imagery within OSSIM is welcome.

Thank you for your kind support, 

Martina 

--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone <a moz-do-not-send="true" href="tel:%2B%2B39%200644585087" value="&#43;390644585087" target="_blank">++39 0644585087
E-mail [hidden email][hidden email]




--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone <a moz-do-not-send="true" href="tel:%2B%2B39%200644585087" value="&#43;390644585087" target="_blank">++39 0644585087
E-mail [hidden email]



--
Martina Di Rita, PhD Student                               
Geodesy and Geomatics Division   
University of Rome "La Sapienza"
via Eudossiana, 18 - 00184 Rome Italy

Phone ++39 0644585087
E-mail [hidden email]


------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
www.ossim.org
Ossim-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/ossim-developer