The provided documentation for Goldstar GPS systems focuses exclusively on the technical functionality and administrative procedures for managing GeoZones within a fleet tracking platform. GeoZones are defined as user-created geographic boundaries that are automatically applied to all vehicles within a specific account. These boundaries are instrumental for monitoring vehicle movement relative to predefined areas, such as impound lots, service territories, or restricted zones. The system is designed to generate alerts when a device enters or exits these boundaries, though it is important to note that these alerts are not real-time. They are triggered only after the device sends another alert, such as an Auto Report, from within the boundary. The documentation outlines a series of administrative actions for creating, editing, deleting, and mapping GeoZones, providing a structured workflow for account administrators. The information is presented in a procedural, instructional format, typical of user manuals or help guides for software platforms.
Understanding GeoZones in Fleet Tracking Systems
GeoZones serve as a fundamental tool for operational oversight in vehicle fleet management. According to the provided materials, these are "user-created geographic boundaries that are automatically applied to all vehicles in the account." This implies a centralized management system where a single GeoZone configuration affects an entire fleet, streamlining the process for administrators. The primary purpose of these boundaries is to monitor and generate alerts based on vehicle location relative to these zones. For instance, a GeoZone can be established around an impound lot. The documentation specifies that "any device that sends an Auto Report from inside the boundary will also trigger a GeoZone Enter alert." This mechanism allows fleet managers to be notified when a vehicle enters a specific area, which can be crucial for security, logistics, and compliance.
It is critical to understand the system's alert latency. The documentation explicitly states, "GeoZone enter/exit alerts are not real time. Devices must send other alerts before a GeoZone boundary alert is sent." This means the system does not continuously poll for location changes. Instead, it relies on the device's scheduled or event-triggered transmissions (like Auto Reports) to evaluate its position against the GeoZone boundaries. Consequently, the notification of entry or exit is dependent on the device's reporting schedule and the triggering of another alert type. This design balances system load with utility, but users must be aware of the inherent delay, which could be a factor in time-sensitive applications.
Administrative Procedures for GeoZone Management
The Goldstar GPS platform offers a suite of administrative functions to manage GeoZones, accessible through a web-based interface. The process begins with the creation of a GeoZone, followed by options for modification, deletion, and visualization.
Creating a Geozone
The creation process is initiated by selecting an "Add" option, which opens a "Create Geozone" window. The administrator must follow a specific sequence of steps: 1. Name the Geozone: Assign a unique and descriptive name for easy identification. 2. Set Location: Define the center point of the Geozone by setting either an address or GPS coordinates. A button is available to automatically populate the corresponding set of fields (address to GPS or vice versa) once one is entered. 3. Define Size and Shape: Specify the radius of the Geozone in miles. The system also allows for the selection of a shape, though the specific shapes available are not detailed in the provided text. 4. Refine Boundaries (Optional): For greater precision, the administrator can use interactive markers on a map to adjust the boundaries of the Geozone visually. 5. Save: Finalize the creation by clicking the "Save" button.
Editing and Deleting Existing Geozones
To modify an existing Geozone, the administrator clicks the "Edit" (pencil) icon next to the desired zone in the list. This action opens an "Edit Geozone" window where all parameters—the name, address/GPS, radius, and shape—can be altered. The same optional boundary adjustment via map markers is available during editing. Changes are saved by clicking "Save."
Deleting a Geozone is a straightforward but irreversible action. The administrator clicks the "Delete" (trash can) icon next to the target Geozone. This opens a confirmation window ("Delete Geozone"), and clicking "Delete" within this window permanently removes the Geozone from the system. There is no mention of an undo function or recovery process.
Visualizing Geozones on a Map
For a comprehensive overview, the platform provides a "Map All" button located in the upper right of the interface. Activating this button updates the map display at the bottom of the page to show all GeoZones associated with the account simultaneously. This feature is useful for assessing the spatial relationship between different zones and for planning new boundary placements.
Importing Geozones in Bulk
For accounts requiring the setup of numerous GeoZones, a bulk import function is available. The administrator clicks the "Import" button, which opens an "Import Geozones" window. The process requires a CSV (Comma-Separated Values) file that conforms to specified guidelines. After selecting the appropriate file, clicking "Import" adds all the geozones from the file to the account. The provided text does not specify the exact format or required fields for the CSV file, indicating that users must refer to the platform's guidelines for this information.
Technical Considerations and System Limitations
Several technical aspects of the GeoZone functionality are important for users to consider. The system's non-real-time alert generation is a key design feature, as previously noted. This means that for a GeoZone alert to be triggered, the device must first generate another type of alert from within the zone. The "Auto Report" is given as an example of such a triggering alert.
The documentation also mentions that "GeoZone alerts cost 0 TRAK units," which suggests a proprietary point-based or credit system (TRAK units) for other types of alerts or services within the platform. This indicates that GeoZone alerts are offered at no additional cost, which could be a significant factor for cost-conscious fleet operations.
Another point to consider is the scope of application. The documentation states that GeoZones are "automatically applied to all vehicles in the account." This universal application simplifies management but may not suit situations where certain vehicles need to be excluded from specific zones. The provided material does not mention any capability for assigning GeoZones to individual vehicles or subsets of vehicles, implying a one-size-fits-all approach for the entire account.
The lack of detail on specific shapes (e.g., circles, polygons), the exact CSV import format, and the potential for customizing alert types (e.g., entry-only, exit-only, or both) means that users would need to consult additional, more detailed system documentation or contact support for complete operational understanding. The information provided is sufficient for basic administrative tasks but lacks the depth required for advanced configuration.
Conclusion
The Goldstar GPS system provides a structured and user-friendly interface for managing GeoZones, which are essential tools for monitoring vehicle movement within predefined geographic areas. The core functionality allows for the creation, editing, deletion, and visualization of these boundaries, with an additional option for bulk import to streamline setup for large fleets. A critical operational characteristic is the non-real-time nature of alerts, which are dependent on the device sending other alerts from within the zone. While the system offers GeoZone alerts at no cost (0 TRAK units) and applies them universally to all vehicles in an account, the provided documentation is limited in scope. It does not address advanced features such as custom shapes, vehicle-specific assignments, or detailed alert configurations. For comprehensive system utilization, users would likely need to reference supplementary guides or contact technical support to fill these information gaps.