[postgis-users] Integer geometry type

[Paul Ramsey]

... and should be spitting out results over the next few months as it
is a priority and funded.

P.

On Wed, Jan 16, 2013 at 3:34 PM, Paul Ramsey <pramsey at opengeo.org> wrote:
> Development work in this vein is ongoing
>
> https://github.com/pramsey/pointcloud
>
> On Wed, Jan 16, 2013 at 1:49 PM, Bruce Rindahl <bruce.rindahl at gmail.com> wrote:
>> I am currently building a large PostGIS database of lidar data and going
>> through several performance tweaks to make 1.5 billion records respond
>> better.  One of the big ones was to convert the z data by multiplying by 100
>> and storing it as an integer instead of a double (I know - pretty obvious).
>> The resulting reduction in storage space is significant as is query
>> performance.  The x and y values are stored as a point value in a geometry
>> type which i believe is stored like two double precision values.  Would it
>> be possible to specify a special geometry type using integer values instead
>> of doubles?  You could either add a factor (and a special SRID) or just
>> round the values (possible in my case - are the lidar points really accurate
>> to less than a foot?).  D3.js is doing something very similar to this in its
>> topoJSON format.
>> How much brain damage would this cause?  Just thinking out loud...
>> Bruce
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>>