Skip to main content

cnspy_spatial_csv_formats Package

This package holds header and format definitions for CSV-files that hold timestamped 3D spatial information. By spatial

  • 3-DoF relative position (),
  • 3-DoF attitude ,
  • 6-DoF pose (position + orientation represented by quaternions in the [qx qy qz qw] order)
  • 3-DoF position and 3-DoF orientation with uncertainty (position and orientation uncertainties is given by two 3x3 upper triangular covariance matrices). TODO: make default assumption on the uncertainty space
  • 3-DoF position and 3-DoF orientation with typed uncertainty (position and orientation uncertainties is given by two 3x3 upper triangular covariance matrices) [1*].
  • 6-DoF pose with upper triangular pose uncertainty. TODO: make default assumption on the uncertainty space
  • 6-DoF pose with upper triangular pose typed uncertainty [1*] .

[1*] Typed uncertainty: The space/reference frame of the covariance is specified by the "est_err_type" and "err_representation" entry. In case of an error-state estimator, the error representation of the orientation needs to be specified in the CSV files. The estimation error types are defined in the EstimationErrorType file. The error representation type is defined in the ErrorRepresentationType file.

Orientation are represented by quaternions in the [qx qy qz qw] order, meaning that the real-part appears at the end aka JPL order.

File headers are in the first line of a CSV file should not start with a #, followed by a sequence of unique comma separated strings/chars.

It is highly recommended loading the CSV files into a pandas.DataFrame. For convenience, there is a package called cnspy_csv2dataframe that does the conversion using the CSVFormatPose definitions.

Note

The CSVFormatPose.TUM format, got it's name for file format used in the TUM RGB-D benchmark tool. Noticeable, is that the order of quaternion is non-alphabetically ([q_x,q_y,q_z, q_w] instead of [q_w, q_x, q_y, q_z]), meaning that first comes the imaginary part, then the real part, but this is just a matter of taste and definition! To be backward compatible with older/other tools (TUM RGB-D benchmark tool, rpg_trajectory_evaluation, etc.), we follow this non-alphabetically order! Note that the rpg_trajectory_evaluation framework is based on space-separated *.txt trajectory files, meaning that these files cannot be directly processed in the current framework as the file header cannot be interpreted correctly. Support may be added in future.

Installation

Install the current code base from GitHub and pip install a link to that cloned copy

git clone https://github.com/aau-cns/spatial_csv_formats.git
cd spatial_csv_formats
pip install -e .

or the official package via

pip install cnspy-spatial-csv-formats

Dependencies

It is part of the cnspy eco-system of the cns-github group.

License

Software License Agreement (GNU GPLv3 License), refer to the LICENSE file.

Sharing is caring! - Roland Jung

Metadata

Release files for cnspy-spatial-csv-formats 0.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cnspy-spatial-csv-formats 0.2.2
File Size Uploaded Provenance Actions
cnspy_spatial_csv_formats-0.2.2.tar.gz 21.6 kB Without provenance Details for cnspy_spatial_csv_formats-0.2.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cnspy-spatial-csv-formats 0.2.2
File Interpreter ABI Platform Actions
cnspy_spatial_csv_formats-0.2.2-py3-none-any.whl Python 3 none any Details for cnspy_spatial_csv_formats-0.2.2-py3-none-any.whl

Total release size: 46.4 kB

Release files / cnspy_spatial_csv_formats-0.2.2.tar.gz

Download URL cnspy_spatial_csv_formats-0.2.2.tar.gz
Size 21.6 kB
Tags Source
SHA-256 checksum
How to use checksums
7d7166385edceaee1b041b4f7c5a96eee425550d7a08fcd488c5d77fd23f968a
BLAKE2b-256 checksum
How to use checksums
8998bfcf53284a8b831300ec9fb1ffbf5a8b15bef656d02bdd399d3290afd716
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.8.10

Release files / cnspy_spatial_csv_formats-0.2.2-py3-none-any.whl

Download URL cnspy_spatial_csv_formats-0.2.2-py3-none-any.whl
Size 24.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c2ccf70d6eefc7cba8989c4f08c29a376eb6ca8cfd3ccf9786819877346b13a5
BLAKE2b-256 checksum
How to use checksums
fd95915b596d9e10e39a4f05ade61761801cc2c53df191cd53beeeda8b9104bd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.8.10

Security for cnspy-spatial-csv-formats 0.2.2

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page