How to Install and Uninstall postgresql-16-pointcloud Package on Kali Linux
Last updated: December 26,2024
1. Install "postgresql-16-pointcloud" package
Please follow the guidelines below to install postgresql-16-pointcloud on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
postgresql-16-pointcloud
Copied
2. Uninstall "postgresql-16-pointcloud" package
Please follow the step by step instructions below to uninstall postgresql-16-pointcloud on Kali Linux:
$
sudo apt remove
postgresql-16-pointcloud
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the postgresql-16-pointcloud package on Kali Linux
Package: postgresql-16-pointcloud
Source: pgpointcloud (1.2.5-1)
Version: 1.2.5-1+b1
Installed-Size: 473
Maintainer: Debian PostgreSQL Maintainers
Architecture: amd64
Depends: libc6 (>= 2.14), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4)
Size: 111180
SHA256: e6abda3ec33146ae617a130151bfeb446d44e7e926b6b59155e952644e765a0e
SHA1: dfb705651df64e5a8ad7607d302b9bdc848f7751
MD5sum: ef26413f2b9e9303e9c9e8d32ca0e663
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.
Description-md5:
Homepage: https://github.com/pgpointcloud/pointcloud
Section: database
Priority: optional
Filename: pool/main/p/pgpointcloud/postgresql-16-pointcloud_1.2.5-1+b1_amd64.deb
Source: pgpointcloud (1.2.5-1)
Version: 1.2.5-1+b1
Installed-Size: 473
Maintainer: Debian PostgreSQL Maintainers
Architecture: amd64
Depends: libc6 (>= 2.14), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4)
Size: 111180
SHA256: e6abda3ec33146ae617a130151bfeb446d44e7e926b6b59155e952644e765a0e
SHA1: dfb705651df64e5a8ad7607d302b9bdc848f7751
MD5sum: ef26413f2b9e9303e9c9e8d32ca0e663
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.
Description-md5:
Homepage: https://github.com/pgpointcloud/pointcloud
Section: database
Priority: optional
Filename: pool/main/p/pgpointcloud/postgresql-16-pointcloud_1.2.5-1+b1_amd64.deb