Tabular Layout (Table Extract Method) - Revision history

Rpatton: /* Using a Header Row Extractor */

2026-01-07T21:48:24Z

Using a Header Row Extractor

← Older revision		Revision as of 16:48, 7 January 2026
Line 125:		Line 125:
	A '''Header Row''' is the line (or lines) at the top of a table that contains the column labels, such as "Item No.", "Description", "Qty.", or "Total". In document processing, the header row provides essential context for identifying and aligning data in each column. Accurate header detection ensures that extracted values are mapped to the correct [[Data Column]]s, even when table layouts vary between documents.		A '''Header Row''' is the line (or lines) at the top of a table that contains the column labels, such as "Item No.", "Description", "Qty.", or "Total". In document processing, the header row provides essential context for identifying and aligning data in each column. Accurate header detection ensures that extracted values are mapped to the correct [[Data Column]]s, even when table layouts vary between documents.

	A '''Header Row Extractor''' is a specialized [[Value Extractor]] that detects the entire header row at once, rather than relying on individual header extractors for each column. This approach is especially useful when:		A '''Header Row Extractor''' is a specialized [[Value Extractor]] that detects the entire header row at once, rather than relying on individual header extractors for each column. The Header Row Extractor would be used in place of the Header Extractors on each Data Column. This approach is especially useful when:
	* Table headers span multiple lines or have complex formatting.		* Table headers span multiple lines or have complex formatting.
	* Column order varies between documents.		* Column order varies between documents.

Rpatton: /* Introduction */

2026-01-07T21:45:41Z

Introduction

← Older revision		Revision as of 16:45, 7 January 2026
Line 15:		Line 15:
	The '''Tabular Layout Table Extract Method''' is a powerful tool in Grooper for extracting structured tabular data from documents. It detects table headers, rows, and footers using a combination of value extractors and layout analysis. Tabular Layout is ideal for documents where tables are clearly defined, such as invoices, statements, and reports.		The '''Tabular Layout Table Extract Method''' is a powerful tool in Grooper for extracting structured tabular data from documents. It detects table headers, rows, and footers using a combination of value extractors and layout analysis. Tabular Layout is ideal for documents where tables are clearly defined, such as invoices, statements, and reports.

	Unlike other Table Extraction Methods (such as Row Match or Delimited Extract), Tabular Layout leverages header and footer labels, supports multi-line and stacked layouts, and provides advanced configuration for handling complex table structures.		Unlike other Table Extraction Methods (such as Row Match or Delimited Extract), Tabular Layout leverages header and footer labels, supports multi-line and stacked layouts, and provides advanced configuration for handling complex table structures. The Tabular Layout method is also more flexible than other methods. The table doesn't have to have a 'fixed' structure for Grooper to return information.

	== When to use ==		== When to use ==

Rpatton: /* Introduction */

2026-01-07T21:44:22Z

Introduction

← Older revision		Revision as of 16:44, 7 January 2026
Line 13:		Line 13:

	== Introduction ==		== Introduction ==
	The '''Tabular Layout Table Extract Method''' is a powerful tool in Grooper for extracting structured tabular data from documents. It ~~automatically~~ detects table headers, rows, and footers using a combination of value extractors and layout analysis. Tabular Layout is ideal for documents where tables are clearly defined, such as invoices, statements, and reports.		The '''Tabular Layout Table Extract Method''' is a powerful tool in Grooper for extracting structured tabular data from documents. It detects table headers, rows, and footers using a combination of value extractors and layout analysis. Tabular Layout is ideal for documents where tables are clearly defined, such as invoices, statements, and reports.

	Unlike other Table Extraction Methods (such as Row Match or Delimited Extract), Tabular Layout leverages header and footer labels, supports multi-line and stacked layouts, and provides advanced configuration for handling complex table structures.		Unlike other Table Extraction Methods (such as Row Match or Delimited Extract), Tabular Layout leverages header and footer labels, supports multi-line and stacked layouts, and provides advanced configuration for handling complex table structures.

Randallkinard: /* Using Named Groups */

2025-12-15T21:24:08Z

Using Named Groups

← Older revision		Revision as of 16:24, 15 December 2025
Line 157:		Line 157:
	For example, to capture a header row with "Item No.", "Description", and "Qty.", you might use:		For example, to capture a header row with "Item No.", "Description", and "Qty.", you might use:
	<pre>		<pre>
	(?<ItemNo>Item\s*No\.?)\s+(?<Description>Description)\s+(?<Qty>Qty\.?)		(?<ItemNo>Item\s*No\.?)\s+
			(?<Description>Description)\s+
			(?<Qty>Qty\.?)
	</pre>		</pre>

Randallkinard: /* Using Named Groups */

2025-12-15T21:22:41Z

Using Named Groups

← Older revision		Revision as of 16:22, 15 December 2025
Line 148:		Line 148:
	==== Using Named Groups ====		==== Using Named Groups ====

	A '''Named Group''' is part of a regular expression pattern that captures a specific portion of text and assigns it a name. In Grooper, named groups are used to map header labels directly to [[Data ~~Column]]s~~.		A '''Named Group''' is part of a regular expression pattern that captures a specific portion of text and assigns it a name. In Grooper, named groups are used to map header labels directly to Data Columns.

	*'''Named Group Syntax:'''		*'''Named Group Syntax:'''

Randallkinard: /* Basic setup */

2025-12-15T21:19:55Z

Basic setup

← Older revision		Revision as of 16:19, 15 December 2025
Line 66:		Line 66:
	# Right click on your Data Model.		# Right click on your Data Model.
	# Hover over "Add" and select "Data Table..." from the fly out menu.		# Hover over "Add" and select "Data Table..." from the fly out menu.
	# When the "Add" window appears, enter a name for your Data Table in the Name property.		# When the "Add" window appears, enter a name for your [[Data Table]] in the Name property.
	# When satisfied with the naming, click "Execute" to add the Data Table.		# When satisfied with the naming, click "Execute" to add the Data Table.
	# Add the Data Columns as children of the Data Table using one of the following methods:		# Add the Data Columns as children of the Data Table using one of the following methods:

Randallkinard: /* Basic setup */

2025-12-15T21:19:14Z

Basic setup

← Older revision		Revision as of 16:19, 15 December 2025
Line 59:		Line 59:

	== Basic setup ==		== Basic setup ==
	Grooper must be able to detect the columns and rows of a table to extract data. The Tabular Layout does this by identifying the column headers, which indicates where the columns are located on the document. Then at least one Value Extractor must be set on a Data Column that will return a result on each row of the table, giving Grooper context for where the rows of the table are located.		Grooper must be able to detect the columns and rows of a table to extract data. The Tabular Layout does this by identifying the column headers, which indicates where the columns are located on the document. Then at least one Value Extractor must be set on a [[Data Column]] that will return a result on each row of the table, giving Grooper context for where the rows of the table are located.

	'''Step 1: Create the Data Elements and select the Extract Method'''		'''Step 1: Create the Data Elements and select the Extract Method'''

Randallkinard: /* When to use */

2025-12-15T21:08:59Z

When to use

← Older revision		Revision as of 16:08, 15 December 2025
Line 27:		Line 27:
	'''Drawbacks:'''		'''Drawbacks:'''
	* Tabular Layout may be less effective for highly irregular tables or lists without clear headers.		* Tabular Layout may be less effective for highly irregular tables or lists without clear headers.
	* For simple delimited data (e.g., CSV), Delimited Extract may be more efficient.		* For simple delimited data (e.g., CSV), [[Delimited Extract]] may be more efficient.
	* Requires well-defined header labels or extractors for best results.		* Requires well-defined header labels or extractors for best results.

Rpatton at 15:56, 15 December 2025

2025-12-15T15:56:13Z

← Older revision		Revision as of 10:56, 15 December 2025
Line 1:		Line 1:
	{\|class="~~wip~~-box"		{{AutoVersion}}

			<blockquote>{{#lst:Glossary\|Tabular Layout}}</blockquote>

			{\|class="download-box"
	\|		\|
	~~'''WIP'''~~		[[File:Asset 22@4x.png]]
	\|		\|
	~~This article is a work-in-progress or created as a placeholder for testing purposes~~. ~~This article is subject to change and/~~or ~~expansion~~. ~~It may be incomplete, inaccurate,~~ or ~~stop abruptly~~.		You may download the ZIP(s) below and upload it into your own Grooper environment (version 2025). The first contains one or more '''Batches''' of sample documents. The second contains one or more '''Projects''' with resources used in examples throughout this article.
			* [[Media:2025 Wiki Tabular Layout Batches.zip]]
	~~This tag will be removed upon draft completion~~.		* [[Media:2025 Wiki Tabular Layout Project.zip]]
	\|}		\|}

	~~{{AutoVersion}}~~

	~~<blockquote>{{#lst:Glossary\|Tabular Layout}}</blockquote>~~

	== Introduction ==		== Introduction ==
Line 307:		Line 307:
	Sometimes when setting up your Tabular Layout Extractor, you may run into situations where the basics just aren't enough to capture the data you're looking for. There are a few extra properties you can configure to improve your results.		Sometimes when setting up your Tabular Layout Extractor, you may run into situations where the basics just aren't enough to capture the data you're looking for. There are a few extra properties you can configure to improve your results.

	== Maximum Header Distance ==		=== Maximum Header Distance ===

	'''Maximum Header Distance''' controls how far below the detected table header the first row is allowed to appear and still be considered part of the table. The distance is measured as a multiple of the average line height. If the first candidate row is farther than this limit, it will not be treated as part of the table.		'''Maximum Header Distance''' controls how far below the detected table header the first row is allowed to appear and still be considered part of the table. The distance is measured as a multiple of the average line height. If the first candidate row is farther than this limit, it will not be treated as part of the table.

	=== What it does ===		==== What it does ====
	* Ensures the first row starts close enough to the header.		* Ensures the first row starts close enough to the header.
	* Helps avoid mistakenly including unrelated content (decorative lines, spacing, notes) as part of the table.		* Helps avoid mistakenly including unrelated content (decorative lines, spacing, notes) as part of the table.
	* When set to '''0''', header proximity is not required (useful when rows begin immediately below or header detection is unreliable).		* When set to '''0''', header proximity is not required (useful when rows begin immediately below or header detection is unreliable).

	=== Configuration ===		==== Configuration ====
	# Open the [[Data Table]] that uses '''Tabular Layout'''.		# Open the [[Data Table]] that uses '''Tabular Layout'''.
	# In "Row Detection", set '''Maximum Header Distance''' to a value that fits your layout:		# In "Row Detection", set '''Maximum Header Distance''' to a value that fits your layout:
Line 334:		Line 334:


	== Using Footer labels ==		=== Using Footer labels ===

	Even after setting an extractor on a Data Column, Grooper may not be able to accurately detect rows. Often you might find that Grooper detects a row in a set of data that appears after the table on the document has ended. We can use Footer Labels to tell Grooper where to stop looking for rows, indicating where the table ends.		Even after setting an extractor on a Data Column, Grooper may not be able to accurately detect rows. Often you might find that Grooper detects a row in a set of data that appears after the table on the document has ended. We can use Footer Labels to tell Grooper where to stop looking for rows, indicating where the table ends.

	=== Without Label Sets ===		==== Without Label Sets ====

	To add a Footer Label when you are not using Label Sets:		To add a Footer Label when you are not using Label Sets:
Line 354:		Line 354:


	=== With Label Sets ===		==== With Label Sets ====

	To add a Footer Label:		To add a Footer Label:

Rpatton at 15:03, 15 December 2025

2025-12-15T15:03:24Z

← Older revision		Revision as of 10:03, 15 December 2025
Line 334:		Line 334:


	==== Using Footer labels ====		== Using Footer labels ==

	Even after setting an extractor on a Data Column, Grooper may not be able to accurately detect rows. Often you might find that Grooper detects a row in a set of data that appears after the table on the document has ended. We can use Footer Labels to tell Grooper where to stop looking for rows, indicating where the table ends.		Even after setting an extractor on a Data Column, Grooper may not be able to accurately detect rows. Often you might find that Grooper detects a row in a set of data that appears after the table on the document has ended. We can use Footer Labels to tell Grooper where to stop looking for rows, indicating where the table ends.

	~~'''~~Without Label Sets~~'''~~		=== Without Label Sets ===

	To add a Footer Label when you are not using Label Sets:		To add a Footer Label when you are not using Label Sets:
Line 354:		Line 354:


	~~'''~~With Label Sets~~'''~~		=== With Label Sets ===

	To add a Footer Label:		To add a Footer Label: