2.80:Anchored Extract - Revision history

Dgreenwood at 15:06, 5 August 2025

2025-08-05T15:06:22Z

← Older revision		Revision as of 10:06, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-		\|-

Dgreenwood: Dgreenwood moved page Anchored Extract to 2.80:Anchored Extract

2023-12-22T14:43:56Z

Dgreenwood moved page Anchored Extract to 2.80:Anchored Extract

← Older revision	Revision as of 09:43, 22 December 2023
(No difference)

Dgreenwood at 15:18, 9 December 2022

2022-12-09T15:18:23Z

@@ Line 1: / Line 1: @@
 <blockquote style="font-size:14pt>
 '''Anchored Extract''' extracts text in a rectangular region (often referred to as a "zone" or "extraction zone") near a text label (referred to as the "anchor")
@@ Line 6: / Line 17: @@
 ==About==
 {|cellpadding=10 style="margin:auto"

Dgreenwood at 15:14, 9 December 2022

2022-12-09T15:14:50Z

← Older revision		Revision as of 10:14, 9 December 2022
Line 268:		Line 268:
	\|Output Full Region\|\|False\|\|By default, any review module will highlight just the extracted text. Set Output Full Region to “True” to show the entire potential extraction zone. This can be useful when configuring the zone.		\|Output Full Region\|\|False\|\|By default, any review module will highlight just the extracted text. Set Output Full Region to “True” to show the entire potential extraction zone. This can be useful when configuring the zone.
	\|}		\|}

			[[Category:Articles]]
			[[Category:Version 2.80]]

Dgreenwood at 13:05, 19 October 2020

2020-10-19T13:05:07Z

← Older revision		Revision as of 08:05, 19 October 2020
Line 8:		Line 8:

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-style="background-color:#~~36b0a7~~; color:white"		\|-style="background-color:#f89420; color:white"
	\|style="font-size:14pt"\|~~'''FYI'''~~\|\|''Anchored Extract'' was replaced by the ''[[Read Zone]]'' ~~functionality~~ in version 2.90. The same results can be achieved with slightly different configuration of this '''''Value Extractor'''''. Please visit the ''[[Read Zone]]'' article for more information if you're trying to perform ''Anchored Extract'' in version 2.90.		\|style="font-size:14pt"\|⚠\|\|''Anchored Extract'' was replaced by the ''Read Zone'' extractor in version 2.90. The same results can be achieved with slightly different configuration of this '''''Value Extractor'''''. Please visit the ''[[Read Zone]]'' article for more information if you're trying to perform ''Anchored Extract'' in version 2.90.
	\|}		\|}

Dgreenwood at 19:20, 9 October 2020

2020-10-09T19:20:41Z

← Older revision		Revision as of 14:20, 9 October 2020
Line 6:		Line 6:

	==About==		==About==

			{\|cellpadding="10" cellspacing="5"
			\|-style="background-color:#36b0a7; color:white"
			\|style="font-size:14pt"\|'''FYI'''\|\|''Anchored Extract'' was replaced by the ''[[Read Zone]]'' functionality in version 2.90. The same results can be achieved with slightly different configuration of this '''''Value Extractor'''''. Please visit the ''[[Read Zone]]'' article for more information if you're trying to perform ''Anchored Extract'' in version 2.90.
			\|}



	{\|cellpadding=10 style="margin:auto"		{\|cellpadding=10 style="margin:auto"

Randallkinard at 18:35, 28 July 2020

2020-07-28T18:35:07Z

← Older revision		Revision as of 13:35, 28 July 2020
Line 210:		Line 210:


	The "Line Separator" property specifies how multiple lines of text are broken up. If you have a zone with multiple lines of text, like the example below, they will be returned one line immediately following the other ("Benjamin FinjaminCrigamin Flimfam" in this case). You must specify a ~~seperator~~ here, such as a space or a comma, if you want the lines broken up (the regular expression characters \r \n \t \f and \s may also be used).		The "Line Separator" property specifies how multiple lines of text are broken up. If you have a zone with multiple lines of text, like the example below, they will be returned one line immediately following the other ("Benjamin FinjaminCrigamin Flimfam" in this case). You must specify a separator here, such as a space or a comma, if you want the lines broken up (the regular expression characters \r \n \t \f and \s may also be used).

Mharrison: /* Use Case 1 */

2020-06-01T14:37:13Z

Use Case 1

← Older revision		Revision as of 09:37, 1 June 2020
Line 33:		Line 33:
	=== Use Case 1 ===		=== Use Case 1 ===

	Any structured form where you can reliably count on extracted data to be in the same relative position to a label can take advantage of Anchored Extract. The extractor is doubly useful for data inside tables or other boxed in regions, taking advantage of "snapping" the extraction zone to the boxed in borders.		Any structured form where you can reliably count on extracted data to be in the same relative position to a label can take advantage of Anchored Extract. The extractor is doubly useful for data inside tables or other boxed in regions, taking advantage of "snapping" the extraction zone to the boxed in borders. The traditional approach of using Key-Value Pairs to understand Horizontal and Vertical relationships between the label and value will fail in cases where a form's designer chose to align the label to the top-left corner of a bounding box, while aligning the value to the bottom right corner of a bounding box. The Anchored Extract technique will still understand the relationship without having to worry about these formatting challenges.

	=== Use Case 2 ===		=== Use Case 2 ===

Mharrison: Added links to Layout Data article.

2020-03-24T14:25:27Z

Added links to Layout Data article.

← Older revision		Revision as of 09:25, 24 March 2020
Line 13:		Line 13:
	\|}		\|}

	Anchored Extract is especially useful for structured forms where information resides in labeled boxes. In these cases, the document's ~~layout data~~ (detected through an Image Processing command) can be used to position the extraction zone to the nearest borders around the anchor. As seen in the examples below, the extraction zone automatically "snaps" to the nearest box around the anchor label.		Anchored Extract is especially useful for structured forms where information resides in labeled boxes. In these cases, the document's [[Layout Data]] (detected through an Image Processing command) can be used to position the extraction zone to the nearest borders around the anchor. As seen in the examples below, the extraction zone automatically "snaps" to the nearest box around the anchor label.

	{\|cellpadding=10 style="margin:auto"		{\|cellpadding=10 style="margin:auto"
Line 53:		Line 53:
	The anchor is found using a data extractor. In order to find a value, you will need OCR text or extracted native text from a PDF. To do this, run your document through the Recognize activity.		The anchor is found using a data extractor. In order to find a value, you will need OCR text or extracted native text from a PDF. To do this, run your document through the Recognize activity.

	If you want to snap the extraction region within the borders of a box, you must obtain the document’s ~~layout data~~. To do this, run a Line Detection or Line Removal command on an IP Profile during a Recognize or Image Processing activity. These activities must be run on the Page level.		If you want to snap the extraction region within the borders of a box, you must obtain the document’s [[Layout Data]]. To do this, run a Line Detection or Line Removal command on an IP Profile during a Recognize or Image Processing activity. These activities must be run on the Page level.
	</tab>		</tab>
	<tab name="Step 1">		<tab name="Step 1">

Dgreenwood: /* Use Case 2 */

2020-02-19T15:34:22Z

Use Case 2

← Older revision		Revision as of 10:34, 19 February 2020
Line 37:		Line 37:
	=== Use Case 2 ===		=== Use Case 2 ===

	Text inside the extraction zone can be reprocessed by a second OCR Profile. This is extremely useful on documents where the labels are easily extracted by one OCR Profile, but the values themselves are more accurately read by a different one. For example, one OCR engine may perform better on one font, but a second may do better at another. Grooper 2.80 comes installed with Transym and Tesseract OCR engines. Transym does a great job recognizing most fonts. However, it ~~does~~ a poor job at recognizing the OCRA font. Tesseract has unique functionality to handle the OCRA font.		Text inside the extraction zone can be reprocessed by a second OCR Profile. This is extremely useful on documents where the labels are easily extracted by one OCR Profile, but the values themselves are more accurately read by a different one. For example, one OCR engine may perform better on one font, but a second may do better at another. Grooper 2.80 comes installed with Transym and Tesseract OCR engines. Transym does a great job recognizing most fonts. However, it can do a poor job at recognizing the OCRA font. Tesseract has unique functionality to handle the OCRA font.

	In the example below, the text reading "Wyatt" inside the extraction zone could be reprocessed by an OCR Profile using the Tesseract engine to accurately extract the name "Wyatt".		In the example below, the text reading "Wyatt" inside the extraction zone could be reprocessed by an OCR Profile using the Tesseract engine to accurately extract the name "Wyatt".