Why are there impossibles in my results?
While browsing your results, you may notice that a few of your fields may contain values marked as impossible. Captricity will mark any value impossible if it is illegible (ex. extremely messy handwriting or a scan too dark to read anything) or falls outside the range of allowed values (ex. a field defined with a range of 10-100 has a value of 200 written in). It is especially common to see impossibles if multiple options are circled on your forms, but your field definition allows for only one answer to be chosen.
Data can also be marked as impossible if the filled-in forms do not match the template. It is extremely important that your forms match the template you've selected. If there are variations, your data will not be captured well. You should create a new template or add additional versions to capture any variations in your forms.
To quickly check if your filled-in forms match your template, you can compare the original image of the filled-in form to the Template page. Click on a row header in your results to display an image of the entire form. You can see the original template by clicking on "Show template image" at the top.
A common reason for an impossible piece of data is if the field type is incorrectly defined. For example, a field that should be defined as multiple choice, but is defined as numeric field will return a lot of impossible values. To fix this, you can duplicate and edit your template to redefine the fields.
Defining each piece of information you want captured as a clear, distinct field can help reduce the number of impossibles in your results. For example, drawing a large field over an entire column in a table or a large area of your form is confusing - our system isn't sure what data you want captured. Be sure to properly draw and define your fields to prevent such issues.
Additionally, ambiguous fields can lead to impossibles or incorrectly captured data. This is especially true for long alphanumeric codes or large fields. Adding in special instructions to clearly explain what data you want captured can help reduce the number of impossibles in your results.
Note: If the original image of the field doesn't look like a form at all and is impossible to read, as in the example below, then the form likely didn't match the template. This skewing of the image occurs as our algorithm attempts to match the form with the template. Since they don't match, the form becomes illegible. To process these different forms, you'll need to run new jobs with new templates that match the forms.