The image service definition file structure
An image service definition is composed of many different files and folders. Each is displayed below as they are organized. In ArcCatalog, you only see the contents of the .ISDef folder along with the .DerivedImages folder represented as <name>.ISDef using the icon representing the ImageService.ISDef file.
 |
When you create an image service definition, the first files generated are the .ISDef folder containing the ImageService.ISDef file, the Footprint shapefile, and the RPDefs folder containing the .RPDef files. The ImageService.ISDef file is an XML file containing all the image service definition parameters, such as the number of bands, the spatial reference, the service properties, the client properties, and any service-level processes. The Footprint shapefile contains the outline of the raster data for each raster dataset. The Footprint shapefile attribute table, or service table, contains information for every footprint polygon, including the pointer to the .RPDef file and basic information about the raster dataset, such as the type of raster, an ID number, and information about the pixel sizes. An .RPDef file is created for each raster dataset (each polygon in the footprint). This is an XML file containing information about each raster dataset including its spatial reference, the number of bands, and processing that can be applied to that single raster dataset.
Learn about the .ISDef (image service definition) file
Learn about the Footprint layer
Learn about the .RPDef (raster process definition) file
When you build an image service definition, the Footprint shapefile attribute table is updated and the Boundary shapefile is created. The Boundary shapefile contains one or more polygons that define the extent of all the raster datasets in the image service definition.
Learn about the Boundary shapefile
The other folders or files that appear might not exist for all image service definitions. The Seamline shapefile is created if you create seamlines for the raster datasets in the image service definition. The .DerivedImages folder is created if you optimize your image service definition (which you will likely do) and do not redefine the default location. The SO folder contains any service overview files, the DT folder contains any derived tile files, and the DR folder contains any derived raster files.
Learn more about the Seamline shapefile
When you compile the image service definition, the .ISCDef file is created. This is the file that is used by Image Server Manager to serve the image service definition to clients. If you move an image service definition that is being served, you need to move the .DerivedImages folder and its contents along with the .ISCDef.
Learn about moving a compiled image service definition