From 361cbdfae30a6657febba08a629ff7ed7b831cc4 Mon Sep 17 00:00:00 2001 From: Daniel Lopez Date: Tue, 28 Nov 2023 18:21:14 +0100 Subject: [PATCH 1/2] Fix typo in doc (matrix field) --- docs/_sources/specification/point_cloud.md.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_sources/specification/point_cloud.md.txt b/docs/_sources/specification/point_cloud.md.txt index 66d5250..718d9ca 100644 --- a/docs/_sources/specification/point_cloud.md.txt +++ b/docs/_sources/specification/point_cloud.md.txt @@ -232,7 +232,7 @@ With those definitions, any parser supporting the full glTF specification is a v | camera | **ignored** || | children | **ignored** || | skin | **ignored** || -| matrix | **supported** | Note that glTF follows a y-up convention. Points in a z-up coordinate system could be written without conversion with the following anti-clockwise rotation around the x-axis [[1, 0, 0, 0], [0, 0, -1, 0],[0, 1, 0, 0], [0, 0, 0 0]] defined here. | +| matrix | **supported** | Note that glTF follows a y-up convention. Points in a z-up coordinate system could be written without conversion with the following anti-clockwise rotation around the x-axis [[1, 0, 0, 0], [0, 0, -1, 0],[0, 1, 0, 0], [0, 0, 0, 1]] defined here. | | rotation | **unsupported** | rotation support is covered by the affine matrix transform| | translation | **unsupported** | translation support is covered by the affine matrix transform | | weights | **ignored** || From 107b8b83182f0ef56f9d59608d1f84b6d636911a Mon Sep 17 00:00:00 2001 From: Daniel Lopez Date: Wed, 29 Nov 2023 14:20:40 +0100 Subject: [PATCH 2/2] specify y-up to z-up rotation as flat list in column-major order --- docs/_sources/specification/point_cloud.md.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_sources/specification/point_cloud.md.txt b/docs/_sources/specification/point_cloud.md.txt index 718d9ca..ddae037 100644 --- a/docs/_sources/specification/point_cloud.md.txt +++ b/docs/_sources/specification/point_cloud.md.txt @@ -232,7 +232,7 @@ With those definitions, any parser supporting the full glTF specification is a v | camera | **ignored** || | children | **ignored** || | skin | **ignored** || -| matrix | **supported** | Note that glTF follows a y-up convention. Points in a z-up coordinate system could be written without conversion with the following anti-clockwise rotation around the x-axis [[1, 0, 0, 0], [0, 0, -1, 0],[0, 1, 0, 0], [0, 0, 0, 1]] defined here. | +| matrix | **supported** | Note that glTF follows a y-up convention. Points in a z-up coordinate system could be written without conversion by specifying a z-up to y-up rotation here. When written in the format required for this property (4x4 column-major matrix) that rotation is [1, 0, 0, 0, 0, 0, -1, 0, 0, 1, 0, 0, 0, 0, 0, 1]. | | rotation | **unsupported** | rotation support is covered by the affine matrix transform| | translation | **unsupported** | translation support is covered by the affine matrix transform | | weights | **ignored** ||