Compatibility
Talus is the server of GIS data: vectors, rasters, and tables. The tools your staff already use connect to it through standard doors, and this page outlines some common GIS apps, whether a limit exists, and why.
Checked against Talus 1.0 on 15 November 2026. The desktop tools were last tested on 17 September 2026, against the versions named for each. Tools change; tell us if a claim here has gone stale.
The model
Every read and write goes through the API. Talus uses standards desktop tools already speak: OGC API Features, the Esri FeatureServer dialect, WMTS for imagery, WCS for raster values, vector tiles for the browser, and DCAT-US for open-data harvesters. A user signs in once with an access token that is theirs to revoke; the same sharing rules, audit trail, and conflict detection apply whether an edit arrives from a browser, ArcGIS Pro, QGIS, or a phone. There is deliberately no direct database connection.
Esri
ArcGIS Pro
Read and edit, today. Talus hands out a connection file; import it once per computer and every layer you can see in Talus is in Pro's Catalog pane, and layers shared to you later appear automatically. Editing goes through the Esri FeatureServer door with the same behaviour Pro expects from an ArcGIS Server: paste a layer's address, edit, save. Feature attachments (photos and documents) work natively in Pro with no setup. Imagery is served as WMTS. Bulk loads use Pro's own Append tool.
Limits, plainly. Pro will not render Talus WCS raster values, so imagery is viewed through WMTS. Pro's OGC API Features path is read-only. Verified against Pro 3.7.
ArcGIS Field Maps and Survey123
Not compatible, and nothing Talus can do about it. Both apps sign in to an ArcGIS Online or ArcGIS Enterprise portal and only open the web maps and surveys that live there; they cannot be pointed at any other server. What transfers is the work, not the app: the forms, coded domains, required fields, and offline areas you built there map onto Talus Field, or onto QField. An external GNSS receiver works with Talus Field when it becomes the phone's location, or on Android when Talus Field reads it over Bluetooth; on an iPhone, a receiver that feeds only native apps does not reach it. Talus records capture-time provenance fields (fix quality, accuracy, receiver) on the feature when the receiver supplies them.
Moving from ArcGIS Online or ArcGIS Enterprise
Export each hosted layer as GeoPackage or Shapefile and import it; attachments come in through Pro's Append tool or the attachment chute. Services you cannot move yet stay referenced live from the catalog. Dashboards, story maps, and field forms are rebuilt in the Talus+ modules rather than migrated, because the formats are Esri's. The FAQ covers what Talus deliberately does not replace.
QGIS and QField
QGIS
Read and edit, today. Talus hands out a connection file; import it once per computer and QGIS gets an OGC API Features connection that browses the whole catalog, so adding a layer is expand-and-add, and layers shared to you later appear automatically. Editing goes through the Esri FeatureServer door, one layer's service link at a time; the attachment widget reads and writes photos on features; imagery arrives as WMTS and raster values as WCS. A field project authored in QGIS can be uploaded to the portal for distribution. Verified against QGIS 3.44.
QField
Works today. A publisher generates a field project from a web map in one click, or uploads one authored in QGIS. The project carries a crew credential that can be revoked from the portal, and it is distributed as a link the phone opens directly. Collection and photos round-trip into the same layers and attachments everything else uses. The recipe is in docs/connect-desktop.md. QField is the open, proven baseline; it is not a placeholder for Talus Field.
Stand-alone products
Google Earth desktop
A migration path for the KMZ. Google Earth desktop's discontinuation leaves years of KML and KMZ with nowhere to live. Talus imports both: folders become a column on the layer so your organization survives the move, attributes come in typed when the file declares a schema, and descriptions are kept as text. Overlays and network links are reported in the import summary as not imported, and a linked file is never fetched. Talus is a 2D map with attributes; for the globe itself, point people at Google Earth on the web, or at GeoLibre (below).
GeoLibre
Read-only, today, with nothing to configure. GeoLibre is an open-source GIS that runs in a browser tab, on the desktop, and on a phone. It hosts no data and has no accounts, and its own documentation recommends pairing it with a server that provides those. In the GeoLibre desktop app, choose Add Data, then OGC API Features, and paste the portal's /api/v1/ogc landing page: every publicly shared layer appears and pages through in full. Or choose Add Data, then ArcGIS layer, and paste a public layer's FeatureServer address. Use the desktop app rather than the hosted web app; Talus keeps its doors closed to third-party browser origins on purpose. A private layer opens from a file, downloaded as a GeoPackage first.
Editing from GeoLibre does not work, and the reason is authentication, not capability. GeoLibre writes edits with the same Esri applyEdits call ArcGIS Pro uses on Talus, but its ArcGIS client can only sign in with a token placed in the URL, and Talus accepts tokens only in a request header, by decision: QGIS and Pro never needed a URL token, and a token in a URL leaks into browser history and proxy logs. On an editing-enabled public layer GeoLibre offers the save, Talus refuses it, and nothing is written. Where GeoLibre is the better tool, use it: analysis, print layouts, a 3D globe, viewing on a phone. An organization that runs Talus gets a capable open-source client for nothing, today, for reading.
Standards, data, and the rest of your stack
Standards, scripts, and open data
Served by Talus: OGC API Features (plain JSON, paged), WMTS, WCS, the Esri FeatureServer dialect, vector tiles, and DCAT-US metadata for open-data harvesters, all documented in docs/api-guide.md. Python, R, GDAL and OGR, or anything that speaks HTTP connects with a personal access token, and unattended jobs use scoped service accounts. Consumed by Talus: a live ArcGIS feature or image service, a GeoJSON feed, or an XYZ tile layer can be referenced from the catalog without copying it, so a state parcel service or a regional aerial stays where it is.
Data in and out
In: zipped Shapefile, GeoPackage, GeoJSON, CSV with coordinates, GeoParquet, KML and KMZ, and GeoTIFF, JPEG 2000, and ERDAS IMG rasters, which convert to cloud-optimized GeoTIFF. Out: CSV, GeoJSON, Shapefile, and GeoPackage with reprojection, plus raster exports. Your data is yours to take elsewhere, in the format the next tool reads.
Limit: File Geodatabase is not accepted. Export it from Pro as GeoPackage or Shapefile first, and every field comes across; picklists are bound to a domain in Talus, and attachments load with Pro's Append tool.
From a database you already run: a publisher can keep a read-only copy of a table or view from SQL Server, PostgreSQL, MySQL, or MariaDB in Talus, refreshed nightly or on an interval, with points built from two coordinate columns, or as a table whose addresses you geocode afterwards (that point layer is a copy, not refreshed with the pull). Talus connects with a read-only login your DBA issues and never writes to the source; on PostgreSQL, MySQL, and MariaDB the session is read-only as well. There is no WHERE clause and no free-text SQL on purpose: if you want a subset, your DBA's view is the filter. A refresh writes only the rows that changed, a failed refresh keeps the last good copy and says why, and the copy stays locked against editing in Talus while its source is attached. SDE point feature classes come across through a view that exposes their coordinates; Oracle is listed but not yet available. The full page: How it works: your databases.
Your identity provider
Staff sign in through the organization's existing provider, any SAML or OIDC identity provider, on one branded sign-in page. Entra ID is the worked example in the runbook; Okta, Google Workspace, ADFS, and Ping follow the same steps. Local accounts remain for a crew without a directory entry. Multi-factor is built in; the runbook shows how to require it, administrators first.
Your geocoder
A new install ships with the public OpenStreetMap geocoder switched on, which an administrator can remove. Three more kinds are configured by an administrator: a self-hosted Nominatim; the Esri World Geocoder using a token you generated in your own ArcGIS organization, stored write-only and never echoed back; and an internal locator over your own address points, which costs nothing and stays air-gapped. Batch geocoding shows an estimate before spending anyone's credits.
Your backup target
Backups are written to the host or to any S3-compatible object store you name, with optional encryption to keys only you hold, so an existing Backblaze, Wasabi, MinIO, or AWS bucket works as the off-host copy. Restore is rehearsed by a drill script, not assumed, and the admin pages show when it last passed.
Asset management and work orders
Work-order and asset-management systems are integration points, not features. Talus records what is on the ground and what happened to it; the work-order system reads and writes through the API with a service account. Talus will not assign work, route crews, or manage tickets, and says so in its non-goals. The other direction is covered too: the work-order system's own tables can be kept in Talus as a read-only, nightly-refreshed copy, so crews see the asset and its open work on one map (Data in and out).
Not on this page, by design. Business-intelligence tools, CAD, 3D scene viewers, routing engines, and utility-network products. Talus exports data those tools read; it does not try to be them. The reasoning is on Why Talus? and in the FAQ.