I am unable to extract the values from the OMR template- Please help

Hello,

I am unable to extract the values from the OMR template, Please help.

I have attached my sample image and amr file with this post.

always the value is EMPTY..

Please let me know where i am wrong.

Hi Prashanth,


Thank you for sharing your sample template and the scanned sheet image. We have evaluated the scenario on our end while using the Template Editor as well as the code snippet provided below. Unfortunately, we are unable to get any results as both Template Editor and code return null. In order to further investigate the problem cause, we have logged a ticket (OCR-33858) in our bug tracking system and requested the core development team to analyze the situation. Please spare us little time to isolate the problem cause on our end. In the meanwhile, we will keep you posted with updates in this regard.

C#

//Load template file
OmrTemplate template = OmrTemplate.Load(MyDir + “ffffffffffffff.amr”);
//Load the image to be analyzed
OmrImage image = OmrImage.Load(MyDir + “test.bmp”);

// Instantiate the recognition engine for the template
OmrEngine engine = new OmrEngine(template);

// Extract data. This template has only one page.
OmrProcessingResult result = engine.ExtractData(new OmrImage[] { image });

//Load actual result from
Hashtable OmrResult = result.PageData[0];

//Get Collection of Keys
ICollection key = OmrResult.Keys;

foreach (string k in key)
{
Console.WriteLine(k + ": " + OmrResult[k]);
}

We are sorry for the inconvenience caused to you.

Hi Prashanth,


Thank you for your patience with us.

We have investigated the presented scenario, and were able to isolate the problem cause. The grid element in your provided template captures a part of the border that surrounds OMR marks. Current OMR data extraction algorithm does not handle such cases well, so we’ve updated the template to exclude the borders from the element’s area (see attached ‘updated.amr’), The extraction now works normally with Template Editor as well as the code snippet as provided in the previous post.

Please note, we will look further into this matter to enhance the OMR engine with future releases so it can handle such cases without any issue. In case you have further questions or concerns, please feel free to write back.

Hi again,


This is to inform you that we have resolved the ticket logged earlier as OCR-33858. Please note, the fix will be included in the upcoming release of Aspose.OCR for .NET 2.6.0, that is scheduled for the first week of June 2015, As soon as the next release is available for public use, we will notify you here.

The issues you have found earlier (filed as OCR-33858) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.