Query drillhole collar, assay, and geotechnical data from an acQuire GIM Suite database
domain: acQuire GIM Suite (geoscientific data management) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the target GIM Suite deployment exposes API/ODBC connectivity for the desktop, web, or mobile interface being used.
Connect via ODBC (or the documented API) using credentials scoped to the specific project's drillhole database.
Query drillhole collar data, downhole geophysics, assay results, and geotechnical/hydrogeological monitoring records as separate but linked record types within the schema.
Respect the platform's built-in validation rules at the point of capture — a failed insert usually means a validation-rule conflict, not a connectivity issue.
For downstream 3D modeling, use one of acQuire's documented technology-partner interoperability paths (e.g., importing drillholes into Leapfrog/Seequent tools via their acQuire import feature) instead of hand-building a custom export.
Known gotchas
GIM Suite's schema is deep and project-specific (collar/survey/assay/geotech tables), so a generic "get all drillhole data" query rarely exists — plan queries around the specific record type needed.
Validation rules are configured per deployment; behavior that appears to be an API bug in one acQuire instance may simply be a stricter (or looser) validation configuration in another.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?