[Requests] Comments on 3D Tiles 1.0 (18-053)

Stephane Garcia Stephane.Garcia at ign.fr
Wed Aug 1 04:12:37 EDT 2018


PART A

1. Evaluator:
Dimitri Sarafinof
dimitri.sarafinof at ign.fr

2. Submission: [OpenGIS Project Document Number, Name]
3D Tiles 1.0 (18-053)

PART B

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
General

3. Criticality: [Major, Minor, Editorial, etc.]
Editorial

4. Comments/justifications for changes: [Comments]
Add Scope, Conformance, References and Terms and Definitions + Annex A (ATS) sections in order to follow OGC standards template (and provide a clearer document)

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
General

3. Criticality: [Major, Minor, Editorial, etc.]
Editorial

4. Comments/justifications for changes: [Comments]
The Introduction section is a technical statement section, and this document is missing a "real" (as in OGC standards) Introduction statement providing an overview of the key features of the standard.

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
General

3. Criticality: [Major, Minor, Editorial, etc.]
Technical

4. Comments/justifications for changes: [Comments]
Is a Tile set equivalent to the Tile Matrix Set (of candidate standard TMS)? Consider to explain the relationship, if any.

Note 1: There should be only one Tile definition for all OGC standards
Note 2: There should be some harmonization of Tile-related standards in the OGC.

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
General

3. Criticality: [Major, Minor, Editorial, etc.]
Technical

4. Comments/justifications for changes: [Comments]
Identify requirements (requirements identification is not totally clear) and consider defining the tests required to be conformant to 3D Tiles.

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
1.6

3. Criticality: [Major, Minor, Editorial, etc.]
Editorial

4. Comments/justifications for changes: [Comments]
What is culling? frustrum culling? (please clarify or provide definition)

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
1.7.1

3. Criticality: [Major, Minor, Editorial, etc.]
Editorial

4. Comments/justifications for changes: [Comments]
Title 'A tileset with transforms an external tileset with transforms' is unclear. Is the 'an' an 'and'?

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
1.6 + 1.7.2

3. Criticality: [Major, Minor, Editorial, etc.]
Technical

4. Comments/justifications for changes: [Comments]
Geometric error + relation to SSE (and HLOD): Consider to add some clarification on handling Geometric error (and HLOD if any) or implementation example in order to facilitate the life of implementers (or make it workable).

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
Section 1.6 and following

3. Criticality: [Major, Minor, Editorial, etc.]
Editorial

4. Comments/justifications for changes: [Comments]
A link is expected for the Geometric error text, anywhere when it's used

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
Section 1.7.2

3. Criticality: [Major, Minor, Editorial, etc.]
Technical

4. Comments/justifications for changes: [Comments]
The definition of geometric error given in this paragraph applies only to tile.geometricError and can be extended to root.geometricError. BUT this doesn't apply to tileset.geometricError, leading to confusions.

It would be clearer to separate each case in this level - a schema for each (root, tile, tileset) - would be welcome.

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
General

3. Criticality: [Major, Minor, Editorial, etc.]
General

4. Comments/justifications for changes: [Comments]
As general remark: globally the concept of geometric error and the relation with the SSE have to be clarified (by a schema?)

1. Requirement: [General, #]
General

2. Implementation Specification Section number: [General, #]
Section 1.6.4

3. Criticality: [Major, Minor, Editorial, etc.]
Technical

4. Comments/justifications for changes: [Comments]
The choice of refinement method: replacement or additive can be clarified here.
Can be improved: A better explanation is expected (p. 28) on how the geometric error drives the refinement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20180801/4d447e2a/attachment.html>


More information about the Requests mailing list