Patch Code Detection

A combination of the following flags:

The 'Read Directions' property specifies the scan direction(s) used to search for patch codes in the image. Multiple directions can be selected to detect barcodes with inconsistent or unknown orientations.

• 'South' scans from the top of the page downward (the most common orientation for patch codes).
• Enabling additional directions (East, West, North) can help detect rotated or upside-down barcodes, but may increase processing time.

Important: Some patch code values may be interpreted differently if read upside down. For example, a Patch T barcode read upside down may be detected as a Patch 3.

Example: To detect patch codes regardless of orientation, select all directions. For standard forms, 'South' is usually sufficient.

The 'Quiet Zone Tolerance' property controls how strictly the patch code reader enforces the requirement for a clear area (quiet zone) around the barcode. A value of 1.0 requires a perfect quiet zone, while 0.0 ignores the quiet zone requirement entirely.

• Higher values (closer to 1) reduce false positives and are recommended for patch codes, which are typically unobstructed.
• Lower values (closer to 0) may be needed for barcodes embedded in document content, but can increase the risk of false positives.

Example: For most patch code separation workflows, use a value between 0.5 and 1.0.

Can be one of the following values:

The 'Read Quality' property determines the thoroughness of the patch code search:

• Fastest: Performs a coarse scan for barcode features, prioritizing speed over completeness. May miss some patch codes.
• Default: Balances speed and accuracy. Suitable for most use cases.
• MostAccurate: Performs a fine-grained, multi-pass scan to detect every possible patch code. Recommended for critical separation workflows or low-quality images.

Example: Use 'MostAccurate' for batch separation where missing a patch code could cause data loss. Use 'Fastest' for high-quality, uniform documents where speed is critical.

The 'Scan Interval' property controls how many lines of the image are skipped between scans:

• A value of 1 scans every line for maximum accuracy (slowest).
• Higher values (e.g., 10, 100, 500) scan every Nth line, increasing speed but potentially missing small or misaligned patch codes.

Example: For most patch code separation workflows, a value between 100 and 500 provides a good balance of speed and accuracy. Lower the value if patch codes are small or may be missed at higher intervals.

The 'Command Type Name' property shows the user-friendly name of the IP Command as it appears in the Grooper UI. This helps users identify which command is being configured or executed, especially when working with IP Profiles containing multiple commands.

This property is read-only and is automatically set based on the command's type.

The 'Supported Pixel Formats' property lists the image pixel formats that the IP Command can process. If an image does not match one of these formats, the command will be skipped for that image.

• By default, all pixel formats are supported unless a derived command restricts this list.
• Example formats include Pixel8bppGrayscale, Pixel24bppBgr, and Pixel1bppIndexed.

Use this property to verify compatibility when building IP Profiles or troubleshooting why a command did not execute.