Why did SharpV anonymized plate identifiers change after a configuration change?
Answered by ANPR AI·Sourced
Short answer
Check whether the anonymization salt changed.
Explanation
The HTTP/HTTPS extension uses a salt when anonymizing plate data.
Things to check
- Salt value
- Anonymization setting
- Identifier before and after
What to do
Keep the intended salt consistent across the required matching period. Treat cross-salt matching limitations as part of the data design.
Was this answer helpful?
Your vote decides which questions we answer next.
Cloud API
Test plate and vehicle recognition on your own images.
Send a photo or camera frame to our API and get the plate, country, make and model back as JSON. Start free, or run the same models on your own servers.
- 100 free credits every month, no card
- Plates for Saudi Arabia, Qatar, Kuwait, Bahrain and Oman
- Cloud API or on-premise deployment
What to read next
ProductCloud ANPR APISelf-serve plate and vehicle recognition API with a free tier, or run it on-premise.Read GuideConnect an IP camera to ANPRStep-by-step: RTSP streams and snapshots from the cameras you already have, sent to the API.Read ComparisonANPR camera alternativeWhat a dedicated ANPR camera costs against a standard IP camera plus plate-recognition software.Read
Related questions
Why does a SharpV G3 fail when powered by an older SharpV PoE injector?Why do SharpV HTTP events work but HTTPS events fail?Why are only high-confidence SharpV reads reaching my HTTP receiver?Why did queued SharpV HTTP reads disappear when I disabled offline retention?
Browse all ANPR questions
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.