Main menu

Pages

Edit post

Export Tile Cache, Generate and Import and Manage Tile Cache Tiling Scheme

Husam Jubeh
(0)

Export Tile Cache, Generate and Import and Manage Tile Cache Tiling Scheme Tools

Export Tile Cache

How to Export Tile Cache Tool in Arc Toolbox ArcMap ArcGIS??

Export Tile Cache Tool
Export Tile Cache

Path to access the tool

:

Export Tile Cache Tool, Tile Cache Toolset, Data Management Tools Toolbox

 

Export Tile Cache

Exports tiles from an existing tile cache to a new tile cache or a tile package. The tiles can be either independently imported into other caches or accessed from ArcGIS Desktop or mobile devices.

1.    Input Tile Cache

An existing tile cache to be exported.

2.    Output Tile Cache Location

The output folder into which the tile cache or tile package will be exported.

3.    Output Tile Cache Name

The name of the exported tile cache or tile package.

4.    Export Cache As (optional)

Specifies whether the cache will be exported as a tile cache or a tile package. Tile packages are suitable for ArcGIS Runtime and ArcGIS Mobile deployments.

  1. TILE_CACHE—The cache will be exported as a stand-alone cache raster dataset. This is the default.
  2. TILE_PACKAGE—The cache will be exported as a single compressed file (.tpk) in which the cache dataset is added as a layer and consolidated so that it can be shared easily. This type can be used in ArcMap as well as in ArcGIS Runtime and ArcGIS Mobile applications.
  3. TILE_PACKAGE_TPKX—The cache will be exported using Compact_v2 storage format (.tpkx), which provides better performance on network shares and cloud storage directories. This improved and simplified package structure type is supported by newer versions of the ArcGIS platform such as ArcGIS Online, ArcGIS Pro 2.3, ArcGIS Enterprise 10.7, and ArcGIS Runtime 100.5.

5.    Storage Format (optional)

Determines the storage format of tiles.

  1. COMPACT—Group tiles into large files called bundles. This storage format is more efficient in terms of storage and mobility. This is the default.
  2. EXPLODED—Each tile is stored as an individual file. Note that this format cannot be used with tile packages.

6.    Scales [Pixel Size] (Estimated Disk Space) (optional)

A list of scale levels at which tiles will be exported.

7.    Area of Interest (optional)

An area of interest that spatially constrains where tiles will be exported from the cache.

The area of interest can be a feature class or a feature that you draw on the map.

This parameter is useful if you want to export irregularly shaped areas, as the tool clips the cache dataset at pixel resolution.

Generate Tile Cache Tiling Scheme

How to Generate Tile Cache Tiling Scheme Tool in Arc Toolbox ArcMap ArcGIS??

Generate Tile Cache Tiling Scheme Tool
Generate Tile Cache Tiling Scheme

Path to access the tool

:

Generate Tile Cache Tiling Scheme Tool, Tile Cache Toolset, Data Management Tools Toolbox

 

Generate Tile Cache Tiling Scheme

Creates a tiling scheme file based on the information from the source dataset. The tiling scheme file will then be used in the Manage Tile Cache tool when creating cache tiles.

This tool can be used to edit the properties of an existing tiling scheme, such as tile format, storage format, tile size, and so on. In addition, you can also use it to add new scale levels to an existing tiling scheme.

1.    Input Data Source

The source to be used to generate the tiling scheme. It can be a raster dataset, a mosaic dataset, or a map.

2.    Output Tiling Scheme

The path and file name for the output tiling scheme to be created.

3.    Generation Method

Choose to use a new or predefined tiling scheme. You can define a new tiling scheme with this tool or browse to a predefined tiling scheme file (.xml).

  1. NEW—Define a new tiling scheme using other parameters in this tool to define scale levels, image format, storage format, and so on. This is the default.
  2. PREDEFINED—Use a tiling scheme .xml file that already exists on disk.

4.    Predefined Tiling Scheme (optional)

Path to a predefined tiling scheme file (usually named conf.xml). This parameter is enabled only when the Predefined option is chosen as the tiling scheme generation method.

5.    Number of Scales

The number of scale levels to be created in the tiling scheme.

6.    Cell Size (optional)

Determines the units of the Scales parameter.

  1. Checked—The values of the Scales parameter are pixel sizes. This is the default.
  2. Unchecked—The values of the Scales parameter are scale levels.

7.    Scales (optional)

Scale levels to be included in the tiling scheme. By default, these are not represented as fractions. Instead, use 500 to represent a scale of 1:500, and so on. The value entered in the Number of Scales parameter generates a set of default scale levels.

8.    Tile Origin in map units (optional)

The origin (upper left corner) of the tiling scheme in the coordinates of the spatial reference of the source dataset. The extent of the source dataset must be within (but does not need to coincide) this region.

9.    Dots (Pixels) Per Inch (optional)

The dots per inch of the intended output device. If a DPI is chosen that does not match the resolution of the output device, typically a display monitor, the scale of the tile will appear incorrect. The default value is 96.

10. Tile Size (in pixels) (optional)

The width and height of the cache tiles in pixels. The default is 256 by 256.

For the best balance between performance and manageability, avoid deviating from widths of 256 or 512.

  • 128 x 128— Tile width and height of 128 pixels.
  • 256 x 256—Tile width and height of 256 pixels.
  • 512 x 512—Tile width and height of 512 pixels.
  • 1024 x 1024—Tile width and height of 1024 pixels.

11. Tile Format (optional)

The file format for the tiles in the cache.

  1. PNG—Creates PNG format with varying bit depths. The bit depths are optimized according to the color variation and transparency values in each tile.
  2. PNG8—A lossless, 8-bit color, image format that uses an indexed color palette and an alpha table. Each pixel stores a value (0 to 255) that is used to look up the color in the color palette and the transparency in the alpha table. 8-bit PNGs are similar to GIF images and provide the best support for a transparent background by most web browsers.
  3. PNG24—A lossless, three-channel image format that supports large color variations (16 million colors) and has limited support for transparency. Each pixel contains three 8-bit color channels, and the file header contains the single color that represents the transparent background. The color representing the transparent background color can be set in the application. Versions of Internet Explorer prior to version 7 do not support this type of transparency. Caches using PNG24 are significantly larger than those using PNG8 or JPEG, so will take more disk space and require greater bandwidth to serve clients.
  4. PNG32—A lossless, four-channel image format that supports large color variations (16 million colors) and transparency. Each pixel contains three 8-bit color channels and one 8-bit alpha channel that represents the level of transparency for each pixel. While the PNG32 format allows for partially transparent pixels in the range from 0 to 255, the ArcGIS Server cache generation tool only writes fully transparent (0) or fully opaque (255) values in the transparency channel. Caches using PNG32 are significantly larger than the other supported formats, so will take more disk space and require greater bandwidth to serve clients.
  5. JPEG—A lossy, three-channel image format that supports large color variations (16 million colors) but does not support transparency. Each pixel contains three 8-bit color channels. Caches using JPEG provide control over output quality and size.
  6. MIXED—Creates PNG32 anywhere that transparency is detected (in other words, anyplace where the data frame background is visible), but creates JPEG for the remaining tiles. This keeps the average file size down while providing you with a clean overlay on top of other caches. This is the default.
  7. LERC—Limited Error Raster Compression (LERC) is an efficient lossy compression method recommended for single-band or elevation data with a large pixel depth (12 bit to 32 bit). Compresses between 10:1 and 20:1.

12. Tile Compression Quality (optional)

Enter a value between 1 and 100 for the JPEG or MIXED compression quality. The default value is 75.

Compression is supported only for MIXED and JPEG format. Choosing a higher value will result in higher-quality images, but the file sizes will be larger. Using a lower value will result in lower-quality images with smaller file sizes.

13. Storage Format (optional)

Determines the storage format of tiles.

  1. COMPACT—Group tiles into large files called bundles. This storage format is more efficient in terms of storage and mobility. This is the default.
  2. EXPLODED—Each tile is stored as an individual file.Note that this format cannot be used with tile packages.

14. LERC Error (optional)

Set the maximum tolerance in pixel values when compressing with LERC.LERC Error (optional) Set the maximum tolerance in pixel values when compressing with LERC.

Import Tile Cache

How to Import Tile Cache Tool in Arc Toolbox ArcMap ArcGIS??

Import Tile Cache Tool
Import Tile Cache

Path to access the tool

:

Import Tile Cache Tool, Tile Cache Toolset, Data Management Tools Toolbox

 

Import Tile Cache

Imports tiles from an existing tile cache or a tile package. The target cache must have the same tiling scheme, spatial reference, and storage format as the source tile cache.

1.    Target Tile Cache

An existing tile cache to which the tiles will be imported.

2.    Source Tile Cache

An existing tile cache or a tile package from which the tiles are imported.

3.    Scales [Pixel Size] (Estimated Disk Space) (optional)

A list of scale levels at which tiles will be imported.

4.    Overwrite Tiles (optional)

Determines whether the images in the destination cache will be merged with the tiles from the originating cache or overwritten by them.

  1. Unchecked—When the tiles are imported, transparent pixels in the originating cache are ignored by default. This results in a merged or blended image in the destination cache. This is the default.
  2. Checked—The import replaces all pixels in the area of interest, effectively overwriting tiles in the destination cache with tiles from the originating cache.

5.    Area of Interest (optional)

An area of interest will spatially constrain where tiles are imported into the cache.

This parameter is useful if you want to import tiles for irregularly shaped areas.

Manage Tile Cache

How to Manage Tile Cache Tool in Arc Toolbox ArcMap ArcGIS??

Manage Tile Cache Tool
Manage Tile Cache

Path to access the tool

:

Manage Tile Cache Tool, Tile Cache Toolset, Data Management Tools Toolbox

 

Manage Tile Cache

Creates a tile cache or updates tiles in an existing tile cache. You can use this tool to create new tiles, replace missing tiles, overwrite outdated tiles, and delete tiles.

1.    Cache Location

The folder in which the cache dataset is created or the path to an existing tile cache.

2.    Cache Name (optional)

Name of the cache dataset to be created inside the cache location.

3.    Manage Mode

The mode for managing the cache.

  1. RECREATE_ALL_TILES—Existing tiles will be replaced and new tiles will be added if the extent has changed or if layers have been added to a multilayer cache.
  2. RECREATE_EMPTY_TILES—Only tiles that are empty will be created. Existing tiles will be left unchanged.
  3. DELETE_TILES—Tiles will be deleted from the cache. The cache folder structure will not be deleted.

4.    Input Data Source (optional)

A raster dataset, mosaic dataset, or map document.

This parameter is not required when DELETE_TILES is specified in the Manage Mode parameter.

An ArcMap document (.mxd) cannot contain a map service or image service.

5.    Input Tiling Scheme (optional)

An optional parameter to specify the tiling scheme.

  1. ARCGISONLINE_SCHEME—Use the default ArcGIS Online tiling scheme.
  2. IMPORT_SCHEME—Import an existing tiling scheme.
  3. ARCGISONLINE_ELEVATION_SCHEME—Use this tiling scheme for elevation services.
  4. WGS84_V2_SCHEME—Use this tiling scheme based on WGS84 Version 2.

6.    Import Tiling Scheme (optional)

Path to an existing scheme file (.xml) or imported from an existing image service or map service.

7.    Minimum Cached Scale (optional)

The minimum scale at which you want to create tiles. This does not have to be the smallest scale in your tiling scheme. Your minimum cache scale will determine which scales are used when generating cache.

8.    Maximum Cached Scale (optional)

The maximum scale at which you want to create tiles. This does not have to be the largest scale in your tiling scheme. The maximum cache scale will determine which scales are used when generating cache.

9.    Scales [Pixel Size] (Estimated Disk Space) (optional)

The scale levels at which you will create or delete tiles when running this tool, depending on the value of the Manage Mode parameter. The pixel size is represented based on the spatial reference of the tiling scheme.

  1. By default, only the scales within Minimum Cached Scale and Maximum Cached Scale will be checked on.
  2. Altering the value of either the Minimum Cached Scale or the Maximum Cached Scale parameter will check on or off the appropriate scale values.
  3. Scales checked on and not within the range of Minimum Cached Scale or Maximum Cached Scale are ignored when generating the cache.

10. Area of Interest (optional)

Defines an area of interest to constrain where tiles will be created or deleted.

It can be a feature class, or it can be a feature set that you interactively define.

This parameter is useful if you want to manage tiles for irregularly shaped areas. It's also useful in situations where you want to precache some areas and leave less-visited areas uncached.

11. Maximum Source Cell Size (optional)

The value that defines the visibility of the data source for which the cache will be generated. By default, the value is empty.

If the value is empty

  1. For levels of cache that lie within the visibility ranges of the data source, the cache is generated from the data source.
  2. For levels of cache that fall outside the visibility of the data source, the cache is generated from the previous level of cache.

  • If the value is greater than zero

  1. For levels with cell sizes smaller than or equal to Maximum Source Cell Size (max_cell_size), the cache is generated from the data source.
  2. For levels with cell sizes greater than Maximum Source Cell Size (max_cell_size), the cache is generated from the previous level of cache.

The unit of the Maximum Source Cell Size value should be the same as the unit of the cell size of the source dataset.

Latest articles from : Data Management

Comments

Post a Comment

table of contents title