When FindFingerprint detects a match, it automatically computes the offsets that are required to correct the image registration. It stores these offsets in the Image_Offset variable in the page. The ReadZones action uses the offsets when it sets the runtime field positions.
The following example shows the runtime data for a page that Taskmaster identified correctly and registered automatically by using FindFingerprint.
<P id="TM000003">
<V n="TYPE">Air_Ticket</V>
<V n="STATUS">49</V>
<V n="IMAGEFILE">tm000003.tif</V>
<V n="ScanSrcPath">c:\datacap\traveldocs\images\problem_images_page_3.tif</V>
<V n="RecogStatus">0</V>
<V n="Confidence">0.8689438</V> <-- Confidence level high enough for a match
<V n="Image_Offset">-24,-20</V> <-- Offsets calculated automatically by FindFingerprint
<V n="TemplateID">566</V> <-- Matching fingerprint ID
<V n="Fingerprint Created">No</V>
</P>
FindFingerprint calculates the offsets without using anchor objects. However, the offsets it can handle are small. The CalculateOffset action in the Autodoc library can increase the size that the offsets it can handle. Increasing the size that offsets handle can slow down the matching process.
Library | Action | Description |
---|---|---|
Autodoc | CalculateOffset | Sets the maximum offset supported when you are matching pages to fingerprints. |