Determine the runtime field positions by using anchor offsets

The pat_RecogMatch_Id uses the anchor offsets to determine the Image_Offset value it writes to the runtime page file.

The following example shows how the field positions are determined.

<V n="Image_Offset">-100,-101</V>

The value here (-100, -101) is from the same Hotel #3 page in How the pat_RecogMatch_Id action works. In this example, you can see that pat_RecogMatch_Id used the offset value from Text_Anchor_2.

Important: The pat_RecogMatch_Id action does not create a page data file and does not store the individual offset for each anchor field.

Later on, when Datacap runs the ReadZones action, it uses the Image_Offset value to compute the position of each runtime field, for example:

<F id="Arrival_Date">
   <V n="TYPE">Arrival_Date</V>
   <V n="Position">511,506,813,585</V>
   <V n="STATUS">0</V>
   etc.

Compare the field positions that are defined in the fingerprint, which you can see in the Properties pane, with the field positions in the runtime page file. You can see how Datacap used the offset value (-100, -101) to compute the position of each data field.

Field	Fingerprint 572	Runtime page
Arrival_Date	411,405,713,484	511,506,813,585
Departure_Date	1154,412,1450,488	1254,513,1550,589
Total_Cost	1150,781,1331,860	1250,882,1431,961