[postgis-devel] [PostGIS] #226: Motion to remove PT_16BF from specification

[PostGIS]

#226: Motion to remove PT_16BF from specification
--------------------------+-------------------------------------------------
  Reporter:  mloskot      |       Owner:  mloskot                     
      Type:  enhancement  |      Status:  assigned                    
  Priority:  high         |   Milestone:                              
 Component:  wktraster    |     Version:  trunk                       
Resolution:               |    Keywords:  wktraster, type, float-point
--------------------------+-------------------------------------------------
Old description:

> 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
> [http://trac.osgeo.org/postgis/browser/spike/wktraster/doc/RFC1-
> SerializedFormat RFC1-SerializedFormat] and
> [http://trac.osgeo.org/postgis/browser/spike/wktraster/doc/RFC2-
> WellKnownBinaryFormat 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.'' -
> [http://lists.osgeo.org/pipermail/gdal-dev/2009-July/021451.html Frank's
> post]
>
> Martin Daly and I, we agree that there is no point to support 16-bit
> float-point type.
>
> This ticket is to propose (official) removal of PT_16BF type from the WKT
> Raster specification as well as from the implementation.
>
> Any objections?

New description:

 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
 [http://trac.osgeo.org/postgis/browser/spike/wktraster/doc/RFC1-
 SerializedFormat RFC1-SerializedFormat] and
 [http://trac.osgeo.org/postgis/browser/spike/wktraster/doc/RFC2-
 WellKnownBinaryFormat 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.'' -
 [http://lists.osgeo.org/pipermail/gdal-dev/2009-July/021451.html 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
 [source:spike/wktraster/rt_core/rt_api.c at 4326#L2262 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?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/226#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS