Changes between Version 1 and Version 2 of Ticket #226


Ignore:
Timestamp:
07/29/09 06:19:14 (15 years ago)
Author:
mloskot
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #226 – Description

    v1 v2  
    1 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 and RFC2-WellKnownBinaryFormat]. Also, it is unclear of what's the purpose of this type.
     1Recently, 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.
    22
    33 ''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]