I'm working on an external application that uses Traccar as the tracking platform.
In my application, I use Calendars to represent operational schedules. For example, a multi-day event has one calendar for each operational day.
Each calendar is associated with additional information outside Traccar, such as the route that will be used on that day.
What I'm trying to determine is the best way to associate these schedules with a Group of devices.
At the moment I can think of several approaches:
- Maintain an external mapping between Groups and Calendars.
- Store the relationship in custom attributes.
- Use another Traccar object that I'm overlooking.
I'm not asking for a new Traccar feature. I'm interested in understanding what the recommended approach is when an external application needs to know which operational schedule belongs to a particular group.
How have others solved this kind of integration?
I'm especially interested in solutions that stay as close as possible to the existing Traccar data model and API.
Any suggestions or best practices would be appreciated.
I would store it in your application because managing it on individual devices would get old fast.
I'm working on an external application that uses Traccar as the tracking platform.
In my application, I use Calendars to represent operational schedules. For example, a multi-day event has one calendar for each operational day.
Each calendar is associated with additional information outside Traccar, such as the route that will be used on that day.
What I'm trying to determine is the best way to associate these schedules with a Group of devices.
At the moment I can think of several approaches:
I'm not asking for a new Traccar feature. I'm interested in understanding what the recommended approach is when an external application needs to know which operational schedule belongs to a particular group.
How have others solved this kind of integration?
I'm especially interested in solutions that stay as close as possible to the existing Traccar data model and API.
Any suggestions or best practices would be appreciated.