Skip to content

Commit 2da617f

Browse files
Update README.md
1 parent 8a5da14 commit 2da617f

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -124,12 +124,12 @@ If you keep the the quantization error low enough, it will not affect your resul
124124

125125
Look at the specifications of your sensor and use that value as a reference.
126126

127-
Considering that LiDArs accuracy is usually in the order of **+/- 1 cm** and that the resoultion used in Cloudini is in meters:
127+
Considering that LiDARs accuracy is usually in the order of **+/- 1 cm** and that the resolution used in Cloudini is in meters:
128128

129129
- If the goal of the recorded pointcloud is to do visualization, use a resolution of **0.01 (1 cm)**.
130-
- If you want to record "raw data", a resolution of **0.001 (1mm)** will be more than enough.
131-
- If you are stubborn, and you don't believe a single word I said, use a resolution of **0.0001 (100 microns)**.
132-
But you are being paranoid...
130+
- If you want to record "raw data", a resolution of **0.001 (1 mm)** is the perfect default value.
131+
- If you are stubborn and you don't believe a single word I said, you can go as low as **0.0001 (100 microns)** and still
132+
see significant compression. But you are being paranoid...
133133

134134
### How does it perform, compared to Draco?
135135

0 commit comments

Comments
 (0)