[postgis-devel] [WKTRaster] Setting properties on a raster

[Pierre Racine]

No problem Mateusz. I think it is a good idea and as you could see I agreed with this change with Zwarg...

Pierre

>-----Original Message-----
>From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
>bounces at postgis.refractions.net] On Behalf Of Mateusz Loskot
>Sent: 23 février 2010 10:17
>To: PostGIS Development Discussion
>Subject: Re: [postgis-devel] [WKTRaster] Setting properties on a raster
>
>Pierre Racine wrote:
>> David Zwarg wrote:
>> >There is no ST_GeoReference method (currently), which is in the 0.1.6d
>> >spec.  However, there is an ST_gdalgeotransform and an
>> >ST_esriworldfile method.  Are these alternate/vendor specific
>> >implementations, and ST_GeoReference is just eerily similar, or should
>> >one of them be renamed?  I was also thinking about writing the setter,
>> >but wanted to make sure I wasn't stepping on ML's toes -- the task is
>> >assigned to him on the planning page.
>>
>> ST_esriworldfile() and ST_gdalgeotransform() are replacement for
>> ST_GeoReference().
>>
>> There should probably be two different setters: one the ESRI way, one
>> the GDAL way. The difference between the two is only that one uses the
>> upper left CORNER and the other one the upper left CENTER.
>
>Pierre,
>
>Yesterday during talk with David, I suggested to refactor the two functions
>ST_esriworldfile() and ST_gdalgeotransform() back to single function
>ST_GeoReference and control output with parameters. I didn't mean to
>apply this idea straight away, but to go through spec-level first, of course.
>
>Best regards,
>--
>Mateusz Loskot
>Senior Programmer, Cadcorp
>http://www.cadcorp.com
>****************************************************************************
>This email is confidential and may be privileged and should not be used, read
>or copied by anyone who is not the  original intended recipient. If you have
>received this email in error  please inform the sender and delete it from
>your mailbox or any other storage mechanism. Unless specifically stated,
>nothing in this email constitutes an offer by Cadcorp and Cadcorp does not
>warrant that any information contained in this email is accurate.
>Cadcorp cannot accept liability for any statements made which are clearly the
>sender's own and not expressly made on behalf of Cadcorp or one of its agents.
>Please rely on your own virus check. No responsibility is taken by Cadcorp
>for any damage arising out of any bug or virus infection.
>****************************************************************************
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-devel