[x3d-public] GeoSpatial Component v4 Proposal rev1

[GPU Group]

#4 Viewpoint > walkSurface "HIGHEST" "LOWEST" "PRIORITY" and
prioritySurfaces MFNode - what are they for?
One complaint from those working with bathymetry data - its hard to
get under the water surface if the walk mode wants to walk on the
highest surface - which is the water surface.
So being able to choose LOWEST might seem like a simple solution. But
typically the seafloor surface grid extends up the shore to land and
water level grid would end underneath the shore land - in other words
with LOWEST you would find yourself walking on water when on the
shore.
Having a priority surface - for example the seafloor/land grid - would
allow you to walk on one grid consistently.
Another design option. For example grids could be declared as water surface:
MFNode waterSurfaces []
This may have some benefit for automatically generating fog for the
water stack, and some water-surface related rendering.
-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.