Guidelines for creating a custom raster type
Satisfying the RPDef validator
Image Service Editor attempts to add to the image service definition the RPDefs that the generator returns. Before being added, the RPDefs are validated for minimum required parameters. Custom RPDef generators should ensure that the validator is satisfied with the output. The following table describes all the possible errors generated by the validator:
Status ID |
Severity |
Status Message |
What it means |
00B401 |
Critical Error |
No raster process definition XML available for validation. |
|
00B402 |
Critical Error |
Cannot find the raster process definition file. |
The specified RPDef XML file could not be opened for reading. The file-path might be wrong or the RPDef file might be missing. |
00B403 |
Critical Error |
Raster process definition file is corrupt. |
The XML file exists but cannot be read as an RPDef. |
00B404 |
Critical Error |
Raster type name missing. |
The name of the RPDef generator that created the RPDef is missing. Every RPDef must specify the name of a recognized RPDef generator (raster type) which was used for creating it. RPDefs created using external processes should have "RPDef" as the RPDef generator name. |
00B405 |
Critical Error |
Spatial reference information missing. |
Spatial reference system information is missing from the RPDef file. Currently, only a PRJ string is supported inside //Srs/Prj node of the RPDef. |
00B406 |
Critical Error |
Invalid spatial reference information. |
The spatial reference PRJ string was corrupt and could not be recognized by the system. |
00B407 |
Critical Error |
Footprint shape not available. |
|
00B408 |
Critical Error |
Invalid footprint shape. |
|
00B409 |
Critical Error |
Cannot transform the footprint from raster spatial reference ('{0}') to service spatial reference ('{1}'). |
|
00B410 |
Critical Error |
Invalid seamline shape. |
|
00B411 |
Critical Error |
Cannot transform the seamline from raster spatial reference ('{0}') to service spatial reference ('{1}'). |
|
00B412 |
Error |
Invalid high pixel size or low pixel size value. |
|
00B413 |
Error |
Invalid number of bands. |
|
00B414 |
Error |
Invalid bit-depth defined. |
|
00B415 |
Error |
Invalid pixel type defined. |
|
00B416 |
Warning |
Invalid color space defined. |
|
00B417 |
Warning |
Author not defined. |
|
00B418 |
Warning |
Creation date and time not defined. |
|
00B419 |
Warning |
Raster name not defined. |
|
00B420 |
Error |
Raster ID not defined for raster at position {0}. |
|
00B421 |
Error |
Raster source not defined for raster with ID '{0}'. |
|
00B422 |
Warning |
Pixel size not defined for raster with ID '{0}'. |
|
00B423 |
Warning |
Invalid pixel size defined for raster with ID '{0}'. |
|
00B424 |
Warning |
Invalid minimum and maximum pixel sizes defined for raster with ID '{0}'. |
|
00B425 |
Error |
Format name not defined for raster with ID '{0}'. |
|
00B426 |
Warning |
Format information not available for raster with ID '{0}'. |
|
00B427 |
Warning |
No processes applied on raster with ID '{0}'. |
|
00B428 |
Error |
Duplicate raster ID '{0}' found at positions {1} and {2}. |
|
00B429 |
Error |
Invalid raster source specified for Raster with ID '{0}'. |
|
00B430 |
Error |
Could not validate raster source. |
|
00B431 |
Error |
Could not validate raster source. |
|
00B432 |
Error |
Could not validate raster source. |
|
00B433 |
Error |
Could not validate raster source. |
|
00B434 |
Error |
Could not validate raster source. |
|
00B435 |
Error |
Could not validate raster source. Could not get raster item at position {0}. |
|
00B436 |
Error |
Raster source validation failed. Could not initialize raster item at position {0}. |
|
00B437 |
Error |
Raster source validation failed. |
|
00B438 |
Error |
Derived image does not exist. |
|
00B439 |
Error |
Could not validate raster source. |
|
00B440 |
Error |
Could not validate raster source. |
|
00B441 |
Error |
Could not validate raster source. |
|
00B442 |
Error |
Could not validate raster source. |
|
00B443 |
Error |
Cannot transform the footprint from raster spatial reference ('{0}') to default client spatial reference ('{1}'). |
|
00B444 |
Error |
Cannot open histogram process chain. |
|
00B445 |
Error |
Cannot initialize histogram process chain. |
|
00B446 |
Error |
Cannot create histogram for raster item with ID '{0}'. |
|
00B447 |
Error |
Cannot initialize the histogram generator. |
|
00B448 |
Error |
Invalid pixel size defined for raster with ID '{0}'. |
|
00B449 |
Error |
Invalid spatial reference system defined. |
|
00B450 |
Warning |
Client spatial reference is either missing or invalid |
|
00B451 |
Warning |
Could not compute the pixel size in the units of the raster spatial reference system. |
|
00B452 |
Error |
Could not get the footprint. |
|
00B453 |
Error |
Unsupported bit depth ({0}) for histogram generation for raster with ID '{1}'. |
|
00B454 |
Error |
Could not initialize the spatial reference system transformer object. |
|
Using the image service definition document
RPDef generators often have to adapt the output RPDef to the kind of image service definition it’s being created for. For instance, your raster type might want to create the RPDef differently depending on whether the image service definition (ISDef) expects single band or multi-band raster datasets (that’s defined in Input Definition page of the Service Properties dialog box).
Using the RPDef document
Image Service Editor expects valid RPDef XML strings from any RPDef generator. It’s up to the generator to create the XML. We recommend that custom RPDef generators use the RPDefDocument object to create and update RPDef XMLs.