Geolocation of assets and tickets in GLPI

The NexTool Geolocation module captures the technician's GPS coordinates when registering followups and solutions in GLPI, automatically converting them to a readable address via reverse geocoding.

Where was the technician when they resolved the ticket? – The NexTool Geolocation module answers this question automatically, capturing GPS coordinates at the time of the followup or solution and displaying the physical address directly in the ticket timeline.

The problem

In field teams, knowing where the technician was when registering an occurrence is fundamental for audits, SLAs, and route planning. Today, the only way to record this in GLPI is by manually typing the address in the followup – a process susceptible to errors, omissions, and inconsistencies.

Additionally, managers who need to verify physical presence at external service calls have no way to validate the location without relying on the technician's word or external tracking systems, which rarely integrate with GLPI.

The result is a traceability gap that compromises both the quality of operational data and the credibility of service reports.

How Geolocation works

The module injects a "Get Location" button in the followup and solution forms of tickets. When clicked, the browser requests geolocation permission and captures latitude, longitude, and accuracy via the browser's native API.

Then, an automatic reverse geocoding converts coordinates to a readable address using Nominatim (OpenStreetMap) – a free service with no API key required. The complete process happens in the background, without interrupting the technician's flow.

After saving the followup or solution, a location visual badge is automatically displayed in the ticket timeline, containing:

  • Formatted address – city, neighborhood, and street converted by reverse geocoding.
  • Accuracy in meters – indicates the GPS capture error margin.
  • OpenStreetMap link – allows viewing the exact point on the map with one click.

Other module highlights:

  • Complete history per ticket – all registered locations remain linked to the ticket.
  • Formatted text insertion – the location can be automatically inserted in the followup body.
  • Integrated test page – allows validating capture, permissions, and geocoding directly in the module settings.
  • Multiple provider support – Nominatim implemented; Google Maps and Mapbox prepared for future activation.
Overview of the Geolocation module in GLPI with all settings and tabs
Complete Geolocation settings: map providers and display options

How to activate

  1. Install the NexTool plugin on GLPI.
  2. Go to Setup > NexTool > Modules.
  3. Find the Geolocation card and click Install, then Activate.
  4. Configure the geocoding and badge display options in Configure.
  5. Ensure the environment uses HTTPS – the browser requires HTTPS to grant geolocation permission.
Geolocation module configuration page in GLPI with geolocation options
Module configuration panel in GLPI

Who is it for

The module is especially valuable for field teams that perform external service calls, companies that need to audit physical presence at infrastructure tickets, and managers who want to enrich GLPI operational data with geographic context without relying on external systems.

Compatibility

  • GLPI: 10.x and 11.x
  • Plan: On demand (PAID)
  • Plugin: NexTool 3.x+

Next step

Geolocation is part of NexTool, a modular plugin for GLPI. Explore all modules or contact the team.


This content was produced with the assistance of artificial intelligence and reviewed by the Nextool Solutions team. Screenshots are from the real GLPI environment with the NexTool plugin.

Need help?