Package: postgresql-10-pointcloud
Source: pgpointcloud
Version: 1.2.5-1.pgdg20.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 354
Depends: libc6 (>= 2.14), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4)
Homepage: https://github.com/pgpointcloud/pointcloud
Priority: optional
Section: database
Filename: pool/main/p/pgpointcloud/postgresql-10-pointcloud_1.2.5-1.pgdg20.04+1_amd64.deb
Size: 54728
SHA256: 55d5fdcb26217d78e33b69f8eff6b5ec8f68ae906e6717fa480b306a2197a2ad
SHA1: d632538647f3ea6547c9f91ac568f471166e8d69
MD5sum: d0cfe9024c4d062d7be44e320960e75d
Description: PostgreSQL extension for storing point cloud (LIDAR) data
 LIDAR sensors quickly produce millions of points with large numbers of
 variables measured on each point. The challenge for a point cloud database
 extension is efficiently storing this data while allowing high fidelity access
 to the many variables stored.
 .
 Much of the complexity in handling LIDAR comes from the need to deal with
 multiple variables per point. The variables captured by LIDAR sensors varies
 by sensor and capture process. Some data sets might contain only X/Y/Z values.
 Others will contain dozens of variables: X, Y, Z; intensity and return number;
 red, green, and blue values; return times; and many more. There is no
 consistency in how variables are stored: intensity might be stored in a 4-byte
 integer, or in a single byte; X/Y/Z might be doubles, or they might be scaled
 4-byte integers.
 .
 PostgreSQL Pointcloud deals with all this variability by using a "schema
 document" to describe the contents of any particular LIDAR point. Each point
 contains a number of dimensions, and each dimension can be of any data type,
 with scaling and/or offsets applied to move between the actual value and the
 value stored in the database. The schema document format used by PostgreSQL
 Pointcloud is the same one used by the PDAL library.