Supported file formats

Image

Following image file formats are supported: jpeg, png, bmp.

3D point cloud

PCD (Point Cloud Data)

Version 0.7 of the PCD format is supported. PCD files can either be ASCII-encoded or binary files. The PCD files should contain at least x, y, and z coordinate fields. Optionally, you can supply an intensity or an RGB field. These fields are used for setting the color of the points. Intensity coloring can be enabled or disabled in the viewer.

Any other fields will be ignored.

Field name	Size (#bytes)	Type	Required
x	4	float
y	4	float
z	4	float
intensity	4	float
rgb	4	float

Please make sure that you supply the values as 32-bit (=4 byte) floats.

Keep in mind that 32-bit floats have limited precision. In fact, only 24 bits can be used to represent the number itself (the significand, excluding the sign bit), or about 7.22 decimal digits. If you want to keep two decimal places, this only leaves 5.22 decimal digits, so the numbers shouldn't be larger than 10^5.22 = 165958.

To avoid rounding problems, it is best practice to subtract the ego position of the first frame from all other ego positions. This way, the first ego position is set to (0, 0, 0) and the subsequent ego positions are relative to (0, 0, 0) . In your export script, you can add the ego position of the first frame back to the object positions.

Binary xyzi(r) (KITTI/nuScenes)

Segments.ai supports the binary point cloud formats used by the KITTI and nuScenes datasets. These formats do not contain a header and have a fixed number of fields. When uploading a sample with point clouds in one of these formats, use binary-xyzi (alias kitti) or binary-xyzir (alias nuscenes) for the type field.

Field name	Size (#bytes)	Type	Required
x	4	float
y	4	float
z	4	float
intensity	4	float
ring index	4	float

PLY (Stanford Triangle Format)

The PLY file format can be used for point clouds by encoding the points as vertices. The PLY header should thus contain a vertex element containing x, y, and z properties and optionally also color or intensity properties. Both binary and ASCII PLY files are supported.

Property name	Type	Required
x	float32
y	float32
z	float32
red	uchar [0, 255]
green	uchar [0, 255]
blue	uchar [0, 255]
intensity	float32

LAS

• LAS support is limited to 3D cuboid and 3D vector task types. It is not supported for 3D point cloud segmentation.

• Unlike other file formats, the uploaded files can only be viewed after the tiling process is completed.

• The LAS file format is currently only recommended for huge point clouds (e.g. merged maps) that cannot be tiled otherwise.

Version 1.4 of the LAS file format is supported. Only uncompressed LAS files are currently supported.

Point clouds can optionally include RGB fields, or an intensity field. If both are defined, the intensity will be discarded.

• For point clouds with RGB colors, make sure to set the point format field to 2.

• For point clouds with intensity values, make sure to set the point format field to 0.

Keep in mind to set the LAS scale/resolution small enough (e.g. 1e-6) to avoid discretization errors.

Property name	Type	Required
X	float32
Y	float32
Z	float32
Red	uint8 [0-255]
Green	uint8 [0-255]
Blue	uint8 [0-255]
Intensity	uint8 [0-255]

Text

When uploading text samples in bulk through the web platform, following file formats are supported:

txt

data.txt

First text sample.
Second text sample.

json

data.json

[
    { "text": "First text sample." },
    { "text": "Second text sample."},
]

jsonl

data.jsonl

{ "text": "First text sample." }
{ "text": "Second text sample." }

csv

data.csv

text
First text sample.
Second text sample.