I created a document definition (fcdot) using the Flexicapture engine SDK.
To keep things simple, I defined only a single page which contains 3 Anchors and 2 data fields

When I load this definition and try detecting images the following happens

  1. If I use the SAME image as I used for creating the definition, all the field positions are correct in the recognised result
  2. If I use any other image (even those which have very small difference in height and width), the field locations are offset by some numbers. All the fields are offset by the same number. The offsets depends on which Anchors I define

asked 13 Mar '14, 16:12

sreejith's gravatar image

sreejith
13114


Dear Sreejith,

On the document definition file that you have sent us in your last letter some inaccuracy in matching anchors taking place, that is why this definition cannot be match on the other documents. As we can see the left bottom corner is absent on the image that you used for creating a form, instead of the corner there is a black area in the bottom of the picture. The left top square that you have matched as anchor too have rather complex boundaries, so it is not a very suitable element for anchor. Please, try to set as third anchor some static text, for example the full line “PAYBACK REGISTRATION FORM”.

Hope this information will be helpful.

link

answered 14 Mar '14, 16:21

SDK_support's gravatar image

SDK_support ♦♦
2763

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×18
×16
×1

Asked: 13 Mar '14, 16:12

Seen: 1,278 times

Last updated: 14 Mar '14, 16:21

© 2016 ABBYY. All rights Reserved. www.ABBYY.com | Privacy Policy | Legal