You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/changelog.md
+14-34
Original file line number
Diff line number
Diff line change
@@ -2,37 +2,18 @@
2
2
3
3
### features
4
4
5
-
* Splitted .bin files in folders.
6
-
* Introduced the concept of hierarchy and hierarchyStepSize
7
-
*hierarchyStepSize defines how many depth-levels are kept in the same directory (further levels are stored in subdirectories)
8
-
*hierarchy: The .bin files are organized in subdirectories inside ./data. The cloud.js contains only the hierarchy information of the root (which keeps this file small independently of the cloud size). The hierarchy is stored in .hrc files, in packets of 5 bytes. This list of 5-byte packets is a breadth-first traversal of the tree, starting in itself.
9
-
* 1 byte with a mask of this node's children. E.g: 00000011 in the file r.hrc refers to the nodes r0 and r1
10
-
* 4 bytes (unsigned long int) storing the number of points in that node.
5
+
* Update file format to 1.6. (see [Potree File Format](https://github.com/potree/potree/blob/master/docs/file_format.md))
6
+
* Removed hierarchy from cloud.js and store it in smaller chunks.
7
+
* Node-files in ./data are now grouped into a directory hierarchy.
8
+
* RGB, INTENSITY and CLASSIFICATION can be written to the binary format in any order and combination.
9
+
* Added automatic web page generation with the ```--generate-page``` or ```-p``` parameter.
10
+
* Added support for PTX. (Thanks to @chiccorusso)
11
+
* Support for both, 1byte and 2byte colors in LAS or LAZ files.
11
12
12
-
For example, consider the following output of PotreeConverter:
13
-
* ./data/r
14
-
* ./data/r.bin
15
-
* ./data/r.hrc
16
-
*./data/r/r0.bin
17
-
*./data/r/r0.hrc
18
-
*./data/r/r1.bin
19
-
*./data/r/r1.hrc
20
-
21
-
The file ./cloud.js will contain information only about the root:
22
-
"hierarchy": [
23
-
["r", 13291]
24
-
]
25
-
26
-
The file ./data/r.hrc will contain 2 packs of 5-bytes withthe following data:
27
-
* (3,$number_of_points_in_r.bin)
28
-
* (0,$number_of_points_in_r0.bin)
29
-
* (0,$number_of_points_in_r1.bin)
30
-
31
-
* The byte containing the value 3 (00000011 in binary) shows that the root contains the nodes r0 and r1. The tree is traversed breadth-first, so the following two lines correspond to r0 and r1, respectively:
32
-
* r0 has a value 0 for the mask (so no more children)
33
-
* r1 has a value 0 for the mask (so no more children)
34
13
14
+
### bugfixes
35
15
16
+
* Displaying correct number of written points
36
17
37
18
38
19
## 2014.12.30
@@ -46,15 +27,14 @@ The file ./data/r.hrc will contain 2 packs of 5-bytes withthe following data:
46
27
### features
47
28
* Instead of specifying ```-s arg```, spacing can now also be calculated from the diagonal by specifying ```-d arg```.
48
29
spacing = diagonal / arg. This has the advantage that it scales automatically with the extent of the point cloud.
49
-
Thanks to @chiccorusso for this feature.
30
+
(Thanks to @chiccorusso)
50
31
* The default value for the spacing has been changed from ```-s 1``` to ```-d 250```, i.e. spacing = diagonal / 250.
51
32
This seems to work fine for small, as well as large point clouds.
52
-
* Added ```--scale arg``` parameter. This parameter specifies the precision of point coordinates (currently only for
53
-
LAS and LAZ output formats). Previously, this was fixed to 0.01 which gives centimeter precision for
54
-
point clouds with metric coordinate units.
55
-
Thanks to @chiccorusso for this feature.
33
+
* Added ```--scale arg``` parameter. This parameter specifies the precision of point coordinates (currently only for
34
+
LAS and LAZ output formats). Previously, this was fixed to 0.01 which gives centimeter precision for
35
+
point clouds with metric coordinate units.
36
+
(Thanks to @chiccorusso)
56
37
* Added classification, point source ID and return number to LAS and LAZ output.
57
38
58
39
### bugfixes
59
40
* Fixed adaptive point sizes. Sometimes, the point size calculation close to the border of 2 nodes failed. This was because the bounding box was written to the cloud.js in low precision.
0 commit comments