Feature Request: Checkpoints for Route Visit Monitoring

Feature Request: Checkpoints for Route Visit Monitoring

Summary

I would like to suggest a new feature for Traccar: map-based checkpoints that can be automatically marked as visited when a vehicle passes near them.

The main use case is route monitoring for services such as garbage collection, street cleaning, inspections, maintenance teams, school transport, and other operations where it is important to verify whether a vehicle actually passed through specific locations.

Proposed Behavior

Administrators would be able to create checkpoints directly on the map by placing a pin.

Each checkpoint could contain information such as:

• Name
• Latitude and longitude
• Configurable detection radius
• City
• Area or neighborhood
• Route/group
• Active/inactive status

The interface could also provide filters by:

• City
• Route
• Vehicle
• Date
• Checkpoint status

Checkpoint Status

For daily monitoring, checkpoints could have a simple visual status:

• Not visited
• Visited
• Optional: probable/partial visit

When a vehicle enters the configured radius of a checkpoint, Traccar would automatically register the visit and change its status to visited for that day.

For example:

Checkpoint A
Status: Visited
Vehicle: Garbage Truck 03
Time: 08:42
Date: 2026-09-10

The checkpoint could automatically appear as not visited again on the next day, while keeping the historical visit records.

Visit History

It would be useful to store information such as:

• Checkpoint
• Vehicle
• Device
• Position
• Date/time
• Minimum distance from the checkpoint
• Route

This would allow reports such as:

Route: Downtown Collection

Expected checkpoints: 120
Visited checkpoints: 114
Not visited: 6
Coverage: 95%

Possible Implementation

This feature could potentially reuse some of Traccar's existing geofence functionality.

A checkpoint could internally behave similarly to a small circular geofence with a configurable radius.

When a device enters the checkpoint area, an event similar to geofenceEnter could be used to register the visit.

However, having a dedicated checkpoint concept could make the interface and reporting much easier for operational use cases where hundreds or thousands of small points need to be monitored.

Optional Improvement

GPS reporting intervals can sometimes cause a vehicle to pass near a checkpoint without sending a position exactly inside its radius.

An optional improvement would be to check whether the line segment between the previous and current GPS positions passed within the checkpoint radius.

This could reduce false "not visited" results.

Example Use Case

In a municipal garbage collection operation:

Garbage Truck
     ↓
Checkpoint 01 → 
     ↓
Checkpoint 02 → 
     ↓
Checkpoint 03 → 
     ↓
Checkpoint 04 → 

At the end of the route, supervisors could immediately see which collection points were visited and which were missed.

Why This Could Be Useful

Although geofences already provide similar location-based detection, a dedicated checkpoint workflow could make Traccar more suitable for operational route verification and service execution monitoring.

It could be useful for:

• Garbage collection
• Street cleaning
• Public works
• Inspection routes
• Delivery operations
• Utility maintenance
• School transport
• Municipal service fleets

Thank you for considering this feature.