Use GeoLens from ArcGIS Pro

ArcGIS Pro reads GeoLens through its built-in OGC API, XYZ tile and STAC support. Nothing needs installing. This page was tested with ArcGIS Pro 3.7 and GeoLens 1.27.1.

Public datasets work over OGC API Features, XYZ tiles and STAC. Private datasets work only as raster tiles. Replace https://geolens.example.com with your GeoLens instance’s URL in every example.

Public vector datasets: OGC API Features

1. In Pro, open Insert > Connections > Server > New OGC API Server.

2. Set the URL to your instance’s API root:

   https://geolens.example.com/api

3. In the Catalog pane, expand Servers, the new connection, then Features. Right-click a dataset and choose Add To Current Map.

Pro pages through every feature, so a large dataset takes a few requests to finish drawing. Raster datasets do not appear under Features. Points uploaded from a file show as Multipoint, because GeoLens stores uploaded geometries as multi-part types.

Private vector datasets

Pro cannot add a private vector dataset yet. It sends a custom request parameter while browsing the catalog, so the private collection is listed, but it does not send the parameter when it adds the layer. The add fails with “Failed to add data”.

Use QGIS for private vector data. It sends an X-Api-Key header on every request.

Rasters as XYZ tile layers

1. On the dataset page, open Connect and choose Copy XYZ Tile URL. See Tile endpoints.

2. Replace {z}/{x}/{y} with {level}/{col}/{row}. The copied URL ends in ?api_key={your_key}: for a private raster, replace {your_key} with a read-only key; for a public one, delete the whole ?api_key={your_key}.

   https://geolens.example.com/raster-tiles/<dataset-id>/tiles/{level}/{col}/{row}.png?api_key=<read-only key>

3. In Pro, on the Map tab, choose Add Data From Path, paste the URL and leave Service type on Automatic.

Pro adds a “Tiled service layer”. It renders in place and zooms normally. The key goes out with every tile request and survives closing and reopening the project. Keep the URL the Connect menu copies rather than the versioned template from the collection’s tiles link: a saved layer would keep that version forever. After a raster is replaced, the copied URL can show the old tiles of a public raster for up to an hour. See API Authentication for how to create a key.

Caution

The project file stores the full URL, including the key, in plain text. Use a read-only key scoped to what the project needs, and treat the .aprx file as a secret.

A signed URL from GET /api/tiles/token/{dataset_id}/ also works, with the same {level}/{col}/{row} substitution, until it expires within 16 minutes. After that Pro shows stale cached tiles and reports no error. Signed URLs suit a quick look, not a saved project.

Rasters as analysis-ready layers: STAC

A STAC connection gives you the cloud-optimized GeoTIFF itself as a raster layer, not a rendered tile pyramid.

1. Open Insert > Connections > STAC Connection > New STAC Connection.

2. Set the URL to:

   https://geolens.example.com/api/stac

3. In the Catalog pane, expand STACs and double-click the connection to open Explore STAC. Select the collection, choose View Results, then use Add to Current Map on an item.

Pro reads the COG directly with HTTP range requests. Only public items work today. A custom X-Api-Key header lets the search list private items, but Pro fetches the item and its COG without the header, so adding a private item fails.

Vector tiles

Pro does not support GeoLens vector tiles. Pro needs a VectorTileServer or a style JSON, and GeoLens serves a bare {z}/{x}/{y}.pbf template. Use OGC API Features for vector data in Pro.