Eternet Portal Documentation
Geofence Management
Central catalog
The Geofences page presents the shared geofence catalog alongside a map. Operators can search and inspect areas, show or zoom to a shape, and create, edit, or delete a shared definition through the portal’s geofence integration.
Vehicle assignment
Vehicle detail uses the Geofence tab to assign or unassign existing shared areas. Definitions are managed centrally; a vehicle assignment is not a second geofence copy.
System of record
Geofence definitions and enforcement are synchronized with Traccar through Eternet’s Vehicle Service/Core API integration. Traccar remains the system that evaluates geofence behavior. Confirm successful API responses and compare the Traccar catalog when verifying synchronization.
Safety distinction
Removing an assignment from a vehicle is distinct from deleting a shared geofence. Deletion affects the shared definition and should be confirmed explicitly.
Defining and reviewing a geographic area
Geofence management provides a central catalog rather than a separate collection for each vehicle. An operator can search existing definitions, select one to show its boundary on the map, zoom to its extent, and open the editor to create or change a shape. The editor supports drawing circles, lines, and polygons. A circle requires a center and radius; a line requires at least two points; a polygon requires at least three boundary points. Geometry is serialized and submitted through the portal’s API so the shared definition is stored by Traccar through the Eternet integration. The map supports visual inspection, but the saved geometry returned by the service remains the authoritative record.
Shared ownership has practical consequences. Editing an existing area changes the definition seen by every vehicle assigned to it. This is appropriate when an organization’s boundary itself has changed, but it is not the right operation for a vehicle-specific exception. Vehicle detail offers a separate assignment interface so an operator can link or unlink existing geofences without copying their geometry. Deleting a geofence is a more consequential action: it removes the shared definition and can affect all associations, so the portal uses a confirmation step and should report service errors clearly.
Synchronization and operational validation
The intended system of record for geofence enforcement is Traccar. The portal sends create, update, delete, and assignment operations through Eternet’s Vehicle Service/Core API integration, while Traccar evaluates positions against the configured areas. A portal response should be checked against the Traccar catalog when verifying synchronization. A local success notice alone is not enough if the upstream operation is asynchronous or can fail after an intermediary response. Likewise, a matching list confirms definitions are aligned but does not prove the position feed is current or that entry/exit notifications are configured.
To validate a new area, save one shape, refresh the portal list, confirm the same identifier and geometry in Traccar, and inspect a vehicle’s assignment list. Then use an authorized test vehicle position or test environment to verify that Traccar evaluates entry/exit behavior. Do not move a real vehicle into a restricted boundary just for a demonstration. Coordinate systems, point order, radius units, and malformed geometry are common sources of errors, so review the geometry and the backend response before relying on a boundary for safety or compliance.
Customer value and limits
Central management makes it easier for fleet teams to standardize locations such as depots, service zones, customer sites, and restricted areas. Reusing one definition avoids drift between vehicle records and lets administrators manage changes in one place. The portal is the operator interface and synchronization path; Traccar performs geofence processing. Position freshness, notification rules, and retention depend on the connected tracking system. During a customer demonstration, show the map representation and explain the difference between modifying a shared boundary and assigning that boundary to a vehicle. Include the Traccar verification step so the customer sees that the data is synchronized, not merely drawn in the browser.