2024:OCR Synthesis (Concept) - Revision history

Dgreenwood at 19:26, 3 April 2025

2025-04-03T19:26:21Z

← Older revision		Revision as of 14:26, 3 April 2025
Line 449:		Line 449:

	The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.		The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.

			== Azure OCR incompatibility ==

			Azure OCR is NOT compatible with Grooper's "Image Segmentation" and "Segment Reprocessing" Synthesis features. The Read API will return an error if you attempt to configure these properties in an OCR Profile. The image snippets Grooper uses to process the segments fall under Azure's minimum image dimensions.

			OUR BEST PRACTICE ADVICE: Set the "Synthesis" property to Disabled when using Azure OCR in an OCR Profile.

Dgreenwood: /* Azure OCR incompatibility */

2025-04-03T19:25:53Z

Azure OCR incompatibility

← Older revision		Revision as of 14:25, 3 April 2025
Line 449:		Line 449:

	The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.		The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.

	~~=== Azure OCR incompatibility ===~~

	Azure OCR is NOT compatible with the Segment Reprocessing feature. The Read API will return an error if you attempt to configure this property in an OCR Profile. The image snippets Grooper uses to reprocess the segments fall under Azure's minimum image dimensions.

Dgreenwood: /* Known Concerns */

2025-04-03T19:16:26Z

Known Concerns

← Older revision		Revision as of 14:16, 3 April 2025
Line 450:		Line 450:
	The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.		The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.

	=== ~~Known Concerns~~ ===		=== Azure OCR incompatibility ===

	Azure OCR is NOT compatible with the Segment Reprocessing feature. The Read API will return an error if you attempt to configure this property in an OCR Profile. The image snippets Grooper uses to reprocess the segments fall under Azure's minimum image dimensions.		Azure OCR is NOT compatible with the Segment Reprocessing feature. The Read API will return an error if you attempt to configure this property in an OCR Profile. The image snippets Grooper uses to reprocess the segments fall under Azure's minimum image dimensions.

Dgreenwood: /* Segment Reprocessing */

2025-04-03T19:15:59Z

Segment Reprocessing

← Older revision		Revision as of 14:15, 3 April 2025
Line 449:		Line 449:

	The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.		The reason behind this is how colons are used on documents. Typically, they themselves are used to break information out into meaningful segments. On the left side of the colon is some kind of label identifier. On the right followed by a gap is a piece of information that label pertains to. These labels are very important and the pieces of information they relate to are very important. Making sure both can be reprocessed independently tends to yield better OCR results and therefore data extraction down the line.

			=== Known Concerns ===

			Azure OCR is NOT compatible with the Segment Reprocessing feature. The Read API will return an error if you attempt to configure this property in an OCR Profile. The image snippets Grooper uses to reprocess the segments fall under Azure's minimum image dimensions.

Dgreenwood: Dgreenwood moved page OCR Synthesis (Concept) to 2024:OCR Synthesis (Concept)

2025-03-03T17:34:54Z

Dgreenwood moved page OCR Synthesis (Concept) to 2024:OCR Synthesis (Concept)

← Older revision	Revision as of 12:34, 3 March 2025
(No difference)

Randallkinard: // via Wikitext Extension for VSCode

2024-12-10T15:25:16Z

// via Wikitext Extension for VSCode

Show changes

Randallkinard at 16:40, 28 August 2024

2024-08-28T16:40:21Z

← Older revision		Revision as of 11:40, 28 August 2024
Line 1:		Line 1:
	{{~~Migrated2023~~}}		{{Migrated}}
	{{2023:{{PAGENAME}}}}		{{2023:{{PAGENAME}}}}

Randallkinard: Randallkinard moved page OCR Synthesis to OCR Synthesis (Concept): new naming convention

2024-04-16T20:43:18Z

Randallkinard moved page OCR Synthesis to OCR Synthesis (Concept): new naming convention

← Older revision	Revision as of 15:43, 16 April 2024
(No difference)

Dgreenwood: Removed redirect to OCR Synthesis - 2023

2023-12-22T18:04:27Z

Removed redirect to OCR Synthesis - 2023

← Older revision		Revision as of 13:04, 22 December 2023
Line 1:		Line 1:
	~~#REDIRECT [[OCR Synthesis -~~ 2023]]		{{Migrated2023}}
			{{2023:{{PAGENAME}}}}

Randallkinard: Changed redirect target from OCR Synthesis - 2.8 to OCR Synthesis - 2023

2023-10-30T16:58:09Z

Changed redirect target from OCR Synthesis - 2.8 to OCR Synthesis - 2023

← Older revision		Revision as of 11:58, 30 October 2023
Line 1:		Line 1:
	#REDIRECT [[OCR Synthesis - ~~2.8~~]]		#REDIRECT [[OCR Synthesis - 2023]]