[postgis-devel] Regarding Raster RFC2 edit (r16452)

[Bborie Park]

Apologies for not being more transparent as I changed the RFC. I was
writing some unit tests for a separate python package built based upon the
WKB RFC and just could not confirm correct behavior. After checking a few
spots (including the old prototypes of WKT Raster and GDAL), i confirmed
that the enum/index used in the RFC was wrong.

Given that the mistake is in the RFC only, I would propose the following
corrective action

1. Leave the fix commit as is
2. Create necessary Trac ticket for trace-ability
3. Update the RFC modify date (version)
4. Send out a message on postgis-users and postgis-devel

Does that sound reasonable?

-bborie

On Sun, Mar 11, 2018 at 2:02 PM, Mateusz Loskot <mateusz at loskot.net> wrote:

> On 11 March 2018 at 20:41, Sandro Santilli <strk at kbt.io> wrote:
> > Bborie, could you please revert your r16452 and discuss here
> > before such a change ?
>
> Sandro,
>
> Bborie's change seems also correct according the earliest prototype
> known as WKT Raster
>
> https://trac.osgeo.org/postgis/browser/spike/wktraster/rt_core/rt_api.h?
> rev=3571#L62
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20180313/d7d05dff/attachment.html>