hi, i've been testing around with rotated images. the ocr and everything works fine, but there will be some image correction that's applied before, right (i.e. "undoing" the rotation). the coordinates in the xml output though are not the corrected ones but the original ones of the rotated image. is it possible to get the corrected coordinates instead? i need to calculate if words are aligned vertically, so this would be quite important for that. thanks

asked 15 Sep '14, 23:30

kofoapp's gravatar image

kofoapp
1113

Hi, we are consulting with our developers concerning your question.

(17 Sep '14, 18:16) Oksana Serdyuk ♦♦

Now there is no way to get coordinates of a deskewed image directly in ABBYY Cloud OCR SDK. You can do it only for two processing iterations: one needs to get the deskewed image and then you should send this deskewed image for re-recognition.

link

answered 20 Sep '14, 02:34

Oksana%20Serdyuk's gravatar image

Oksana Serdyuk ♦♦
1.5k16

ok thank you! how exactly can i get the deskewed image?

link

answered 22 Sep '14, 17:17

kofoapp's gravatar image

kofoapp
1113

There is no API to save image after deskewing and rotation in Cloud OCR SDK. But you can export result to the pdfSearchable format and then use this PDF for re-recognition or at first convert this pdfSearchable file to an image by your application and then process it again.

link

answered 23 Sep '14, 01:06

Oksana%20Serdyuk's gravatar image

Oksana Serdyuk ♦♦
1.5k16

cool, thanks very much! i'd have to pay for two processes then though, right? or is there a way to do it with just one document credit?

(23 Sep '14, 11:20) kofoapp

Unfortunately, now there is no way to do it with one document credit.

However we are consulting with our developers and analyst about this issue. Could you please specify if you need to get the coordinates of the image after all preprocessing steps or it is enough to get the coordinates of the deskewed image?

(24 Sep '14, 18:32) Oksana Serdyuk ♦♦

best would be to get them after all preprocessing steps, thank you!

(06 Oct '14, 17:49) kofoapp

hi oksana, are there any news about this issue? there's one other thing i have noticed with the workaround solution (reprocessing the searchable pdf): in many cases i get worse results when sending the pdf than with the original image, even if the correct text recognition from the first round is stored with the pdf (e.g. additional spaces)

(16 Oct '14, 19:17) kofoapp

Thank you for this information. We are still working on this issue and I will give you our concrete answer next week. Sorry for inconvenience!

(17 Oct '14, 17:41) Oksana Serdyuk ♦♦

We are extremely sorry for a long silence. After a long consultation it was decided to add the separate xml export format with the coordinates for the corrected image - xmlForCorrectedImage. This feature is going to be implemented in the nearest future. I will inform you about it.

(29 Oct '14, 18:39) Oksana Serdyuk ♦♦

great, thanks a lot!

(29 Oct '14, 19:22) kofoapp
showing 5 of 7 show 2 more comments

I’m glad to inform you that we have implemented a new export format for the processImage method, namely xmlForCorrectedImage. Now to get the coordinates of the corrected image it is enough to set exportFormat= xmlForCorrectedImage. The corresponding documentation will be updated soon.

link

answered 10 Nov '14, 15:23

Oksana%20Serdyuk's gravatar image

Oksana Serdyuk ♦♦
1.5k16

perfect, tested it and works great! thanks very much

link

answered 16 Nov '14, 21:59

kofoapp's gravatar image

kofoapp
1113

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:

×49
×11
×2

Asked: 15 Sep '14, 23:30

Seen: 3,614 times

Last updated: 16 Nov '14, 21:59

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