[x3d-public] GeoLODObject.java doesn't produce -rootNode containerField, X3DJSAIL

Don Brutzman brutzman at nps.edu
Wed Jun 20 01:51:23 PDT 2018


[cc: geospatial group]

On 3/21/2017 3:45 AM, yottzumm at gmail.com wrote:
> I can provide examples if necessary.  It currently produces -children for -rootNode

You are correct - thank you for immediately "zooming in" on this issue, John.

I will work on properly integrating rootNode field to the X3D XML Schema annotations and thus X3DUOM and X3DJSAIL, reporting back when corrections are ready.

There are some questionable aspects of GeoLOD design, particularly rootNode and children relationships, that have inhibited broad utilization of the node.  Mike McCann and I have discussed this in some depth here at Web3D 2018.

The path forward will be to
- capture X3D version 3 object design accurately,
- test using examples and regression tests,
- considering whether node design can be further improved,
- apply and evaluate the normalization of GeoLOD node design in X3D version 4.

Interesting there is perhaps nothing intrinsically wrong with GeoLOD node per se.  However, as with a number of nodes, consistency among the abstract interfaces and especially global optimization of design interfaces can be improved.  The containerField issues are simply the manifestation of these differences in parent=child node relationships.

Best of all we are steadily removing historic stumbling blocks that sometimes made debugging a challenge.  Improved GeoLOD reliability is an excellent outcome to strive for.

Looking forward to continuing refinement and improvement of X3D geospatial support.

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman




More information about the x3d-public mailing list