Aller au contenu
getgeolens.com

Use GeoLens from ArcGIS Pro

Ce contenu n’est pas encore disponible dans votre langue.

ArcGIS Pro reads GeoLens through its built-in OGC API, XYZ tile, STAC and 3D Tiles support. Nothing needs installing. The public-data steps were last tested on 2026-11-11 with ArcGIS Pro 3.7 and GeoLens 1.31.0.

Public datasets work over OGC API Features, XYZ tiles, STAC and 3D Tiles. From GeoLens 1.28.0, private vector datasets work over OGC API Features with an API key as the saved login, and private rasters work as tiles. Replace https://geolens.example.com with your GeoLens instance’s URL in every example.

  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

    The dialog opens on Server Authentication with empty fields. Leave them empty for public data.

  3. In the Catalog pane, expand Servers, the new connection, then Features. Each dataset is listed as its title followed by its id in parentheses. Right-click one and choose Add To Current Map.

  4. Pro shows an Add OGC API Layer(s) dialog. Choose OK to load every feature, or tick Use Spatial Extent first to load only the features in the current view.

Pro downloads the layer when you add it. It asks for pages of limit=3000 and follows the server’s next links, so a large dataset takes a few requests to finish drawing. With Use Spatial Extent it sends the view as a bbox and GeoLens returns only what falls inside. Raster datasets do not appear under Features.

Pro then filters, queries and draws its own copy. A definition query, the attribute table, zooming and panning send nothing to GeoLens, and changes made on the server later don’t appear until you add the layer again.

Points arrive as Multipoint, because GeoLens stores uploaded geometries as multi-part types.

Export Features can write polygons with a negative Shape_Area. GeoLens sends each polygon’s rings in the order they were stored, and Pro keeps the order it receives. Data that came from ArcGIS, a shapefile or a file geodatabase usually has clockwise exterior rings and exports with a positive area. Data loaded from GeoJSON usually has counter-clockwise exterior rings, as the GeoJSON specification (RFC 7946) asks, and exports with a negative area. Run Repair Geometry on the exported feature class: it fixes the sign and keeps every feature.

From GeoLens 1.28.0, Pro opens private datasets through its Server Authentication login, with an API key as the password.

  1. Open Insert > Connections > Server > New OGC API Server.

  2. Set the URL to the desktop entry point:

    https://geolens.example.com/api/desktop
  3. When Pro asks for a login, enter any username and an API key as the password, and save the login. A read-only key is enough.

  4. Add datasets from Features as for a public connection.

/api/desktop serves the OGC API itself and keeps every link under /api/desktop, and it answers 401 with a Basic challenge to any request without a working key. The key authenticates GET, HEAD and OPTIONS requests only, so the connection can read but never write. GeoLens never accepts an account password this way. See HTTP Basic form.

If Pro refuses a key, restart Pro before you try again. In Pro 3.7, after one refused login Pro stops contacting that server for the rest of the session, so even the right key gets the same “unable to connect” message.

Before 1.32.0 the entry point redirected to /api/ after the login, so Pro saved each private layer under /api and showed it as broken when the project was reopened. A project saved then keeps those addresses: add its private layers again through /api/desktop once the instance runs 1.32.0.

Earlier releases can’t add a private vector dataset to Pro: the add fails with “Failed to add data”. Use QGIS there, which sends an X-Api-Key header on every request.

  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.

Pro adds the layer even when the key is missing from the URL; the tiles then answer 404 and nothing draws. To pass the layer to someone else, save it with Sharing > Save As Layer File. The .lyrx file is JSON and holds the whole URL, key included, so share it as carefully as the key.

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.

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. Pro lists the collections by id, not by title.

  4. Tick a collection and, with the icon at the right of its row, pick the data asset type, which is the COG.

  5. Choose View Results, then use Add to Current Map on an item.

Pro reads the COG directly with HTTP range requests and adds it inside a group layer named “STACResultsGroupLayer”. A large COG on remote storage can take about a minute to appear. Items cataloged from a remote COG, and mosaics, show a blank card in the results because they have no thumbnail asset.

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.

  1. On the dataset page, open the Access tab and copy the tileset URL. See Opening a dataset in a client.

    https://geolens.example.com/api/datasets/<dataset-id>/tiles3d/tileset.json
  2. In Pro, open or insert a local scene. On the Map tab, choose Add Data From Path and paste the URL.

  3. Pro sets Service type to 3D Tiles Service. Keep the suggested Layer Type, or choose 3D Object for buildings, and choose Add.

Pro adds the layer and zooms to it. If the scene is empty at that first view, zoom in. Pro requests a tile’s children only once the tile’s geometric error is large enough on screen, so a tileset whose root has no content and a small geometric error draws nothing from far away. Only a public dataset was tested.

Pro does not support GeoLens vector tiles. Pro needs a VectorTileServer, and GeoLens serves a bare {z}/{x}/{y}.pbf template and a MapLibre style.json per map. A plain template does not work: Pro requests the URL literally, with {z}/{x}/{y} unreplaced, and adds an empty “Tiled service layer” without an error. It refuses the style.json URL with “Invalid Path” while Service type is Automatic. With Service type set to Vector Tile Service and ?sprite=url on the URL, Pro adds a “Vector Tile Layer” and reads the style and its sprite, then asks for each tile one zoom level off, so the layer stays blank. Use OGC API Features for vector data in Pro.