Transaction Layout Detection

Detects transaction boundaries in documents by analyzing layout features such as lines, boxes, and whitespace areas.

Remarks

The Transaction Layout Detection class enables Grooper to identify the start and end of transactions or sections within a document by considering visual presentation elements. This includes horizontal and vertical lines, boxes, and whitespace areas that often separate or group related content.

How It Works

When extracting transactions, this class uses the configured 'Minimum Width' and 'Maximum Distance' properties to determine which lines of text should be grouped together as part of the same transaction. By leveraging layout cues, it can more accurately segment complex documents where text alone is insufficient for reliable separation.

Configuration Guidance

• Set 'Minimum Width' to exclude narrow sections that are unlikely to represent valid transactions.
• Adjust 'Maximum Distance' to control how far apart lines of text can be and still be considered part of the same transaction.
• Both properties accept values in logical units (such as inches or percentages), allowing for flexible configuration across different document types and layouts.

Usage Example

To configure Transaction Layout Detection for a document with wide transaction rows and moderate spacing:

layoutDetection.MinimumWidth = "75%"; layoutDetection.MaximumDistance = "0.5in";

This configuration will only return sections that are at least 75% of the page width and will group lines that are within half an inch of each other.

Notes

• Transaction Layout Detection is typically used in conjunction with other section or transaction extractors for best results.
• Proper configuration is essential for accurate detection; test with representative samples to ensure optimal results.
• For more information, see the documentation for Section Extract Methods and Transaction Detection.

Properties

Name	Type		Description
Minimum Width	String	►	The minimum width a section must have to be considered a valid transaction. ConverterUniversal Value Converter Default75% The 'Minimum Width' property sets a threshold for the width of detected sections. Any section whose width is less than this value will be excluded from the results. This helps filter out narrow or incidental groupings that do not represent meaningful transactions. The value can be specified as a percentage (for example, 75%) or as an absolute measurement (for example, 3in). Use a percentage to make the setting relative to the page width, which is useful for documents of varying sizes. Example: layoutDetection.MinimumWidth = "80%"; Increasing this value will require wider sections to be included, which can help avoid false positives in documents with narrow columns or side notes. Decreasing it allows narrower sections to be considered, which may be useful for documents with compact layouts.
Maximum Distance	String	►	The maximum vertical distance allowed between lines for them to be grouped in the same transaction. ConverterUniversal Value Converter Default0.5in The 'Maximum Distance' property controls how far apart lines of text can be and still be considered part of the same transaction. If the vertical distance between two lines exceeds this value, they will not be grouped together. The value can be specified in logical units such as inches (for example, 0.5in) or as a percentage of the page height. Adjust this setting to match the typical spacing of lines within your transactions. Example: layoutDetection.MaximumDistance = "0.25in"; Lower values make the detector more strict, requiring lines to be closer together to be grouped. Higher values allow for more vertical spacing, which can be useful for documents with larger gaps between transaction rows.

Used By

Transaction Detection