For all data products, an embedded VICAR label follows the PDS label and      
is pointed to by the PDS pointer "^IMAGE_HEADER".  The VICAR label is         
also organized in an ASCII, "keyword = value" format, although there are      
only spaces between keywords (no carriage return/line feeds as in PDS).       
The information in the VICAR label is an exact copy of the information in     
the PDS label.                                                                
                                                                              
The reader is referred to the VICAR File Format document for details          
of the format, which is available at the URL                                  
"http://www-mipl.jpl.nasa.gov/vicar/vic_file_fmt.html".                       
The following text is an excerpt which describes the basic structure:         
A VICAR file consists of two major parts: the labels, which describe          
what the file is, and the image area, which contains the actual image.        
The labels are potentially split into two parts, one at the beginning         
of the file, and one at the end. Normally, only the labels at the             
front of the file will be present. However, if the EOL keyword in the         
system label (described below) is equal to 1, then the EOL labels             
(End Of file Labels) are present. This happens if the labels expand           
beyond the space allocated for them. The VICAR file is treated as a           
series of fixed-length records, of size RECSIZE (see below). The image        
area always starts at a record boundary, so there may be unused space         
at the end of the label, before the actual image data starts.                 
The label consists of a sequence of "keyword=value" pairs that describe       
the image, and is made up entirely of ASCII characters.                       
Each keyword-value pair is separated by spaces. Keywords are strings,         
up to 32 characters in length, and consist of uppercase characters,           
underscores ("_"), and numbers (but should start with a letter).              
Values may be integer, real, or strings, and may be multiple                  
(e.g. an array of 5 integers, but types cannot be mixed in a                  
single value). Spaces may appear on either side of the equals                 
character (=), but are not normally present. The first keyword is             
always LBLSIZE, which specifies the size of the label area in bytes.          
LBLSIZE is always a multiple of RECSIZE, even if the labels don't fill up     
the record. If the labels end before LBLSIZE is reached (the normal case),    
then a 0 byte terminates the label string. If the labels are exactly          
LBLSIZE bytes long, a null terminator is not necessarily present.             
The size of the label string is determined by the occurrence of the first     
0 byte, or LBLSIZE bytes, whichever is smaller. If the system keyword         
EOL has the value 1, then End-Of-file Labels exist at the end of the          
image area (see above). The EOL labels, if present, start with another        
LBLSIZE keyword, which is treated exactly the same as the main LBLSIZE        
keyword. The length of the EOL labels is the smaller of the length to         
the first 0 byte or the EOL's LBLSIZE. Note that the main LBLSIZE does        
not include the size of the EOL labels. In order to read in the full          
label string, simply read in the EOL labels, strip off the LBLSIZE            
keyword, and append the rest to the end of the main label string.