Skip to main content

FZI-AURA SDK

Python tools for downloading, validating, and working with the FZI-AURA dataset.

Compatibility

FZI-AURA SDK 1.0.x supports:

  • FZI-AURA dataset release v1.X
  • FZI-AURA data format v1.2.1
  • Python 3.8+

Installation

Install the SDK from PyPI with:

python -m pip install fzi-aura

The downloader is an optional dependency:

python -m pip install "fzi-aura[download]"

Visualization packages used by the notebooks can be installed with:

python -m pip install "fzi-aura[vis]"

For development from a repository checkout, install the development, downloader, and notebook visualization dependencies together:

python -m pip install -e ".[dev,download,vis]"

Download FZI-AURA

Accept the dataset terms on Hugging Face and sign in:

hf auth login

Download and extract the published keyframe data:

fzi-aura-download /data/fzi-aura

The downloader can select splits, scenes, and data layers. Use --dry-run to inspect a selection before downloading it:

fzi-aura-download /data/fzi-aura \
  --splits train \
  --layers camera_keyframes,lidar_raw_keyframes \
  --dry-run

Data is published in complete scene blocks, so a scene selection may include neighboring scenes from the same block. Re-running the downloader picks up newly published blocks and keeps data that is already present.

Set the dataset root for the examples and notebooks:

export FZI_AURA_ROOT=/data/fzi-aura

See Downloading FZI-AURA for layer selection, archive retention, verification, parallel extraction, and archive mounting.

Quickstart

import os

from fzi_aura import FZIAURADataset

dataset = FZIAURADataset(os.environ["FZI_AURA_ROOT"], split="train")
scene = dataset[0]
frame = scene[0]

print(scene.scene_id, len(scene))
print(frame.timestamp_ns)
print(frame.available_cameras())
print(frame.available_lidars())

FZIAURADataset provides scene-level access. A scene contains lazy frame objects, and sensor data is read when a load_* method is called.

FZIAURADataset
└── FZIAURAScene
    └── FZIAURAFrame

Use dataset.as_frames() when you need a flat frame index across a split:

frames = dataset.as_frames(sample_filter="any_label")
print(len(frames))

Working with the dataset

Frame filters make it easy to select samples with the data required by a task. For example, select a frame with a front camera and motion-compensated LiDAR:

frames = scene.frames(
    sample_filter="sensor_available",
    require_cameras=["front_medium"],
    require_lidars=["top_left"],
)

frame = frames[0]
image = frame.load_camera("front_medium")
cloud = frame.load_lidar("top_left", stage="motion_compensated")

Load 3D boxes from an annotated frame:

box_frame = scene.frames(sample_filter="boxes_3d")[0]
boxes = box_frame.load_boxes(frame="base_link")

Load point-aligned semantic and instance labels:

semantic_frame = scene.frames(
    sample_filter="semantic_lidar",
    require_lidars=["top_left"],
    require_semantics_for=["top_left"],
)[0]

cloud, labels = semantic_frame.load_lidar_semantic_pair(
    "top_left", stage="motion_compensated"
)

Data conventions

  • Sensor data and 3D boxes can be transformed through the ROS base_link frame: X points forward, Y left, and Z up.
  • Raw and motion-compensated LiDAR may contain different point fields. Inspect cloud.field_names before selecting fields.
  • Semantic labels follow LiDAR point order. Use load_lidar_semantic_pair(...) to load and check the pair together.
  • The sample stream runs at 10 Hz and annotations are provided on 2 Hz keyframes. An annotated frame may contain zero boxes.
  • Object IDs identify tracks within one scene.

The notebooks cover calibration, coordinate transforms, camera projection, ego poses, and temporal trajectories with complete examples.

See FZI-AURA data format for the public dataset layout, sample index, sensor files, annotations, calibration, and ego data. Transform directions, temporal alignment, and projection conventions are covered in Coordinate systems and transforms.

Validation

Validate an extracted or selectively downloaded dataset with:

fzi-aura-validate "$FZI_AURA_ROOT"

The validator checks the dataset structure, metadata, installed sensor files, annotations, calibration, and point-label alignment.

Examples and notebooks

Contributing and support

Use GitHub Issues for bugs and usage questions. Pull requests are welcome.

The release process is documented in docs/releasing.md.

License

The SDK is licensed under Apache License 2.0. The FZI-AURA dataset is distributed separately and is subject to its own license. See the FZI-AURA dataset page for dataset licensing information.

Citation

Please use the citation provided in the FZI-AURA dataset card.

Release files for fzi-aura 1.0.1

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

Source distribution (sdist)

Source distribution for fzi-aura 1.0.1
File Size Uploaded
fzi_aura-1.0.1.tar.gz 4.0 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for fzi-aura 1.0.1
File Interpreter ABI Platform
fzi_aura-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 4.1 MB

Release files / fzi_aura-1.0.1.tar.gz

Download URL fzi_aura-1.0.1.tar.gz
Size 4.0 MB
Tags Source
SHA-256 checksum
How to use checksums
37c716153e6e3bdef866c82f65c8322ae1a4eff72a88315567b7e8943743cc92
BLAKE2b-256 checksum
How to use checksums
a1c2668ec8adb4a80c566778f93fe689bb2dfa75a1e41f478cefbacb3286d35f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / fzi_aura-1.0.1-py3-none-any.whl

Download URL fzi_aura-1.0.1-py3-none-any.whl
Size 59.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4ab40c33310f2da7337ced6c90941d7f7b1bf86ad4fd86e573d286532d5d7d22
BLAKE2b-256 checksum
How to use checksums
63dae05d879b7cb369f3bd7d2868585b2345facc843cc6cfb77c6e5f9a0de9fb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.1 This release

2 release files

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