Last updated

API / geotoolkit3d / scene / surface / Surface / Surface

Namespace: Surface

surface.Surface.Surface

Table of contents

Type Aliases

Contents

Type Aliases

CanvasServer

Ƭ CanvasServer: Object

Type declaration

NameTypeDescription
formatterfunctionFormatterFunctionformatter function for loading tiles
serverstringserver for loading tiles

CommonOptions

Ƭ CommonOptions: Object

Type declaration

NameTypeDescription
extentBox2visible model limits of elevation (WGS84 full limits by default)
geometryCanvasServerobject for loading geometry tiles
highlightmode?HighlightModeDefine how the Surface will be highlighted when selected.
Default is HighlightMode.ContourHighlight for regular Surfaces, or HighlightMode.HaloHighlight for HeightMap surfaces.
maplimitsBox2model limits of elevation (WGS84 full limits by default)
materialCanvasServerobject for loading texture tiles
maximumrequestsnumbermaximum requests at the same time (for network optimization)
maxlodnumberthe highest level of tile layer
minlodnumberthe lowest level of tile layer
tileheightnumbertile height
tilewidthnumbertile width

CommonOptionsBase

Ƭ CommonOptionsBase: Options & TextureOptionsIn & Partial<CommonOptions> & { colorprovider?: ColorProvider | string | Color ; data?: { valuemode?: HeightMapElevationValueMode } }


CommonOptionsBaseOut

Ƭ CommonOptionsBaseOut: Required<Options> & TextureOptionsOut & CommonOptions & { nullvalue: number ; zmax: number ; zmin: number }


FormatterFunction

Ƭ FormatterFunction: (z: number, y: number, x: number) => string

Type declaration

▸ (z, y, x): string

Parameters
Name Type
znumber
ynumber
xnumber
Returns

string


MemoryCapabilitiesInfo

Ƭ MemoryCapabilitiesInfo: Object

Type declaration

NameTypeDescription
limitationLimitationDescribe the current bottleneck for the provided estimation.
Please note that if the VRAM argument is not provided, it is not possible to tell if the GPU memory is the current limitation.
maxverticesnumberThe maximum number of vertices that can be loaded safely, with the given memory information.
For example, if the result is 1000,000 vertices, one can imagine loading a Surface of dimensions of 1000 * 1000 (or any combinations that leads to one million).
Please keep in mind this is only an estimation, even if the VRAM option is provided, browsers and OSes handle RAM and VRAM memory very differently.

MemoryEstimationOptions

Ƭ MemoryEstimationOptions: Object

Type declaration

NameTypeDescription
ramnumberThe amount of estimated available RAM in bytes, that the Surface visual can allocate.
On average, Surface will use 40 bytes of RAM per cell.
Additional features such as intersections and transparency can create additional memory spikes.
useintersection?boolean(Optional) Use an extra amount of RAM per cell if intersections are used. Default is false.
vram?number(Optional) The amount of estimated available VRAM (Video Memory) in bytes, that the Surface visual can allocate.
Surface will use 28 bytes of VRAM per cell.

Options

Ƭ Options: Options & Options & CommonOptionsBase

The options to use to create the surface


OptionsBase

Ƭ OptionsBase: OptionsBase & CommonOptionsBase


OptionsBaseOut

Ƭ OptionsBaseOut: OptionsBaseOut & CommonOptionsBaseOut