Your ground data, in the tools you already use
Two releases that stop GIMLabs being somewhere you export from.
Blog · 2 September 2026
Every ground investigation platform eventually gets the same request, phrased a dozen different ways. Someone wants the data somewhere else. In a GIS project alongside the utilities and the constraints. In a dashboard the client already looks at. In a warehouse feeding a model. In a spreadsheet, because that is where the calculation lives.
The usual answer is an export. Somebody opens the platform, picks a project, chooses a format, downloads a file, and emails it on. It works, and it is wrong in a specific way: the moment that file lands, it stops being your data and starts being a copy of your data from a Tuesday. The next time anyone needs it, they do the whole thing again, and now there are two files that disagree.
We have shipped two things that remove the export from the middle.
The first is an API. A plain HTTP endpoint that returns JSON, at api.gimlabs.io/v1. Projects, locations with their coordinates and depths, and any AGS table, for a whole project or a single hole. Anything that can make a web request can read it: a Python script, a BI tool, a scheduled sync. Pass a timestamp and you get only the rows that have changed since, so keeping a warehouse current is a small nightly job rather than a full re-pull.
It is read-only, and that is a design decision rather than a stage we have not got to yet. An API key cannot create, change or delete anything. The worst a leaked key can do is read, and it can be restricted to named projects, so even that is bounded.
The second is a QGIS plugin. For a lot of engineers the map is where the thinking happens, and until now getting boreholes onto it meant exporting a CSV and joining it up by hand every time something changed. GIMLabs for QGIS loads your locations, site boundaries and location groups straight onto the canvas as styled layers, with the same symbology the GIMLabs map uses. The marker artwork you have set up comes through as marker artwork, not as a stand-in circle.
It caches what it has loaded, so a laptop that has seen a project once can open it again on a site with no reception, and it tells you how old the cached copy is rather than quietly showing you last week.
Both of these are about the same thing. Your ground data should not live in one place and be copied everywhere else. It should be readable, from wherever you happen to be working, as it is right now.
Available on Pro. Both are documented in detail in the platform, under Docs.