[x3d-public] GeoSpatial Component v4 Proposal rev1

GPU Group gpugroup at gmail.com
Mon Jun 29 10:05:12 PDT 2020


#3 GeoTiles > why wasn't GeoLOD enhanced? Why 2 nodes instead of just one?
An old problem with GeoLOD: it had 4 fields for up to 4 child LODs, by URL.
Cesium Tiles allows any number of children per LOD layer.
web3d uses MFString for url, and doesn't have a field type for
array-of-MFStrings -- so how to do an array of children?
Making child a node, then the node can have a url, and we can have
MFNode children [] in the parent
Cesium Tiles shows the way - that's how they do it.
Such a big change on GeoLOD would be breaking old scenes.
Starting fresh with new node types allows implementers to focus on
harmonizing with cesium tiles.
-Doug

On Mon, Jun 29, 2020 at 8:58 AM GPU Group <gpugroup at gmail.com> wrote:
>
> Any geospatial people on x3d-public? I;d love some comments on
> proposed v4 changes
> Thanks,
> -Doug Sanden
>
> http://dug9.users.sourceforge.net/web3d/temp/geospatial_june28_SRF_Convert_WalkSurface_Nav_Tile_Sys.html
>
> 1) GeoSRF renamed GeoSystemExplicit
> 2) Node signature for GeoSystemNode and GeoSystem
> - not shown: geoNodes would have new SFNode field to take either
> GeoSystem or GeoSystemExplicit
> - alternate approach: GeoSystemExplicit would have a name= field, and
> 'register' and the current geoSystem would refer to it by name like it
> does pre-defined (2007 method)
> 3) GeoTileSet, GeoChildTile  (aka GeoTile) node signatures
> - goal: compatibility with cesium tileset, tiles
> https://github.com/CesiumGS/3d-tiles/tree/master/specification
> 4) GeoViewpoint > navigation types added, benchmarked against
> googleEarth and Cesium
> - walkSurface for bathy; other variants possible, such as listing
> water nodes ...
> 5) GeoConvert
> .. given GC coords, can convert to any surface or vice versa, or
> between surface coord systems, via routing / scripting
>
> Generally: none of this is implemented in freewrl except a variant of
> GeoConvert with different node signature. geo WALK, FLY have been
> working for a few years, and walkSurface coded but not tested.



More information about the x3d-public mailing list