Selon cobalto :
> These NITFs contain RPCs, so I mostly am unconcerned with the geotransform,
> exact or approximated. However, proper interpretation of the RPCs requires
> knowledge of the projection reference. In these cases, it seems somewhat
> circuitous to look for a projection reference amo
balto"
Subject: [gdal-dev] Re: GetProjectionRef() difference 1.8 vs 1.7.2
Date: 15 פברואר 2011 03:29
> You can still force compute an approximate
> geotransform by calling GDALGCPsToGeoTransform( nGCPCount, psGCPs,
> adfGeoTransform, TRUE ). And the projection can i
> You can still force compute an approximate
> geotransform by calling GDALGCPsToGeoTransform( nGCPCount, psGCPs,
> adfGeoTransform, TRUE ). And the projection can indeed be fetched by
> GDALGetGCPProjection() when GCPs are returned instead of a geotransform.
>
These NITFs contain RPCs, so
Le lundi 14 février 2011 21:40:36, cobalto a écrit :
> I'm hesitant to post the entire gdalinfo dump, but below are the changed
> sections for nitf_im:0:myfile.nitf between v1.7.2 and v1.8.0 of gdalinfo
> (Win64 w/ kakadu). Does this help? It seems like the info I'm after is now
> in the GCP Projec
I'm hesitant to post the entire gdalinfo dump, but below are the changed
sections for nitf_im:0:myfile.nitf between v1.7.2 and v1.8.0 of gdalinfo
(Win64 w/ kakadu). Does this help? It seems like the info I'm after is now
in the GCP Projection rather than the coordinate system. Does this provide
an
