Supported Data Sources (Details)

The tables and lists show which data sources are supported by which functions of Cadenza Workbooks. The generally supported versions of the data sources can be found on the overview page. You can also find an overview of the mapping of database data types to Cadenza data types here.

Information on mapping data source-specific data types to Cadenza data types

As a rule, further requirements must be met in order to use the functions, for example configuration via plug-ins or requirements for the data sources themselves.

Databases for Cadenza Infrastructure Functions

opt. Oracle PostgreSQL/EDB MSSQL

Cadenza infrastructure (Metadaten)

Access management

✅

✅

–

1)

Repositories

✅

✅

–

1)

✅

Performance logging

✅

–

–

✅

Audit logging

✅

✅

–

1)

Storage of user settings

✅

✅

–

1)

Job Scheduling

✅

✅

–

1)

Data management (spatial and non-spatial data)

Cadenza Data Store (CDS)
(for data managed by Cadenza, e.g. imported data)

✅

✅

✅

1)

1) also H2 for test purposes (we expressly advise against using it in production operation)

Data Sources for Analyzing Data

Depending on the type of data source, there are technical restrictions on objecttypes, views and filters. Cadenza offers the option of downloading the required data by objecttype into a Cadenza Data Store so that the full Cadenza functionality can be used.

Relational Databases

  • Oracle, Oracle Spatial and Graph

  • PostgreSQL/EDB, PostGIS

  • Microsoft SQL Server (MSSQL) with the following limitations:

    • Objecttypes: no data enrichment

  • SAP HANA (Currently in beta)

  • H2 (for test purposes; we expressly advise against use in productive operation)

Search and Analysis Engines

  • Elasticsearch with following limitations

    • Only individual indices are supported.

    • Data types: no binary, unsigned-long or nested data types and no dynamic attributes (e.g. _id or _score)

    • Data sources: no use as CDS

    • Objecttypes: no geometries, hierarchies or function attributes; No “Count (distinct)" aggregation, no associations or static data restrictions; no combined objecttypes; no data acquisition; no data import

    • Views: no advanced OLAP functionalities (e.g. subtotals, Top-N analysis); no JasperReports views

    • Filters: Supported are table, value interval, date, date interval and text pattern filters (text pattern filter: full Lucene functionality)

    • Location Finder: is not supported.

    • Test connection in Management Center: For authorized users to be able to test the connection to the Elasticsearch engine from the Management Center, users must have the monitor cluster permission in ELK (Elasticsearch/Kibana). If the permission is not granted, Cadenza can still connect (given other read permissions), only the Cadenza function Test connection will not work as expected.

  • OpenSearch

    OpenSearch has the same limitations as Elasticsearch.

Geodata Services

  • WFS with the following limitations:

    • Data sources: no use as CDS

    • Objecttypes: no function attributes or associations; no combined objecttypes; no variables for user-based restrictions; no data acquisition

    • Views: no Top-N analyses, intermediate values or total values (columns and rows); no display of dimension values without data; no JasperReports views

    • Filters: Supported are table, value interval, date, date interval and text pattern filters (text pattern filter: case sensitive), as well as spatial filters.

    • Filter: Attributes are not available in query filters.

    • Location Finder: Only text attributes (String) can be defined as searched attributes for the search source.

  • Feature service of ArcGIS Server (REST interface) with the following limitations:

    • Data sources: no use as CDS

    • Objecttypes: no function attributes, date hierarchies or associations; no combined objecttypes; no variables for user-based restrictions; no data acquisition

    • Views: no Top-N analyses or intermediate values; no display of dimension values without data; no JasperReports views

    • Filters: Attributes are not available in query filters.

    • Location Finder: Only text attributes (String) can be defined as searched attributes for the search source.

Files (via Import into the Cadenza Data Store):

  • Excel with coordinate columns or addresses or without spatial reference

  • CSV with coordinate columns or addresses or without spatial reference

  • Shapefiles

  • KML according to the OGC KML schema 2.2 (namespace "http://www.opengis.net/kml/2.2"). Cadenza also attempts to import KML files that do not correspond to this schema. However, the functionality is not guaranteed.

    • Cadenza interprets the KML feature <Placemark>.

    • KML files with extended schemas can be imported if the schema extension is defined in the file. Supported KML data types are string, int, float, double, bool and datetime.

    • KML files with elements containing HTML tags can be imported. For security reasons, however, the HTML is not interpreted. So if attribute content is displayed via the object information, for example, any HTML content is visible in plain text.

  • GeoPackage

  • GPX and CSV with movement profile information

  • ZIP and KMZ archive files

  • GeoJSON data as a layer (via Cadenza API only)

    • Supports all geometry types, but not properties.

    • The data of the added layers is only temporarily available within the geometry creation/editing dialog. Cadenza does not save added layers.

Data Sources for Visualization in a Map View Only

  • WMS, WMTS

    • Cadenza supports the WMS/WMTS standard and assumes that WMS/WMTS servers are also configured accordingly.

    • So far, the “Basic Authentication Method” of WM(T)S servers has been implemented. This excludes WM(T)S servers that use preemptive authentication.

    • Users can add additional request parameters to the server URL as key-value pairs (KVP) (e.g. “version=1.1.1”), which are used to retrieve the capabilities document.

    • Layers support the following features:

      • authentification option

      • print name (<Title> tag or, if not available, <NAME> tag)

      • optional: description (<Abstract> tag)

      • feature information (via GetFeatureInfo). Supported formats are JSON, GeoJSON, GML. In order for feature information to be displayed for a WMS/WMTS layer, the corresponding layer must be “queryable” (attribute “queryable” in the <Layer> tag of the GetCapabilities response). Ideally, the server should support GML. Then the geometry of the relevant object can also be determined and displayed from the query.

      • opacity

      • graphic legend information as an image

    • Limitations:

      • The display of a WMS layer is determined by the geodata service. If the map service provides several styles for the display, the first style (default) is used. A different style cannot be selected.

      • The format PNG for transferring the map image is not customizable.

      • The query of additional server-specific parameters is not supported.

      • GetFeatureInfo requests are not recorded in the audit logging.

  • Image Service and Map Service of ArcGIS Server (REST interface)

    • The server URL must contain the path element /arcgis/services

    • Layers support the following features:

      • print name

      • description

      • feature information (in parts)

      • opacity

    • Limitations:

      • no authentification option

      • no graphic legend information as an image

  • Vector Tile Service

    • The rendering of the vector tiles is implemented with OpenLayers. This may result in differences compared to other rendering libraries (Mapbox GL JS / MapLibre GL JS).

    • The URL of the Vector Tile Service must refer to a style document in JSON format accessible via URL in accordance with the Mapbox style specification (https://docs.mapbox.com/style-spec/reference/). The focus is currently on the use of “Mapbox/MapLibre Vector Tiles (MVT)” as a background map layer.

    • Layers support the following features:

      • print name

      • description

      • opacity

    • Limitations:

      • no authentification option

      • no feature information

      • no graphic legend information as an image