In an ICC color management workflow, an input color is mapped from a device color space using an A2B (device dependant to device independent) tag to a Profile Connection Space, (either XYZ or LAB) and then through a B2A (device independent to device dependent) tag to the output device space. The tags in this instance are look-up tables; the contents are interpolated to allow a small table to encode a large input and output range.When developing the B2A tags, one must gamut map from a grid in either CIELAB, XYZ or colorimetric RGB to the device gamut. Such grids typically encode non-physical colors that are an artifact of the encoding rather than colors one would expect to occur in nature. These non-physical colors are problematic if one wishes to gamut map in a color appearance space such as CIECAM 02.Compared with CIELAB, CIECAM02 should allow gamut mapping along a more perceptually constant hue. Gamut mapping is one of the recommended uses of CIECAM02. But a brute-force approach, simply replacing CIELAB calculations with CIECAM02 calculations, is problematic for certain imaginary colors. As an example, it is not possible to devise a colorimetric RGB color encoding which encompasses the entire ICC v.4 Reference Medium Gamut (RMG) and has all entries as valid CIECAM02 encodings. Below is a wide-gamut colorimetric RGB color encoding mapped into CIECAM02. Even though this encoding isn't large enough to include all ICC v.4 RMG colors, the blue primary is located in an inappropriate location in CIECAM02. Expanding the color space would result in imaginary CIECAM02 values.