Docstoc

BS Contact Geo

Document Sample
BS Contact Geo Powered By Docstoc
					                                BS Contact Geo




               Documentation of geo nodes supported




Revision:         2
Date:             28 Dec 2006



Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de
Index
The document describes the geo nodes supported by BS Contact Geo in addition to the
nodes and features supported by BS Contact VRML / X3D. Please see latest release
information at: www.bitmanagement.de/products/bs_contact_vrml.de.html#Contact7.0

     1. Encoding of Raster data...........................................................................1

     2. Encoding of Vector data...........................................................................2

     3. X3D Geospatial nodes..............................................................................3

     4. GEO Coordinate Transform.....................................................................3

     5. GEO Navigation.........................................................................................4

     6. Node Reference.........................................................................................5
         6.1. GeoSphere................................................................................................................ 5
         6.2. GeoMap..................................................................................................................... 7
         6.3. GeoSystem................................................................................................................ 8
         6.4. GeoLocation.............................................................................................................. 10
         6.5. GeoElevationGrid...................................................................................................... 11
         6.6. GeoTouchSensor....................................................................................................... 13
         6.7. GeoPositionInterpolator............................................................................................. 15


     7. BSTile data formats..................................................................................17
          8.1. Uncompressed encodings........................................................................................ 17
          8.2. Compressed encodings............................................................................................ 17
          8.3. Elevation encodings................................................................................................. 17


     8. Links and References................................................................................18

     9. Contact........................................................................................................18




Bitmanagement Software GmbH             Geschäftsführer                       Deutsche Bank 24 AG                Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                       Peter Schickel                        BLZ 700 700 24                     Fax. 0049 (0)8151 97170-9
82335 Berg                              AG München HRB 143734                 Kto 1530211                        http://www.bitmanagement.de
Germany                                 UST ID DE 224651645                                                      mail: info@bitmanagement.de
                                                                                                                1




                          Example view of 500 m raster data set with vector information.




 1. Encoding of Raster data
Raster data for the whole earth globe or detail satellite image is stored in BSTile File
format. The node GeoSphere dynamically tessellates an Earth Ellipsoid and applies
Raster Tiles at the level of detail needed. The native BSTile Format is a special image
format that enables the storage of an precomputed mip-mapped image pyramid. It allows
the progressive loading of extremely high resolution textures, thereby overcoming video
card limitations (of at most 4096 × 4096) and drastically improving scene initialization
times and real-time performance. As the name suggests, large images are divided up into
smaller, seamless tiles of a recommend size of 512 × 256 pixels (or some other power of
2) and these are loaded by the application only when required. The loading of tiles is done
in an background thread, an a in-memory cache allows seamless browsing of the data.




Bitmanagement Software GmbH      Geschäftsführer          Deutsche Bank 24 AG     Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                Peter Schickel           BLZ 700 700 24          Fax. 0049 (0)8151 97170-9
82335 Berg                       AG München HRB 143734    Kto 1530211             http://www.bitmanagement.de
Germany                          UST ID DE 224651645                              mail: info@bitmanagement.de
                                                                                                           2




                                          BSTile subdivision scene

A conversion tool has been created to convert from RAW (BIN), jpg, j2k, png, bmp,tiff and
dds. BSTile images can be exactly placed on a GeoSphere by specifying a range of GDC
geo coordinates. In addition to image raster data GeoSphere also supports elevation
raster data stored in a 16Bit gray scale BSTile image. Seams between tiles are
automatically closed. Depending on quality and performance criteria the subdivision
criteria can be specified and changed dynamically by the author.



 2. Encoding of Vector data

The GeoMap node supports the overly of projected vector data like polylines, markers and
text onto the earth. One supported format are ESRI Shape file format. The native BSMap
Format stores vector objects into an on demand loaded quad tree splitted binary file and
allows. BSMap currently supports Markers, Polylines, Text, and Text along Splines
primitives. BSMap also supports different scale levels of data. Individual GIS layers can be
toggled on or off and full control is available over color, text sizes, fonts and at what
elevation ranges layers are active.




Bitmanagement Software GmbH   Geschäftsführer          Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel           BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734    Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                            mail: info@bitmanagement.de
                                                                                                          3


 3. X3D Geospatial nodes
The Web3D Consortium has defined a Geospatial component.
Please see http://www.web3d.org/x3d/specifications/ISO-IEC-19775-
X3DAbstractSpecification/Part01/components/geodata.html


The following Nodes from this component are supported.
GeoLocation                    to place an 3D model at a geo referenced location
GeoElevationGrid               to specify an 3D height grid in Geo coordinates
GeoPositionInterpolator to interpolate between Geo coordinates
GeoTouchSensor                 to detect clicks and report positions in Geo coordinates
GeoMetadata                    to annotate data with Geo metadata information


GeoCoordinate, and GeoLOD nodes are in preparation. But we think the concept of BS
GeoSphere and GeoMap dealing with the bulk of geo data is a more performant and
scalable approach.




 4. GEO Coordinate Transform
The GeoSphere and GeoMap nodes are using GDC (latitude, longitude) coordinates.
GDC coordinates are then transformed to cartesian GCC coordinates. These coordinates
are then transformed from double precision to single (float) using a normalization
transform. The Graphics API can only deal with floating point precision. In order to avoid
jitter if navigation from space to a very close spot on the earth this normalization
transformation can be adapted dynamically. Although the X3D Geospatial component
addresses this problem and suggest the use of a relative origin set using an GeoOrigin
node                                    http://www.web3d.org/x3d/specifications/ISO-IEC-19775-
X3DAbstractSpecification/Part01/components/geodata.html#high-precisioncoords
We think adapting the normalization transform dynamically depending on the view is a

Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                               4

better approach. This frees the Author of specifying useful relative origins. However using
the automatic auto normalization transformation, the X3D coordinate system units are
changing dynamically and are not in the default unit meters with 0 0 0 as origin any more.
This means in the auto normalization mode the scene graph must fully use Geo nodes as
root nodes for geometrical data.




 5. GEO Navigation
For spherical Geo-specific navigation modes for "fly" and "examine" special modes for
geographical visualisation of the earth to provide a similar experience for the user as on a
printed map are needed.


Geo-Examine:                  North is always up. The velocity is reduced once closer to the poles.
Geo-Fly:                      Always fly on the "great circle" of the geoid (sphere).


The geo examine mode is a more natural way of navigating the globe - speed is
dependent on elevation and vertical movement is restricted from pole to pole (-90S to
+90N), thereby avoiding the camera "roll" associated with the standard examine mode.
Additional browser methods have also been created for the programmatic setting of geo
location (via double floating point precision latitude, longitude and elevation). A smooth
geo-transition from one set of coordinates to another is generated.
The geo-fly mode enables users to fly over global terrain.




Bitmanagement Software GmbH        Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                  Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                         AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                            UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                                  5


 6. Node Reference
This is the list of nodes supported in BS Contact Geo. The first two node types are only
available in BS Contact Geo.


6.1. GeoSphere

    GeoSphere : X3DGeometryNode {
     SFBool [in,out] enabled  TRUE
     SFBool [in,out] solid   TRUE

        SFVec3d [in,out] rangeMin      -180.0 -90.0 0        (-∞,∞)
        SFVec3d [in,out] rangeMax       180.0 90.0 0        (-∞,∞)

        SFInt32 [in,out] levelMin   0          (-∞,∞)
        SFInt32 [in,out] levelMax   32         (-∞,∞)
        SFFloat [in,out] deltaMin   0.5        (0,∞)

        SFBool [in,out] zbuffer   TRUE
        SFBool [in,out] zwrite    TRUE
        SFVec2f [in,out] depthBias 0 0          (-∞,∞)

        SFBool [in,out] gridEnabled FALSE
        SFColor [in,out] gridColor 0.5 0.5 0.5           (-∞,∞)
        SFVec2f [in,out] gridSpacing 10.0 10.0             (-∞,∞)


        SFString [in,out] imageMap         ""
        SFInt32 [in,out] imageLevelMax -1                   (-∞,∞)
        SFInt32 [in,out] imageLevelBias -1                  (-∞,∞)
        SFBool [in,out] imageBorder        FALSE

        SFBool [in,out] elevationEnabled TRUE
        SFString [in,out] elevationMap      ""
        SFInt32 [in,out] elevationLevelBias -1              (-∞,∞)
        SFDouble [in,out] elevationScale 1.0                (-∞,∞)
        SFDouble [in,out] elevationClamp -∞                 (-∞,∞)


        SFBool [out]     isLoaded
        SFString [out]   currentImageMap
        SFString [out]   currentElevationMap

        SFVec3f []       bboxCenter 0 0 0       (-∞,∞)
        SFVec3f []       bboxSize   -1 -1 -1   [0,∞) or −1 −1 −1
    }

The GeoSphere renders a Sphere in the longitude latitude range [rangeMin rangeMax].


Bitmanagement Software GmbH      Geschäftsführer              Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                Peter Schickel               BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                       AG München HRB 143734        Kto 1530211           http://www.bitmanagement.de
Germany                          UST ID DE 224651645                                mail: info@bitmanagement.de
                                                                                                          6

For the whole Earth range should be set to -180.0 -90.0 0 and                      180.0 90.0 0 The
sphere is subdivided recursively from level 0 until subdivision step levelMax is reached.
The main tessellation parameter is deltaMin, if the length of the diagonal of the projected
bounding box of a patch is below deltaMin in view space (-1 .. 1) subdivision stops. 0.5
provides a smooth tessellation , 1.0 a coarser tessellation.
The field imageMap specifies the filename of an BSTile image file. At a subdivision level X
the image tiles from level (X+imageLevelBias) are used, or lower ones if the tile is not yet
loaded to memory. imageLevelMax allows to clamp the maximum detail level of the BSTile
filed used. imageBorder allows to fill the border pixel to white, useful for detail image.

An latitude, longitude grid can be enabled with gridEnabled , the spacing in degrees is
gridSpacing, the color is gridColor.


For elevation data if elevationEnabled is TRUE the field elevationMap specifies the
filename of an BSTile image file with greyscale height information. At a subdivision level X
the elevation image tiles from level (X+elevationLevelBias) are used, or lower ones if the
tile is not yet loaded to memory. The elevation values can be clamped at elevationClamp,
e.g. set to 0 for clamping at sear level. The height can be scaled by elevationScale.


By default z buffer testing (zbuffer) and z buffer writing (zwrite) are enabled. For custom
composition of several layers of GeoSphere and GeoMap node by rendering first a smaller
sphere to the z-buffer and then disabling z-write is allowing better z-buffer composition and
voide z-fighting issues.
The Appearance node of the Shape containing a GeoSphere is currently ignored.




Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                                 7


6.2. GeoMap

GeoMap : X3DNode {
    SFBool [in,out] enabled                               TRUE
    SFString [in,out] url                                 ""
    MFString [in,out] layerAttributes        ""

        MFNode [in,out] fontTexture []                             [FontTexture]
        SFNode [in,out] symbolTexture        NULL         [ImageTexture]

        SFString [in,out] labelField                      "TEXT"
        SFString [in,out] labelChars                      ""

        SFBool [in,out] zbuffer                           TRUE
        SFBool [in,out] zwrite                            FALSE


        SFDouble [in,out] scaleMin                        -∞          (-∞,∞)
        SFDouble [in,out] scaleMax                        ∞           (-∞,∞)
        SFDouble [in,out] scaleLevel                      1000        (-∞,∞)


        SFString [in] set_layerAttribute
        SFString [in] set_markedIDs
        SFBool [out] isLoaded

    }

The GeoMap nodes renders Vector data from Shape file or BSMap file. Url specifies the
filename.
layerAttributes sets the initial attributes like visibility color size for lines markes and text.


fontTexture is a set of BS Contact FontTexture nodes to render text in an efficient way.
The field labelChars give the used characters in UTF-8 encoding, this is needed that the
FontTexture nodes can allocated space in the Texture for all used character symbols.
symbolTexture can contain an ImageTexture node containing the set of used symbols.


Example layer attributes for a Layer LineDefiniteInternationalBoundary:

layerAttributes [
      "LineDefiniteInternationalBoundary.enabled=true",
      "LineDefiniteInternationalBoundary.color=0.400 0.000 0.400",
      "LineDefiniteInternationalBoundary.alpha=1.000",

Bitmanagement Software GmbH       Geschäftsführer            Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                 Peter Schickel             BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                        AG München HRB 143734      Kto 1530211           http://www.bitmanagement.de
Germany                           UST ID DE 224651645                              mail: info@bitmanagement.de
                                                                                                          8

          "LineDefiniteInternationalBoundary.level=1",
          "LineDefiniteInternationalBoundary.lineEnabled=true",
          "LineDefiniteInternationalBoundary.linetype=CONTINUOUS",
          "LineDefiniteInternationalBoundary.symbol=4",
          "LineDefiniteInternationalBoundary.scale=0.00 2500.00",
          "LineDefiniteInternationalBoundary.textEnabled=true",
          "LineDefiniteInternationalBoundary.textItalic=false",
          "LineDefiniteInternationalBoundary.textAlign=BLOCK",
          "LineDefiniteInternationalBoundary.textFontIndex=0",
          "LineDefiniteInternationalBoundary.textSize=0.0100",
          "LineDefiniteInternationalBoundary.pointSize=0.0100"
]



    6.3. GeoSystem

Once the spatial reference frame has been defined, a single geographic coordinate is
specified as an SFVec3D. The meaning of each component value depends upon the
particular spatial reference frame that was defined via the geoSystem field in the same
node. Given the following geoSystem definitions, the meaning of each component is
defined as follows.

      •   GD: (<latitude>, <longitude>, <elevation>) or (<longitude>, <latitude>, <elevation>).
          The order of latitude and longitude is controlled by the geoSystem field. If
          "latitude_first" is specified, the order is latitude then longitude. If "longitude_first" is
          specified, the order is longitude then latitude. If neither is specified, "latitude_first" is
          the default. Latitude and longitude are given in units of degrees. Latitude is in the
          range −90..+90, and longitude can be in the range −180..+180 or 0..360 (0 deg
          longitude is the same point in both cases). Longitudinal values are relative to the
          Greenwich Prime Meridian. Elevation is given in units of metres above the ellipsoid
          (the default) or above the geoid.

          Example for GD [“GD”,”WG”,”longitude_first”]

          The first parameter is obligation and defines the spatial frame, the second
          parameter is optional and defines the ellipsoid and the last parameter is optional too
          and defines if the order is latitude or longitude is.

Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                                9

     •   UTM: (<northing>, <easting>, <elevation>) or (<easting>, <northing>, <elevation>).
         The order of northing and easting is controlled by the geoSystem field. If
         "northing_first" is specified, the order is northing then easting. If "easting_first" is
         specified, the order is easting then northing. If neither is specified, "northing_first" is
         the default. Elevation is always specified third. Northings, eastings, and elevation
         are all given in units of metres. The zone of the coordinate, and whether it is in the
         southern hemisphere, are defined in the geoSystem string. Elevation is given with
         reference to the ellipsoid (the default) or the geoid.

         Example for UTM [“UTM”,”Z1”,”N”,”WG”,”easting_first”]

         The first three parameter are obligation. The defines the spatial frame, the second
         parameter defines the zone and the third parameter defines the hemisphere. The
         last two parameter are optional, the first parameter of the optional is for defining the
         ellipsoid and the second is for the order of the easting and northing.

     •   GC: (<x>, <y>, <z>). These values are all given in units of metres. The coordinate
         represents an offset from the center of the planet, based upon the WGS84 ellipsoid.
         The z-axis passes through the poles while the x-axis cuts through the
         latitude/longitude coordinate (0,0) degrees.

         Example for GC: [“GC”,”WG”]

         This system has only two parameters. The first parameter is obligation and defines
         the spatial frame, the second parameter defines the ellipsoid.

                              List of supported ellipsoid and there abbreviations

                          Abbreviations Ellipsoid name
                          AA                Airy
                          AM                Modified Airy
                          AN                Australian National
                          BN                Bessel 1841 (Namibia)
                          BR                Bessel 1841 (Ethiopia Indonesia...)
                          CC                Clarke 1866
                          CD                Clarke 1880


Bitmanagement Software GmbH       Geschäftsführer           Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                 Peter Schickel            BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                        AG München HRB 143734     Kto 1530211           http://www.bitmanagement.de
Germany                           UST ID DE 224651645                             mail: info@bitmanagement.de
                                                                                                            10

                     Sequel to list of supported ellipsoid and there abbreviations

                          Abbreviations Ellipsoid name
                          EA             Everest (India 1830)
                          EB             Everest (Sabah & Sarawak)
                          EC             Everest (India 1956)
                          ED             Everest (W. Malaysia 1969)
                          EE             Everest (W. Malaysia & Singapore 1948)
                          EF             Everest (Pakistan)
                          FA             Modified Fischer 1960
                          HE             Helmert 1906
                          HO             Hough 1960
                          ID             Indonesian 1974
                          IN             International 1924
                          KA             Krassovsky 1940
                          RF / GRS80     Geodetic Reference System 1980 (GRS 80)
                          SA             South American 1969
                          WD / WGS72     WGS 72
                          WE / WGS84     WGS 84




6.4. GeoLocation

 MFNode [in] addChildren                                 [X3DChildNode]
 MFNode [in] removeChildren                              [X3DChildNode]
 MFNode [in,out] children                []              [X3DChildNode]
 SFVec3d [in,out] geoCoords              000             (-∞,∞)
 MFString []   geoSystem                 ["GD","WE"]     [see 25.2.3]
 SFVec3f []    bboxCenter                000             (-∞,∞)
 SFVec3f []    bboxSize                  -1 -1 -1        [0,∞) or −1 −1 −1


The GeoLocation node provides the ability to georeference any standard X3D model. That
is, to take an ordinary X3D model, contained within the children field of the node, and to
specify its geospatial location. This node is a grouping node that can be thought of as a
Transform node. However, the GeoLocation node specifies an absolute location, not a
relative one, so content developers should not nest GeoLocation nodes within each other.

The geoSystem field is used to define the spatial reference frame and is described in the

Bitmanagement Software GmbH    Geschäftsführer          Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26              Peter Schickel           BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                     AG München HRB 143734    Kto 1530211           http://www.bitmanagement.de
Germany                        UST ID DE 224651645                            mail: info@bitmanagement.de
                                                                                                                         11

node description geoSystem.

The geometry of the nodes in children is to be specified in units of metres in X3D
coordinates relative to the location specified by the geoCoords field. The geoCoords field
should be provided in the format described in geoSystem.

The geoCoords field can be used to dynamically update the geospatial location of the
model; for example, an event could be sent from a GeoPositionInterpolator node.

An example for a simple GeoLocation placed in Las Vegas a red sphere.

         GeoLocation
         {
                  geoSystem["GD","","longitude_first"]
                  geoCoords -115.150763375295 36.109734396373 0
                  children
                  [
                           Shape
                            {
                                 appearance Appearance
                                  {
                                        material Material
                                        {
                                                 diffuseColor 1 0 0
                                        }
                                 }
                                 geometry Sphere         { radius 50000 }
                           }
                  ]
         }




6.5. GeoElevationGrid

The   GeoElevationGrid is useful to display highfields like plateaus, hills and mountains.
Here are the available fields with there specification from the node.

             MFDouble         [in]       set_height
             SFNode           [in,out]   color            NULL
             SFNode           [in,out]   normal           NULL
             SFNode           [in,out]   texCoord         NULL
             SFFloat          [in,out]   yScale           1.0             (0,∞)
             SFBool           []         ccw              TRUE
             SFBool           []         colorPerVertex          TRUE
             SFDouble         []         creaseAngle      0                        (0,∞)


Bitmanagement Software GmbH          Geschäftsführer             Deutsche Bank 24 AG       Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                    Peter Schickel              BLZ 700 700 24            Fax. 0049 (0)8151 97170-9
82335 Berg                           AG München HRB 143734       Kto 1530211               http://www.bitmanagement.de
Germany                              UST ID DE 224651645                                   mail: info@bitmanagement.de
                                                                                                                   12

          SFVec3d             []    geoGridOrigin 0 0 0             (-∞,∞)
          MFString            []    geoSystem     ["GD","WE"]
          MFDouble            []    height        [0 0]                      (0,∞)
          SFBool              []    normalPerVertex TRUE
          SFBool              []    solid         TRUE
          SFInt32             []    xDimension    0                          (0,∞)
          SFDouble            []    xSpacing      1.0                        (0,∞)
          SFInt32             []    zDimension    0                          (0,∞)
          SFDouble            []    zSpacing      1.0                        (0,∞)

The fields color, colorPerVertex, texCoord, normal, and normalPerVertex all have the
same meaning as for ElevationGrid.

The ccw, solid, and creaseAngle fields are commen geometry fields.

The geoSystem field is used to define the spatial reference frame and is described in
geoSystem.

The geoGridOrigin field specifies the geographic coordinate for the south-west corner
(bottom-left) of the dataset. This value should be specified as described in geospatial
coordinates.

The height array contains xDimension × zDimension floating point values that represent
elevation above the ellipsoid or the geoid, as appropriate. These values are given in row-
major order from west to east, south to north. When the geoSystem is GD, xSpacing refers
to the number of degrees of longitude between adjacent height values and zSpacing refers
to the number of degrees of latitude between vertical height values. When the geoSystem
is UTM, xSpacing refers to the number of eastings (metres) between adjacent height
values and zSpacing refers to the number of northings (metres) between vertical height
values.

The yScale value can be used to produce a vertical exaggeration of the data when it is
displayed. By default, this value is 1.0 (no exaggeration). If this value is set greater than
1.0, all heights will appear larger than actual.

Example for a GeoElevationGrid. This example Grid can you find southern of
Hawaii.
         Shape
         {
                  appearance Appearance


Bitmanagement Software GmbH        Geschäftsführer         Deutsche Bank 24 AG       Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                  Peter Schickel          BLZ 700 700 24            Fax. 0049 (0)8151 97170-9
82335 Berg                         AG München HRB 143734   Kto 1530211               http://www.bitmanagement.de
Germany                            UST ID DE 224651645                               mail: info@bitmanagement.de
                                                                                                                13

                  {
                         material Material { diffuseColor 0.700 0.700 0.700 }
                 }
                 geometry GeoElevationGrid
                 {
                         xDimension 4
                         xSpacing 3000
                         zDimension 4
                         zSpacing 3000
                         solid FALSE
                         colorPerVertex TRUE
                         geoGridOrigin 0 0 0
                         yScale 1000
                         geoSystem["UTM","Z5","N","RF", "easting_first"]
                         color Color
                         {
                                  color
                                  [
         0.134 0.543 0 0.132 0.546 0 0.124 0.56 0 0.126 0.558 0 0.136 0.539 0 0.114 0.58 0 0.111 0.584 0
         0.106 0.593 0 0.106 0.593 0 0.104 0.597 0 0.109 0.589 0 0.106 0.594 0 0.119 0.57 0 0.117 0.574 0
         0.091 0.62 0 0.09 0.622 0
                                  ] # color
                         } # color Color
                         height
                         [
                         01230338
                         12481356
                         ] # height
                 } # End of geometry ElevationGrid
         } # End of ElevationGrid Shape




6.6. GeoTouchSensor

          SFString            [in,out] description                  ""
          SFBool              [in,out] enabled                      TRUE
          SFVec3f             [out] hitNormal_changed
          SFVec3f             [out] hitPoint_changed
          SFVec2f             [out] hitTexCoord_changed
          SFVec3d             [out] hitGeoCoord_changed
          SFBool              [out] isActive
          SFBool              [out] isOver
          SFTime              [out] touchTime
          MFString            []     geoSystem                      ["GD","WE"]

A GeoTouchSensor node tracks the location and state of a pointing device and detects
when the user points at geometry contained by the parent group of the GeoTouchSensor.
This node provides the same functionality as a TouchSensor but also provides the ability


Bitmanagement Software GmbH        Geschäftsführer         Deutsche Bank 24 AG    Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                  Peter Schickel          BLZ 700 700 24         Fax. 0049 (0)8151 97170-9
82335 Berg                         AG München HRB 143734   Kto 1530211            http://www.bitmanagement.de
Germany                            UST ID DE 224651645                            mail: info@bitmanagement.de
                                                                                                          14

to return the geographic coordinate under the pointing device.
The description field in the GeoTouchSensor node specifies a textual description of the
GeoTouchSensor node. This may be used by browser-specific user interfaces that wish to
present users with more detailed information about the GeoTouchSensor.

A GeoTouchSensor can be enabled or disabled by sending an event of value TRUE or
FALSE to the enabled field. A disabled GeoTouchSensor does not track user input or send
events.

The geoSystem field is used to define the spatial reference frame for the output format of
the geo coordinates and is described in the node description geoSystem.

The fields hitNormal_changed, hitPoint_changed, hitTexCoord_changed, isActive, isOver,
and touchTime all have the same meaning as in the TouchSensor node.

The hitGeoCoord_changed field is generated while the pointing device is pointing towards
the GeoTouchSensor's geometry, i.e. when isOver is TRUE. It is a field containing the
geospatial coordinate for the point of intersection between the pointing device's location
and the underlying geometry. The value of the geoSystem string defines the spatial
reference frame of the geospatial coordinate. For example, given the default geoSystem
value of "GD", the hitGeoCoord_changed field will be in the format (<latitude> <longitude>
<elevation>).

An example for a GeoTouchSensor:

         GeoTouchSensor        {
               description "Earth"
               geoSystem ["GC",””]
               enabled TRUE
         }




Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                                 15


6.7. GeoPositionInterpolator

         SFFloat              [in]       set_fraction         (-∞,∞)
         MFFloat              [in,out]   key           []    (-∞,∞)
         MFVec3d              [in,out]   keyValue      []
         SFVec3d              [out]      geovalue_changed
         SFVec3f              [out]      value_changed
         MFString             []         geoSystem           ["GD","WE"]


The GeoPositionInterpolator node provides an interpolator capability where key values are
specified in geographic coordinates and the interpolation is performed within the specified
spatial reference frame.

The geoSystem field is used to define the spatial reference frame and is described in the
node description geoSystem.

The fields key, set_fraction, and value_changed have the same meaning as in the
PositionInterpolator node.

The keyValue array is used to contain the actual coordinates and should be provided in a
format consistent with that specified for the particular geoSystem.

The geovalue_changed field outputs the the interpolated coordinate in the spatial
reference frame specified by geoSystem. This can be passed to other GeoX3D nodes that
support a field of this form like GeoLocation.

Example for a GeoPositionInterpolator for a rotaion around the world:

         DEF Interpolator GeoPositionInterpolator
         {
                key [ 0.0 0.25 0.5 0.50000001 0.75 1.0 ]
                keyValue [
                0 5194455 5224697.6,             # in GD notation 000° 45° 1000000m 5224697.6 5194455 0,
                                 # in GD notation 090° 45° 1000000m
                0 5194455 -5224697.6,            # in GD notation 180° 45° 1000000m
                -91183 5194455 -5223901.91, # in GD notation 181° 45° 1000000m
                -5224697.6 5194455 0,            # in GD notation 270° 45° 1000000m
                0 5194455 5224697.6,             # in GD notation 000° 45° 1000000m
                         ]
                geoSystem ["GC"]
         }



Bitmanagement Software GmbH          Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                    Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                           AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                              UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                          16

ROUTE <Defined Timer>.fraction_changed TO Interpolator.set_fraction
ROUTE Interpolator.geovalue_changed TO <GeoLocation node>.set_geoCoords




Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de
                                                                                                                   17


 7. BSTile data formats

BStile stores a series of image tiles at levels up to a maximum level. An dictionary allows
fast random access to a give tile with tile coordinates xy at an index level.



7.1. Uncompressed encodings
Any native DirectX surface formats is supported.
The graphics card of the target machine must be able to support the surface format:

a) Examples are:

    ●    DXT1                 DXT1 compression, 1/8 of size of 32 BIT RGB, tileSize must be divisisble by 4
    ●    X8R8G8B8             32 bit RGB
    ●    A8R8G8B8             32 bit RGBA
    ●    L8                   8 bit Grayscale
    ●    R5G6B5               16 bit RGB
    ●    X1R5G5B5             15 bit RGB
    ●    L16                  16 bit Grayscale




7.2. Compressed encodings
Each individual tile is encoded use a standard image compression scheme.
The type of encodings are


    ●    JPEG
    ●    PNG
    ●    TGA
    ●    JP2




7.3. Elevation encodings

    ●    L16      16 Bit integer


Bitmanagement Software GmbH         Geschäftsführer          Deutsche Bank 24 AG     Tel. 0049 (0)8151 97170-8
Oberlandstraße 26                   Peter Schickel           BLZ 700 700 24          Fax. 0049 (0)8151 97170-9
82335 Berg                          AG München HRB 143734    Kto 1530211             http://www.bitmanagement.de
Germany                             UST ID DE 224651645                              mail: info@bitmanagement.de
                                                                                                          18

 8. Links and References
NASA BlueMarble next generation data
http://visibleearth.nasa.gov/view_set.php?categoryID=2355

X3D geospatial component

http://www.web3d.org/x3d/specifications/ISO-IEC-19775-
X3DAbstractSpecification/Part01/components/geodata.html



 9. Contact
Our product portfolio, demos and download of evaluation visualisation software please find
at:

Bitmanagement Software GmbH
Oberlandstrasse 26
82333 Berg near Munich

www.bitmanagement.com               Telephone: 0049 (0)8151-971708
info@bitmanagement.com              Telefax: 0049 (0)8151-971709



Berg, December 2006




Bitmanagement Software GmbH   Geschäftsführer         Deutsche Bank 24 AG   Tel. 0049 (0)8151 97170-8
Oberlandstraße 26             Peter Schickel          BLZ 700 700 24        Fax. 0049 (0)8151 97170-9
82335 Berg                    AG München HRB 143734   Kto 1530211           http://www.bitmanagement.de
Germany                       UST ID DE 224651645                           mail: info@bitmanagement.de

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:67
posted:10/21/2010
language:English
pages:20