[Requests] Proposed Correction to Document 16-009r1 - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight

Bernard Leclerc bernard.leclerc at cae.com
Thu May 26 00:22:03 EDT 2016


PART A


1.       Evaluator: Bernard Leclerc, Senior Technical Specialist, CAE, Montreal, Canada

2.       Submission: Document 16-009r1 - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight


PART B


1.       Requirement: T2DModel Tree Structure Restrictions

2.       Implementation Specification Section number: 6.2.2.1

3.       Criticality: Major

4.       Comments/justifications for changes: During the implementation of T2DModels in applications such as the Image Generator, the Radar, and the Terrain Server, it has been found that the restriction that "Each layer SHALL be composed of exactly one OpenFlight Object node" is too restrictive and unnecessary. We ran into cases where multiple object nodes were necessary to represent a single layer. The restriction forces the creation of multiple layers, each having a single object node. However, these layers are disjoint (not overlapping) and, consequently, could have been processed all at once instead of in sequence.

The proposed text to replace the stated restriction in Requirement 4 is that "Each layer SHALL be composed of zero, one, or more OpenFlight Object nodes".

PART B


1.       Requirement: Internal Structure of T2DModels

2.       Implementation Specification Section number: Figure 6-3

3.       Criticality: Major

4.       Comments/justifications for changes: If the restriction on the structure of layers is changed  then Figure 6-3, Internal Structure of T2DModels, must be updated.

PART B


1.       Requirement: T2DModel Tree Structure

2.       Implementation Specification Section number: 6.2.2

3.       Criticality: Minor

4.       Comments/justifications for changes: The presence of an optional LOD node may pose a problem if multiple object nodes per layer are allowed. The problem is related to the fact that sibling LOD nodes are mutually exclusive (as specified in requirement 26). Accordingly, a layer cannot have multiple LOD nodes as its immediate children; a group node would be necessary to isolate a LOD node from its siblings. However, to keep the structure of T2DModels as simple as possible, and since the LOD node is optional, I would recommend that no LOD node be used when multiple object nodes are necessary to represent a layer.

PART B


1.       Requirement: T2DModel Tree Structure

2.       Implementation Specification Section number: 6.2.2

3.       Criticality: Editorial

4.       Comments/justifications for changes: The last sentence of the section is "Each layer has an optional LOD node followed by a fixed hierarchy of regular OpenFlight Object, Face, and Mesh nodes." It is suggested to remove two words, fixed and regular, to simplify the sentence; especially if the above proposed changes are accepted. The resulting sentence would then be "Each layer has an optional LOD node followed by a hierarchy of OpenFlight Object, Face, and Mesh nodes."


The attached document contains the changes that are proposed here except for the update to Figure 6-3.  All edits have been done with Track Change active.



[cid:image001.jpg at 01D1B6D2.F44D7780]<http://www.cae.com/fr>

Bernard Leclerc, ing./eng.
Spécialiste technique sénior, Ingénierie mondiale du développement
Senior Technical Specialist, Global Development Engineering
T. +1-514-341-2000, 2062   E. bernard.leclerc at cae.com
8585 Cote-de-Liesse, Saint-Laurent, Quebec, Canada, H4T 1G6
[cid:image002.jpg at 01CF1816.30D5AA50]<http://www.twitter.com/CAE_Inc>[cid:image005.jpg at 01CF181D.F77FCDA0]<http://www.flickr.com/cae_inc>[cid:image004.jpg at 01CF1816.30D5AA50]<http://www.youtube.com/user/CAEvideogallery>[cid:image003.jpg at 01CF1816.30D5AA50]<http://www.linkedin.com/company/cae>


AVIS DE CONFIDENTIALITÉ
Ce courriel est destiné exclusivement au(x) destinataire(s) mentionné(s) ci-dessus et peut contenir de l'information privilégiée, confidentielle et/ou dispensée de divulgation aux termes des lois applicables. Si vous avez reçu ce message par erreur ou s'il ne vous est pas destiné, veuillez le mentionner immédiatement à l'expéditeur, effacer ce courriel sans en faire de copie et ne pas divulguer ou transmettre à quiconque ce courriel.

CONFIDENTIALITY NOTICE
This e-mail message is intended only for the above named recipient(s) and may contain information that is confidential. If you have received this message in error or are not the named recipient(s), please immediately notify the sender, delete this e-mail message without making a copy and do not disclose or relay this e-mail message to anyone.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1980 bytes
Desc: image001.jpg
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 859 bytes
Desc: image002.jpg
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 835 bytes
Desc: image003.jpg
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 862 bytes
Desc: image004.jpg
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 859 bytes
Desc: image005.jpg
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 16-009r1_Volume_6_-_OGC_CDB_Rules_for_Encoding_Data_using_OpenFlight_BP_.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 4356213 bytes
Desc: 16-009r1_Volume_6_-_OGC_CDB_Rules_for_Encoding_Data_using_OpenFlight_BP_.docx
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20160526/2fb3a568/attachment-0001.docx>


More information about the Requests mailing list