Syntax @Split(, (|), [, ]*) Arguments The string to split into component pieces. It should contain enough component parts to assign to each of the attribute names listed. Each component part is separated from the others by the delimiter character. Range: String The character(s) used to divide the into its component pieces. Range: Single Character or Character Sequence A format specification may be used in place of a delimiting character. The format specification consists of a series of field widths, separated by s characters. If the last s character is followed by a *, it will be repeated as many times as necessary until the input string is empty. The will be created or broken apart according to the widths specified. The format specification can be distinguished from the delimiting character because the format string must always have more than one character in it. Range: #s[#s]+[#s*] The names of the attributes assigned the pieces of when it is split apart. The first component of is assigned to the first attribute name, the second component to the second attribute, and so on. The number of attribute names must match the number of component parts of . A repeat attribute is seen as a single attribute for this count. It will be turned into a list attribute. If only one attribute is present, and it is a list attribute, the format specification will instead split the input string into the different indexes of the list. A repeat attribute will continue to enlarge the list as necessary. Range: String Description The @Split command breaks a string into its component parts and assigns those parts to attributes of a feature. It is used to facilitate translation when a single attribute value in one system implies a set of attribute values in another. For example, when @Split is invoked on a destination line with these parameters: @Split(top|left,|,vertical,horizontal) the vertical attribute in the feature is assigned a value of top, and the horizontal attribute is assigned a value of left. Any character may be chosen to be the delimiter for the input string. However, it is critical that the number of attribute names listed matches the number of component parts present in the input string. If the delimiter starts with a backslash ("\"), it is interpreted as a quoted special character sequence, as specified in the following table. If the sequence is not listed in the table, then the backslash character is simply ignored. \a Audible alert (bell) (0x07) \b Backspace (0x08) \f Form feed (0x0c) \n Newline (0x0a) \r Carriage return (0x0d) \t Tab (0x09) \v Vertical tab (0x0b) \, Comma \\ Backslash \/ Slash \ooo The digits ooo describe a character in octal notation. (There may be one, two, or three octal digits.) \xhh The digits hh describe a character in hexadecimal notation. (There may be one or two hexadecimal digits.) The delimiter may also be specified in an encoded internal FME format produced by FME Workbench. This encoding allows for a multiple character string with special character handling. The field attribute names may be names of attribute lists. List attribute names contain empty {} in their names. If the field names are lists, then the input string is assumed to be a list itself, and each element in the input string is broken into pieces and assigned to the next element in the attribute list. The {} are filled in with element numbers starting at 0 as the list is unpacked. Tip: If one attribute is a list, then they all must be.