Plate
Visible characters interpreted with an individual confidence level.
LICENSE PLATE OCR SOFTWARE • EMBEDDED ALPR / LPR
Our proprietary engine analyzes the image itself, turns each reading into a structured event and keeps confidence and capture context attached. The module can run onboard and integrate with vehicles, applications and platforms.
For projects that already have a vehicle, application or platform and need to embed Areatec's OCR engine.
STRUCTURED RESULT
The module returns more than a character string. Each hypothesis can retain the visual evidence and the data another system needs to review it, query an authorized source or apply the configured rule.
Visible characters interpreted with an individual confidence level.
Visual classification produced directly from the image.
Visual attribute with its own confidence and the possibility of an inconclusive result.
Image, time, camera, channel and equipment associated with the reading source.
PROCESSING
The camera records the scene and identifies the source channel.
1Processing finds the region compatible with a license plate.
2Characters receive a hypothesis and confidence level.
3Make, model and color are classified in the image itself.
4Result, image, time and equipment remain associated.
5The structured event moves to the project's authorized workflow.
6PERFORMANCE WITH CRITERIA
In tests conducted with our OCR, we achieved 98.7% accuracy in license plate reading.
This is a test result, not a universal percentage for every scenario. Capture conditions, installation and configuration affect the reading.
For each project, performance is confirmed with a sample representative of the actual route and acceptance criteria defined for the operation.
Learn how to evaluate accuracy and performanceField of view, distance, height, focus and stabilization.
Speed, approach, direction and set vibration.
Lighting, rain, glare, occlusion and plate condition.
Hardware, simultaneous channels and modules running on the device.
Representative scenes and annotated ground truth before testing.
Correct, incorrect and inconclusive results separated by condition.
INTEGRATION
The delivery method is defined by the contracted architecture. Hardware, channels, event format, credentials, retries and audit records are part of the technical design and acceptance test.
A module, SDK or library can run the required processing on onboard hardware.
API, web service, webhook, structured file or queue can transport authorized events.
OCR reading, external query and operating decision remain identifiable in the workflow.
CHOOSE THE RIGHT SCOPE
This separation prevents the wrong scope from being selected and takes each team directly to the information it needs.
For embedding the reading engine into equipment, an application or a platform.
See integrationComplete productOlho Vivo Patrol is the complete product, with the vehicle, cameras, processing and field-operation capabilities.
Explore PatrolTechnical contentFor understanding OCR, LPR, ALPR, applications and performance evaluation.
Open the centerRESPONSIBLE USE
Purpose, legal basis, queried sources, access, retention, security and review are defined for each operation. A reading does not issue a citation by itself, and an inconclusive result should not be treated as confirmation.
FREQUENTLY ASKED QUESTIONS
It is a software module that locates visible license plates in images, reads their characters and interprets visual vehicle attributes such as make, model and color. The engine can run on onboard hardware or integrate with an application or platform while retaining confidence and capture context.
Vehicle OCR is the technical capability for onboard capture and reading. Olho Vivo Patrol is the complete vehicle product, which can combine that capability with field operations, telemetry, communication and other project specific resources.
No. The reading produces data for an operational workflow. Queries, rule checks, evidence review and any administrative action follow the procedure and authority of the responsible public body.
Yes. In addition to reading the plate, Areatec's engine analyzes the image itself to visually classify vehicle make, model and color, with a confidence level for each result. This classification does not depend on a vehicle registry query. When the project includes an authorized external source, it may be used later for verification or to add data that cannot be inferred from the image.
With a representative operating sample, previously annotated ground truth and criteria defined before testing. The report should separate correct, incorrect and inconclusive readings by route, lighting, plate, camera and hardware conditions.
Local capture and processing can continue according to the contracted architecture. Remote queries and synchronization depend on connectivity and should use queues, states and reconciliation. Behavior must be validated during acceptance testing.
Field of view, focus, distance, height, stabilization, speed, direction of approach, lighting, glare, rain, occlusion, plate condition, hardware and the number of channels processed at the same time.
Yes. Depending on the contracted architecture, delivery may use an onboard module, SDK or library, API, web service, webhook, structured file or queue. The technical contract defines hardware, format, credentials and audit while keeping the OCR event, external query and operating decision separate.
The technical conversation starts with the image source, channel count, available processing, output format and acceptance sample.
Request a technical evaluation