pgpointcloud 1.2.5-1 source package in Ubuntu

Changelog

pgpointcloud (1.2.5-1) unstable; urgency=medium

  * New upstream version.
  * Upload for PostgreSQL 16.
  * Use ${postgresql:Depends}.

 -- Christoph Berg <email address hidden>  Wed, 20 Sep 2023 09:56:17 +0200

Upload details

Uploaded by:
Debian PostgreSQL Maintainers
Uploaded to:
Sid
Original maintainer:
Debian PostgreSQL Maintainers
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc

Downloads

File Size SHA-256 Checksum
pgpointcloud_1.2.5-1.dsc 2.0 KiB e479b59dc4eb1ab61d50dc9c1f9cc2da10bb1756c12581e1adb01799e1fdc2f3
pgpointcloud_1.2.5.orig.tar.gz 340.5 KiB f3924f283345f2da46a971e65f0c6ce602640ecf88a2057293443ec2a7a56774
pgpointcloud_1.2.5-1.debian.tar.xz 3.7 KiB 29315a35995a6911101045410c9c50c17a47740d9e5fdcb4a3ae0d306b2723a9

Available diffs

No changes file available.

Binary packages built by this source

postgresql-16-pointcloud: 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.

postgresql-16-pointcloud-dbgsym: debug symbols for postgresql-16-pointcloud