X3D Model Documentation: NarragansettBayMerged.x3d

  1  <?xml version="1.0" encoding="UTF-8"?>
  2  <!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.3//EN" "https://www.web3d.org/specifications/x3d-3.3.dtd">
  3  <X3D profile='Immersive' version='3.3'  xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance' xsd:noNamespaceSchemaLocation='https://www.web3d.org/specifications/x3d-3.3.xsd'>
  4       <head>
  5            <component level='2' name='Geospatial'/>
  6            <meta name='title' content='NarragansettBayMerged.x3d'/>
  7            <meta name='creator' content='Byounghyun Yoo, Don Brutzman'/>
  8            <meta name='created' content='16 June 2008'/>
  9            <meta name='modified' content='13 September 2021'/>
 10            <meta name='description' content='Merged bathymetry + large-area terrain tiles + coordinate axes.'/>
 11            <meta name='identifier' content='https://savage.nps.edu/Savage/Locations/NarragansettBayRhodeIslandBathymetry/NarragansettBayMerged.x3d'/>
 12            <meta name='generator' content='X3D-Edit, https://savage.nps.edu/X3D-Edit'/>
 13            <meta name='license' content='../../license.html'/>
 14       </head>
<!--
<!-- -->
<!-- to top Index for DEF nodes: DirectionalLights, LightSwitch, NarragansettBayRhodeIslandLarge, ORIGIN, PointLights
-->
 15       <Scene>
 16            <!-- make bathymetry 3m lower than actual, pending TODO ceiling adjustment by Rez within tiles when generating ocean surface -->
 17            <WorldInfo title='NarragansettBayMerged.x3d'/>
 18            <Switch whichChoice='-1'>
 19                 <GeoViewpoint description='Default Viewpoint NarragansettBayBathymetry' orientation='-1 0 0 1.57' position='41.500539965587954 -71.43945518210546 82007.5640554569' containerField='children'>
 20 
                    <!-- GeoOrigin ORIGIN is a DEF node that has 2 USE nodes: USE_1, USE_2 -->
                     <GeoOrigin DEF='ORIGIN' geoCoords='41.5 -71.5 0' geoSystem='"GD"'/>
 21                 </GeoViewpoint>
 22                 <!-- TODO: Determine why a GeoTransform and not a GeoLocation node -->
 23                 <GeoTransform geoCenter='41.487 -71.339 0' translation='0 -3 0' containerField='children'>
 24                      <GeoOrigin USE='ORIGIN'/>
 25                      <!-- local bathymetry archive -->
 26                      <!-- local bathymetry -->
 27                      <Inline   url=' "./tiles/0/newport0-0.x3d" "https://savage.nps.edu/Savage/Locations/NarragansettBayRhodeIslandBathymetry/tiles/0/newport0-0.x3d" '/>
 28                 </GeoTransform>
 29            </Switch>
 30            <!-- also add separate terrain archive, unmodified -->
 31            <Inline DEF='NarragansettBayRhodeIslandLarge'   url=' "../NarragansettBayRhodeIslandLarge/tiles/0/newport0-0.x3d" "https://savage.nps.edu/Savage/Locations/NarragansettBayRhodeIslandLarge/tiles/0/newport0-0.x3d" '/>
 32            <!-- This GeoLocation block shows how to geospatially reference regular nongeospatial shapes -->
 33            <!-- Only required to geo-reference a scene -->
 34            <!-- GeoLocation geoCoords='41.487 -71.339 0' geoSystem='"GD" "WE"'> <Transform scale='100 100 100'> <Inline DEF='CoordinateAxesNSEW' "url='../../Basic/course/CoordinateAxesNSEW.x3d" "CoordinateAxesNSEW.x3d" "https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter03Grouping/CoordinateAxes.x3d'/>" </Transform> note: using the same GeoOrigin throughout all three file sets, to avoid Xj3D problem <GeoOrigin USE='ORIGIN'/> </GeoLocation -->
 35            <!-- TODO experiment: replace PointLights with single geospatially referenced DirectionalLight -->
 36            <Switch DEF='LightSwitch' whichChoice='1'>
 37                 <Group DEF='PointLights'>
 38                      <PointLight location='10000000000 0 0' radius='100000000000000.'/>
 39                      <PointLight location='-10000000000 0 0' radius='100000000000000.'/>
 40                      <PointLight location='0 10000000000 0' radius='100000000000000.'/>
 41                      <PointLight location='0 -10000000000 0' radius='100000000000000.'/>
 42                      <PointLight location='0 0 10000000000' radius='100000000000000.'/>
 43                      <PointLight location='0 0 -10000000000' radius='100000000000000.'/>
 44                 </Group>
 45                 <Transform DEF='DirectionalLights' rotation='1 0 0 0.78'>
 46                      <DirectionalLight/>
 47                      <DirectionalLight direction='0 1 0'/>
 48                      <DirectionalLight direction='0 0 1'/>
 49                      <DirectionalLight direction='-1 0 0'/>
 50                      <DirectionalLight direction='0 -1 0'/>
 51                      <DirectionalLight/>
 52                 </Transform>
 53                 <GeoLocation geoCoords='41.56722223554018 -71.30572987125981 0' containerField='children'>
 54                      <GeoOrigin USE='ORIGIN'/>
 55                      <DirectionalLight direction='0 -1 0' global='true'/>
 56                 </GeoLocation>
 57            </Switch>
 58       </Scene>
 59  </X3D>
<!--
<!-- -->
<!-- to top Index for DEF nodes: DirectionalLights, LightSwitch, NarragansettBayRhodeIslandLarge, ORIGIN, PointLights
-->
X3D Tooltips element index: component, DirectionalLight, GeoLocation, GeoOrigin, GeoTransform, GeoViewpoint, Group, head, Inline, meta, PointLight, Scene, Switch, Transform, WorldInfo, X3D, plus documentation for accessType definitions, type definitions, XML data types, and field types
-->
<!-- Online at
https://savage.nps.edu/Savage/Locations/NarragansettBayRhodeIslandBathymetry/NarragansettBayMergedIndex.html -->
<!-- Version control at
https://gitlab.nps.edu/Savage/Savage/Locations/NarragansettBayRhodeIslandBathymetry/NarragansettBayMerged.x3d -->

<!-- Color-coding legend: X3D terminology <X3dNode  DEF='idName' field='value'/> matches XML terminology <XmlElement  DEF='idName' attribute='value'/>
(Light-blue background: event-based behavior node or statement) (Grey background inside box: inserted documentation) (Magenta background: X3D Extensibility)
-->

to top <!-- For additional help information about X3D scenes, please see X3D Tooltips, X3D Resources, and X3D Scene Authoring Hints. -->