[GRASS-user] [gdal-dev] Working with NTF files

[Markus Metz]

On Tue, Jul 16, 2013 at 12:34 PM, Nikos Alexandris
<nik at nikosalexandris.net> wrote:
> Markus Metz:
>
>> This is mixing different concepts, i.e. import and georeferencing. You
>> can use i.rectify after importing raster data. RPC is not supported by
>> GRASS, thus the gdalwarp approach is most probably the preferred
>> solution. In good GRASS tradition, you could also figure out a
>> reasonable target grid geometry and set this with the corresponding
>> option to gdalwarp.
>
> Ok -- On/Off: would it make sense to be able to say
>
> grass -c Some_NITF_Container /grassdb/Location_Based_On_NITF

You probably mean

grass -c Some_GDAL/OGR_recognized_Container
/grassdb/Location_Based_On_GDAL/OGR_recognized_dataset

which is already possible.

>
> and, if need be, select the SDS that contains/is the SRS, i.e.
>
> grass -c Some_NITF_Container /grassdb/Location_Based_On_NITF sds=2

No, for e.g. hdf and NITF you can specify the sds directly, no need to
have a sds= option.

In general, grass -c <geofile> would use the SRS of the geodataset,
not the SRS of the embedded GCPs or any other geotransform
information. Transformation/georeferencing would be done after import
with i.rectify or before import with gdalwarp.

Markus M