Table or Raster Data – which Raster Type is correct for a derived mosaic dataset

A derived mosaic dataset is a mosaic dataset that is created from adding other mosaic datasets into it. When populating a derived mosaic dataset, it is okay to use either the Raster Dataset or Table as your raster type. The raster type chosen will load your data in a slightly different way.
derived mosaic dataset

If you add your source mosaic datasets as a Raster Dataset raster type, each mosaic dataset is added as one row within your derived mosaic dataset. This means that if there were 3 source mosaic datasets, then only 3 rows will appear within your derived mosaic dataset.
Raster type as Raster dataset

If you add your source mosaic datasets as a Table raster type, then your derived mosaic dataset will add each item from the source, as its own row. This means that if there were a total of 300 mosaic dataset items within the source mosaic datasets, there will be 300 rows within your derived mosaic dataset.
Raster Type as Table

This entry was posted in Imagery and tagged , , . Bookmark the permalink.

Leave a Reply


  1. napugh says:

    I think you have table and raster dataset reversed. Using table would add a row for each item in the source while raster dataset would add a row for each input mosaic dataset.

  2. Simon Woo says:

    The blog has been updated. Thank you for your feedback.

  3. xlhomme says:

    What about the performance those two resulting mosaic dataset when published as a map service ?

    • Simon Woo says:

      I asked around and so far we do not have any official results of the two within a published map service.
      Within the realm of the mosaic dataset, the 2 raster types have the same performance*.

      *The Raster Dataset raster type has the same performance as the Table type – for up to 8 rows that are being currently displayed. Each additional row that is added via Raster Dataset will slow down the performance a bit. If you anticipate more than 8 rows being displayed at any given time, then you should consider the Table type.

      I guess this means I do not need to blog about this next week :)

  4. kakrattiger says:

    Raster Team: What does Esri recommend, Raster or Table data to a derived mosaic, when the rasters in a source mosaic dataset will change content or properties (such as raster functions or removing/adding/updating rasters)? Additionally 1) What is required for the derived mosaic to pick up changes to source mosaic dataset rasters in both the Raster or Table add workflows, and 2) what about functions performed on the source mosaic datasets getting picked up in the derived mosaic dataset? I experience differing results when using both add by table or raster options. Thank for any suggestions you can provide.

    • Simon Woo says:

      I would like to thank Vinay for providing the following answers. If we need to clarify on a point, please let us know.

      Use Rasterdataset – if :
      - you keep changing the source raster functions
      - and you do not want to run sync
      - AND you do not need the metadata
      - And you do not have too many items added using this method into a single mosaic – this is not typically recommended because of the overheads associated with opening individual mosaics.

      Functions applied on the source mosaic does not get carried forward to the derived if you use table type

      Workflow to see updates in case of a table based worlkflow – run the sync tool Workflow to see updates in case of a MD through raster dataset raster type – based worlkflow – none required, it happens on the fly.