[wktraster] Motion to remove PT_16BF from specification

[mloskot]

Recently, Frank and Jorge have pointed that there is no known good reason of supporting PT_16BF (16-bit float-point numeric type) defined in the original specification documents (see RFC1-SerializedFormat and RFC2-WellKnownBinaryFormat. Also, it is unclear of what's the purpose of this type.

I have never seen such a thing before and I'm not sure why it is part of the WKTRaster specification. I would suggest removing it. -  Frank's post

Martin Daly and I, we agree that there is no point to support 16-bit float-point type.

Also, current version (r4326) of WKT Raster declares PT_16BF type as unsupported.

This ticket is to propose (official) removal of PT_16BF type from the WKT Raster specification as well as from the implementation.

Any objections?

[pracine]

I have no problem removing support for PT_16BF. I included it in the original specs without really verifying if there were existing images with this pixel type.

[mloskot]

Fixed (r4476)

I've rebuilt and run tests, but please reopen the ticket if this changeset causes any problems.

[mloskot]

More update to docs (r5861)