Skip to Content
DocumentationUsageImport

Import Geospatial Datasets

Sensor Data

Point Clouds

To import point cloud files in the LAS, LAZ, E57, or epoint format:

cargo run -r -- import-point-cloud \
    --point-cloud-directory-path ${HOME}/Desktop/project/point_clouds

To import only the octree structure without individual point geometries, add --metadata-only:

cargo run -r -- import-point-cloud \
    --point-cloud-directory-path ${HOME}/Desktop/project/point_clouds \
    --metadata-only

This stores only aggregate cell metrics (point density, acquisition time range) without individual point data, which is useful for lightweight overviews of large campaigns.

If you need to apply a translation offset before importing, use epoint-cli :

cargo install epoint-cli@0.0.1-alpha.13 # replace with the latest version
epoint-cli transform \
  --input-directory ${HOME}/Desktop/project/point_clouds_original \
  --output-directory ${HOME}/Desktop/project/point_clouds \
  --translation 0.0 0.0 0.7551

ROS2 Bags

cargo run -r -- import-rosbag \
    --rosbag-directory-path /path/to/rosbag \
    --ecoord-file-path /path/to/additional/ecoord \
    --start-time-offset 20s \
    --total-duration 4s

To import only the octree structure without individual point geometries, add --metadata-only:

cargo run -r -- import-rosbag \
    --rosbag-directory-path /path/to/rosbag \
    --ecoord-file-path /path/to/additional/ecoord \
    --metadata-only

Semantic Models

To import CityGML datasets into the 3DCityDB running alongside sensordb, use the citydb-tool  Docker container:

docker run --rm --net=host --name citydb-tool -i -t \
    -e "CITYDB_HOST=localhost" \
    -e "CITYDB_PORT=5432" \
    -e "CITYDB_NAME=sensordb" \
    -e "CITYDB_USERNAME=postgres" \
    -e "CITYDB_PASSWORD=changeMe" \
    -v "${HOME}/Desktop/project/citygml:/data" \
  3dcitydb/citydb-tool import citygml --no-appearances \
  2021-04-22_HD21_529_Intersections_CityHall_Ingolstadt_enhanced__v3.gml
Last updated on
Getting StartedProcess