Geodatabase Catalog vs Image Server

1768
3
05-27-2010 09:35 AM
StuartKorte
New Contributor II
When or why would you put imagery in a Geodatabase Raster Catalog versus using Image Server? (for those that have both)
0 Kudos
3 Replies
BenKoostra
New Contributor II
I have the same general question, but will expand ...

In AGS 9.x, we have been storing image tiles in an enterprise GDB as a managed raster catalog.  Desktop clients access the raster catalog using direct connect.  For web apps, we created a cached map service.

In AGS 10, what would be the preferred method?

For us, performance (speed) is most important and size (disk space) is secondary.  Our raster data rarely changes.

Based on my understanding, the main options are:

Desktop clients
-- managed raster catalog in a GDB
-- new v10 mosaic dataset in a GDB (that points to the raw images)
-- image service created using AGS Image Server Extension
-- AGS map service with cache

Web apps
-- service created using Image Sever Extension
-- map service with cache


Any performance testing, guidance, suggestions ???

Thanks,
Ben
0 Kudos
MelanieHarlow
Esri Contributor
At 10, the recommendation is to manage your collections of raster data using the Mosaic Dataset.

Where to store the rasters...
- the mosaic dataset is located within a geodatabase (file gdb is recommended if ArcSDE isn't required), but the rasters can exist outside the geodatabase. If DBMS security isn't critical then the raster datasets can remain in your file system (files in directories). Just be sure that the raster data can be easily read (from the mosaic dataset or from ArcGIS Server if serving the mosaic dataset).

Serving...
- you can publish the mosaic dataset directly as an image service
- you can put the mosaic dataset in a .mxd and publish a map service (which can be cached)
- Any time you publish a mosaic dataset (in an mxd or as an image service) you require the ArcGIS Server Image extension.
- If the mosaic dataset has overviews, then it will display relatively quickly as an image service. If speed is your only concern, then publishing it as a cached map service will be the fastest method. However, as an image service you can use it as a raster dataset source, and you can query it and read metadata, etc (http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Querying_an_image_service_layer/00sp00...). But if it's in a map service you are limited to only viewing the imagery as a layer.
JerryGarcia
Occasional Contributor II
Should mosaic datasets be located in ArcSDE or file-based geodatabases?  What are the pros/cons?

Thanks!
0 Kudos