Syntax

   @Log([<message>[,<maxCoords>[,maxFeatures>[,<filename>]]]])
   
Arguments

   <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 
      
   <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

   <filename>

      A file to append the logged feature to.

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.