[Gdal-dev] Support for transforming between pixel/line raster space, and projection coordinates space

[Simon Perkins]

If I understand, you're proposing elevating the GeoTransform to the 
status of a full class instead of just an array of doubles? And then 
adding methods to do useful things like convert from pixel/line to 
geocoords?

I wouldn't have any personal objections to that, though it's not too 
hard to create your own class that wraps the array and adds the 
functionality you need.

Is this something that would be added at the SWIG interface level? i.e. 
the C interface would be unchanged? For all SWIG languages or just C++? 
I imagine there's quite a lot of SWIG code out there that expects an 
array of numbers, so one would have to come up with a new method name, I 
would think.

Cheers,

Sy


Tamas Szekeres wrote:
> Hi All,
>
> Would it be acceptable to support a separate class for the
> transformation between the pixel/line raster space, and projection
> coordinates space? Currently - at the SWIG API - the Dataset
> GetGeoTransform / SetGeoTransform operates on a double array with 6
> elements containing the affine transformation coefficients. Having an
> own GeoTransform quits a lot of
> headaches and helps centralizing the code of calculating the xy 
> coordinates
> in pixel and in projected space. In general, the interface should be
> obvious, clear and self describing.
>
> Having a substantial support on this idea it would be quite an easy to
> proceed with and RFC describing the necessary changes to implement
> this feature.
>
>
> Best regards,
>
> Tamas
> _______________________________________________
> Gdal-dev mailing list
> Gdal-dev at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/gdal-dev