To make GlobeView operate properly and with good performance it is essential that the ElevationInput and SurfaceLayers can handle requests for data at all resolutions. The first tile loaded will typically be very large, but with very low resolution; if the data sources can't handle such a low resolution, the first tiles may take a very long time to load.

For the elevation data it is recommended to use Overviews on the data set to let it generate low-resolution overviews. The JPEG 2000 and ECW datasets will also work well since they can provide low-resolution data directly from the source files. If you have several different datasets for different resolutions, for instance DTED level 0, 1 and 2, it is recommended that you use a LevelOfDetailOperator, possibly in combination with raster caches for the individual datasets.

The surface layers can be configured just like in 2D; using a combination of min and max scales on the layers, and LevelOfDetailOperator. Just make sure that the layers are turned off when zoomed out far, or the first large tile may take a very long time to load. Note that the scale that is used when requesting data from the surface layers is not an absolute scale value (since there is no such thing in a 3D view). However, the layer tries to calculate a scale value that should match a tile of about the same screen area in a 2D view.

If ElevationInput or SurfaceLayers contains a CustomOperatorProxy with a custom operator implementation then the elevation and/or surface layers will be loaded on a single background thread and not use the task based scheduler to load multiple tiles in parallel.

To make GlobeView operate properly and with good performance it is essential that the elevationInput and surfaceLayers can handle requests for data at all resolutions. The first tile loaded will typically be very large, but with very low resolution; if the data sources can't handle such a low resolution, the first tiles may take a very long time to load.

For the elevation data it is recommended to use RasterCachePolicyOverviews on the data set to let it generate low-resolution overviews. The JPEG 2000 and ECW datasets will also work well since they can provide low-resolution data directly from the source files. If you have several different datasets for different resolutions, for instance DTED level 0, 1 and 2, it is recommended that you use a LevelOfDetailOperator, possibly in combination with raster caches for the individual datasets.

The surface layers can be configured just like in 2D; using a combination of min and max scales on the layers, and LevelOfDetailOperator. Just make sure that the layers are turned off when zoomed out far, or the first large tile may take a very long time to load. Note that the scale that is used when requesting data from the surface layers is not an absolute scale value (since there is no such thing in a 3D view). However, the layer tries to calculate a scale value that should match a tile of about the same screen area in a 2D view.

If elevationInput or surfaceLayers contains a CustomOperatorProxy with a custom operator implementation then the elevation and/or surface layers will be loaded on a single background thread and not use the task based scheduler to load multiple tiles in parallel.

To make GlobeView operate properly and with good performance it is essential that the elevationInput and surfaceLayers can handle requests for data at all resolutions. The first tile loaded will typically be very large, but with very low resolution; if the data sources can't handle such a low resolution, the first tiles may take a very long time to load.

For the elevation data it is recommended to use OVERVIEWS on the data set to let it generate low-resolution overviews. The JPEG 2000 and ECW datasets will also work well since they can provide low-resolution data directly from the source files. If you have several different datasets for different resolutions, for instance DTED level 0, 1 and 2, it is recommended that you use a LevelOfDetailOperator, possibly in combination with raster caches for the individual datasets.

The surface layers can be configured just like in 2D; using a combination of min and max scales on the layers, and LevelOfDetailOperator. Just make sure that the layers are turned off when zoomed out far, or the first large tile may take a very long time to load. Note that the scale that is used when requesting data from the surface layers is not an absolute scale value (since there is no such thing in a 3D view). However, the layer tries to calculate a scale value that should match a tile of about the same screen area in a 2D view.

If elevationInput or surfaceLayers contains a CustomOperatorProxy with a custom operator implementation then the elevation and/or surface layers will be loaded on a single background thread and not use the task based scheduler to load multiple tiles in parallel.

To make GlobeView operate properly and with good performance it is essential that the elevationInput and surfaceLayers can handle requests for data at all resolutions. The first tile loaded will typically be very large, but with very low resolution; if the data sources can't handle such a low resolution, the first tiles may take a very long time to load.

For the elevation data it is recommended to use RasterCachePolicy.Overviews on the data set to let it generate low-resolution overviews. The JPEG 2000 and ECW datasets will also work well since they can provide low-resolution data directly from the source files. If you have several different datasets for different resolutions, for instance DTED level 0, 1 and 2, it is recommended that you use a LevelOfDetailOperator, possibly in combination with raster caches for the individual datasets.

The surface layers can be configured just like in 2D; using a combination of min and max scales on the layers, and LevelOfDetailOperator. Just make sure that the layers are turned off when zoomed out far, or the first large tile may take a very long time to load. Note that the scale that is used when requesting data from the surface layers is not an absolute scale value (since there is no such thing in a 3D view). However, the layer tries to calculate a scale value that should match a tile of about the same screen area in a 2D view.

If elevationInput or surfaceLayers contains a CustomOperatorProxy with a custom operator implementation then the elevation and/or surface layers will be loaded on a single background thread and not use the task based scheduler to load multiple tiles in parallel.