Extract geometry features from 3D point clouds
Content
The project contains the following folders:
- geo3dfeatures contains source code
- docs contains some mardown files for documentation purpose and images
- examples contains some Jupyter notebooks for describing data
- tests;
pytestis used to launch several tests from this folder
Additionally, running the code may generate extra subdirectories in a chosen
data repository (./data, by default).
How to install
This projects runs with Python3, every dependencies are managed through poetry.
Installation from source
$ git clone ssh://git@git.oslandia.net:10022/Oslandia-data/geo3dfeatures.git
$ cd geo3dfeatures
$ virtualenv -p /usr/bin/python3 venv
$ source venv/bin/activate
(venv)$ poetry install
Contribution
See CONTRIBUTING.md.
Run commands
In order to get the available program commands, consider the program help (geo3d -h):
usage: geo3d [-h] {info,sample,index,featurize,cluster,train,predict} ...
Geo3dfeatures framework for 3D semantic analysis
positional arguments:
{info,sample,index,featurize,cluster,train,predict}
info Describe an input .las file
sample Extract a sample of a .las file
index Index a point cloud file and serialize it
featurize Extract the geometric feature associated to 3D points
cluster Cluster a set of 3D points with a k-means algorithm
train Train a semantic segmentation model
predict Predict 3D point semantic class starting from a
trained model
optional arguments:
-h, --help show this help message and exit
Any further CLI documentation may be printed with geo3d <command> -h.
Documentation
Some documentation is available, that describes the set of considered geometric features, the fixtures (i.e. dummy datasets) used for test purpose and a practical pipeline use case:
Examples
The following example has been generated starting from
a CANUPO dataset (file scene.xyz, with 500k points, 50 neighbors and all the features):
Oslandia – 2019-2020
Metadata
Release files for geo3dfeatures 0.4.0.post2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| geo3dfeatures-0.4.0.post2.tar.gz | 26.3 kB | Without provenance | Details for geo3dfeatures-0.4.0.post2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| geo3dfeatures-0.4.0.post2-py3-none-any.whl | Python 3 | none | any | Details for geo3dfeatures-0.4.0.post2-py3-none-any.whl |
Total release size: 115.0 kB
Release files / geo3dfeatures-0.4.0.post2.tar.gz
| Download URL | geo3dfeatures-0.4.0.post2.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53dd4ce2f93d075611efb73b92f38f3b02453108048cf0af4b92cdb92dfc8c0c
|
|
BLAKE2b-256 checksum How to use checksums |
c3a9bcd79dfa680019c28001784b0db1e820411865b20dda5d84b941cadb43d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.5 CPython/3.7.4 Linux/4.19.0-5-amd64
|
Release files / geo3dfeatures-0.4.0.post2-py3-none-any.whl
| Download URL | geo3dfeatures-0.4.0.post2-py3-none-any.whl |
|---|---|
| Size | 88.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc849d30362955ad3fd164ce6b049c594db298093ff223603b9b5701dd68943f
|
|
BLAKE2b-256 checksum How to use checksums |
327ace7d656b3f37ff707858e8b1df9fb76c57e0e0fc5309c43a0e70ee15232a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.5 CPython/3.7.4 Linux/4.19.0-5-amd64
|
Security for geo3dfeatures 0.4.0.post2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.