Idea:
ArcGIS Data Pipelines is a powerful tool for preparing and publishing data into ArcGIS Online, but its list of supported connectors is currently limited to Snowflake, BigQuery, Databricks (Beta), cloud storage (S3, Azure), and ArcGIS layers.
Many organizations use Denodo as a data virtualization and federation platform to unify data access across multiple heterogeneous systems (databases, APIs, cloud data warehouses, and legacy systems). By supporting Denodo as a native connector in ArcGIS Data Pipelines, ArcGIS users could tap into a single virtualized data layer rather than building separate integrations for each system.
Proposed Features:
Native connector to Denodo views/tables as inputs to Data Pipelines.
Support for both JDBC/ODBC and REST API access methods.
Secure authentication options (OAuth, SAML, key-based).
Ability to apply Data Pipelines transformations on top of Denodo-virtualized datasets and publish them directly as hosted feature layers.
Benefits:
Simplifies data integration by allowing ArcGIS to connect to a single virtualized source of truth.
Reduces ETL complexity, since Denodo can already handle schema mapping, joins, and governance.
Provides real-time access to enterprise data without duplicating datasets into intermediate storage.
Opens up powerful use cases for organizations in financial services, energy, government, and healthcare, where Denodo is widely adopted for secure, federated access.
Use Cases:
A government agency federates environmental, demographic, and infrastructure data in Denodo and wants to publish subsets directly into ArcGIS dashboards.
An energy company uses Denodo to unify sensor, IoT, and asset data from multiple systems, then serves it to ArcGIS without heavy data replication.
A nonprofit uses Denodo to govern sensitive datasets and still expose curated public layers through ArcGIS Hub.
Adding Denodo support would significantly expand the interoperability and enterprise readiness of ArcGIS Data Pipelines
