I would think it makes sense to return these two fields as metadata,
specifically IGEOLO, since IGEOLO might not be returned as a geotransform (such
as in the case when BlockA or other higher precision georeferencing is
available).
-- Dan Greve
> Date: Tue, 16 Dec 2008 12:01:05 -0500
> From: [email protected]
> To: [email protected]
> Subject: Re: [gdal-dev] NITF Header data
> CC: [email protected]
>
> Christiaan Janssen wrote:
> > Does anyone know if it is possible to access any more of the NITF
> > header data than what is currently listed in the GDAL dataset metadata?
> > There are a number of fields that I have noticed missing, namely ICORDS
> > & IGEOLO that I could really use. I realize that these are image
> > subheader components but it would seem to make sense that a GDAL dataset
> > represents a single NITF subimage and that it would contain the subimage
> > specific metadata. Any help is greatly appreciated, thanks.
>
> Christiaan,
>
> The IGEOLO and ICORDS data are not normally returned as NITF specific
> metadata because they are transformed into a generic geotransform and
> coordinate system definition.
>
> If it is particularly useful, they could also be returned in raw form as
> metadata items.
>
> Best regards,
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up | Frank Warmerdam, [email protected]
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush | Geospatial Programmer for Rent
>
> _______________________________________________
> gdal-dev mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
