Bad Spots Discrimination

2 posts / 0 new
Last post
Last seen: 8 months 2 weeks ago
Joined: 2013/09/18 - 20:39
Bad Spots Discrimination

The sensitivity of the current software is great, but sometimes we see false decodes that the user does not have a chance to edit before being embedded with all of the good spots into the database. Perhaps there could be an option for users to set a flag ( with their registration details or in setting the database parameters) that decodes below say -28dB AND no matching stored locator would be rejected.

That might help automated database processors avoid including bad spots in their products.

Perhaps there is a better method of avoiding " Spots in the Sea" ?