Syntax

   @Log([<message>],[<maxCoords>],[maxFeatures>],[<filename>],[<severity>],[<logfeature>],[<logFeatureTableAsMultipleFeatures>])

Signature for passing FMEParsableTextEncoded message:
   @Log(ENCODED,<FMEParsableTextmessage>,[<maxCoords>],[<maxTimesToLog>],[<filename>],[<severity>],[<logfeature>],[<msgKey>],[<logFeatureTableAsMultipleFeatures>])
If one optional parameter is specified, all parameters prior must be specified as well.

Arguments
   <msgKey> - indicates how often this transformer should log.  It becomes the 
              domain on the maxFeatures.  If not specified, the msg is used
              as the key

   <message>   
      An optional message may be specified. If present, this message is output 
      to the log file before each feature is logged. This is useful to identify 
      features if the @Log command is used in many places within a single 
      mapping file.
      Range: Any String 
   
   <severity> INFO|WARN|ERROR
      The severity of the msg and feature in the log.  Default is INFO

   <logfeature> LOG_ONLY|LOG_RECORD|NONE
      LOG_ONLY = log the feature but do not output to an ffs file
      LOG_RECORD = log the feature and record it to the ffs file
      NONE = only log the message and not the feature
      
  <maxCoords>
      The number of coordinates to be logged.
      If not specified, the first 5 and the last 5 coordinates will be logged. 
      If -1 is specified, all coordinates will be logged. 
      If 0 is specified, no coordinates will be logged.
      If any other value is specified, only the first <maxCoords> coordinates 
      will be logged.
      Range: Integer >= -1 
      
   <maxFeatures>     
      The maximum number of features logged for this message. 
      The number indicated by the LOG_MAX_FEATURES directive limits that given 
      for maxFeatures.
      Range: Integer

   <logFeatureTableAsMultipleFeatures> LOG_FEATURE_TABLE_AS_MULTIPLE_FEATURES|LOG_FEATURE_TABLE_AS_SINGLE_FEATURE
      Specifies whether a feature with a feature table geometry should be logged
      as if it was multiple features (one per row in the feature table), or as a
      single feature with an IFMEFeatureTable geometry.

   <filename>
      A file to append the log messages to.  By default, it is the $(mf_Name).log but 
      this allows log messages to go to another location.  

Configuration

   This function does not accept configuration lines.
      Tip: Because the @Log function writes out large amounts of data to the log 
      file, it significantly slows a translation and should be used only during 
      testing and debugging. The LOG_MAX_FEATURES mapping file directive limits 
      the number of features that may be logged in a single FME session.

Description
   The @Log function outputs features to the FME log file. This function is 
   primarily used during testing and debugging of transformation specifications, 
   so the complete state of a feature can be viewed before and after it is 
   transformed. It can also be used to log a feature before and after a feature 
   function is applied.

   This function is useful for logging erroneous features to the log file when 
   the FME is used as a quality assurance tool for processing data.