Why do non-ASCII plate characters become corrupted in a VaxALPR integration?
Answered by ANPR AI·Sourced
Short answer
Check the reporting template and receiver encoding.
Explanation
The developer guide provides a UTF-8 plate output token.
Things to check
- Selected plate token
- Message bytes
- Receiver decoding
What to do
Use the documented UTF-8 output where required and preserve that encoding end to end.
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 VaxALPR on i-PRO read Latin plates but miss plates with small Arabic characters?Why does VaxALPR on i-PRO fail to retain unsent plate messages locally?Why does VaxALPR’s TCP connection close after sending one plate?Why does VaxALPR merge two similar plate reads into one vehicle event?
Browse all ANPR questions
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.