QGIS and ArcGIS Integration with Datgel View

Datgel View for QGIS and ArcGIS users. Connect your gINT borehole data to QGIS and ArcGIS Pro through the modern OGC API — tiles for fast pan and zoom, and live vector features for analysis. No plugins, no data exports.

OGC API endpoints

Every Datgel View deployment exposes its authorised projects through the modern OGC API standard. Two complementary endpoints — raster tiles and vector features — covering both the "show me a fast basemap of every borehole" workflow and the "give me the actual points so I can run analysis" workflow.

Tiles  : https://your-deployment/api/ogc/tiles/WebMercatorQuad/{z}/{y}/{x}?apikey=YOUR_KEY
Features: https://your-deployment/api/ogc/features/collections/project_{GintProjectId}/items?apikey=YOUR_KEY

Tiles render as 256×256 PNGs in WebMercatorQuad (EPSG:3857). Features return GeoJSON in WGS84 (EPSG:4326) with full attributes (PointID, Type, Elevation, Project) per RFC 7946.

What you get in your desktop GIS

  • Pre-rendered tiles with the same PointType symbols as the web map — fast pan and zoom even at country scale
  • Live vector features with click-through attributes: PointID, type, elevation, project
  • One feature collection per gINT project — toggle on the projects relevant to your current job
  • BBOX, paging, and limit support on the Features endpoint for filtered queries
  • Per-project transparency, ordering, and styling alongside your other layers
  • Per-user, scoped API keys with optional expiry — revoke instantly, no shared credentials

Connecting QGIS 3.30+

For tiles (fast basemap):

  1. Get an API key. Sign in to your Datgel View deployment and visit /account/api-keys. Choose the tiles scope. The plaintext is shown once at creation; copy it immediately.
  2. Add an XYZ Tiles connection. Browser panel → right-click XYZ Tiles → New Connection.
  3. Paste the URL: https://your-deployment/api/ogc/tiles/WebMercatorQuad/{z}/{y}/{x}?apikey=YOUR_KEY
  4. Drag the connection onto your map.

For features (analysis):

  1. Get an API key with the features scope (or use a single key with both scopes).
  2. Add an OGC API - Features connection. Browser panel → right-click OGC API - Features → New Connection.
  3. Paste the URL: https://your-deployment/api/ogc/features?apikey=YOUR_KEY
  4. Connect — you'll see one collection per gINT project you have access to. Drag the ones you want onto your map.

Connecting ArcGIS Pro 3.2+

For tiles:

  1. Get an API key with the tiles scope.
  2. In ArcGIS Pro: Insert → Connections → New XYZ Tile Connection or add via the Catalog pane as a tile layer.
  3. Paste the URL with the ?apikey=... query parameter.

For features:

  1. Get an API key with the features scope.
  2. In ArcGIS Pro: Insert → Connections → New OGC API Server Connection.
  3. Paste the URLhttps://your-deployment/api/ogc/features?apikey=YOUR_KEY and add the project collections to your map.

Other clients

The OGC API standard is supported by GDAL/OGR, FME, MapInfo Pro 2023+, Global Mapper, and any other modern GIS client. The same per-user API keys work everywhere.

Where the keys come from

Every signed-in user can mint their own API keys at /account/api-keys — no admin involvement needed. OrgAdmins can manage keys for any user in their organisation at /admin/apikeys. Keys are scoped (tiles only, features only, or both), can be set to expire, and can be revoked instantly.