> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/connector-repositories/reporting-tool/cartovista/cartovista-lineage.md).

# CartoVista - Lineage

This document outlines the lineage coverage, configuration settings, metadata handling, supported scenarios, component behaviors, process flow, and known limitations for lineage extraction in CartoVista.

The CartoVista connector provides automated lineage extraction for spatial and mapping assets by tracing data flow from DataTables through Layers to Maps and Slides. It enables users to visualize how geographic data moves and transforms across multiple visualization layers. The connector supports both report-level and column-level lineage to improve data transparency and impact analysis.

### Lineage Configuration Requirements

Accurate lineage extraction depends on specific configuration settings. These settings must be defined correctly to ensure that supported data layers and lineage processing behaviors are interpreted properly. 

#### Configuration Requirements Table

<table><thead><tr><th width="199.33331298828125">Configuration</th><th>Text</th></tr></thead><tbody><tr><td>Supported Data Layers</td><td>Supported data layer types for lineage extraction must be defined in CrawlerOption.supportingDataLayers.</td></tr><tr><td>Connection Priority </td><td>Connection priority for lineage processing must be defined in CrawlerOption.connectionsPriorityForLineage. </td></tr><tr><td>Authentication </td><td>Requires valid API credentials for CartoVista access with Map Gallery User role or higher. </td></tr><tr><td>Access Requirements </td><td>Requires a valid CartoVista connection ID and domain access to store lineage. Database connections must be pre-crawled for DataTable and column matching. </td></tr><tr><td>Tenant Settings </td><td>Not applicable </td></tr><tr><td>Lineage Options </td><td>Semantic table creation and column-level lineage are enabled by default. </td></tr></tbody></table>

{% hint style="info" %}
Ensure associated database connections are crawled before lineage extraction to support DataTable and column matching.&#x20;
{% endhint %}

{% hint style="warning" %}
Incorrect configuration, insufficient permissions, or missing metadata may prevent the connector from identifying the correct lineage path or building complete lineage relationships.&#x20;
{% endhint %}

### Lineage Components

<table><thead><tr><th width="382">Component</th><th>Availability</th></tr></thead><tbody><tr><td>Maps</td><td>✅</td></tr><tr><td>Layers</td><td>✅</td></tr><tr><td>DataTables</td><td>✅</td></tr><tr><td>DataTable Columns</td><td>✅</td></tr><tr><td>Slides</td><td>✅</td></tr><tr><td>Semantic Tables</td><td>✅</td></tr><tr><td>Renamed Columns</td><td>✅</td></tr><tr><td>Temp Columns</td><td>✅</td></tr><tr><td>Semantic Columns</td><td>✅</td></tr><tr><td>WMS Layers</td><td>⚠️</td></tr><tr><td>WMTS Layers</td><td>⚠️</td></tr><tr><td>Grid Layers</td><td>❌</td></tr><tr><td>Calculated Fields / Formulas</td><td>⚠️</td></tr><tr><td>Derived Columns</td><td>⚠️</td></tr><tr><td>Geographic / Spatial Fields</td><td>⚠️ </td></tr><tr><td>Relationships</td><td>❌</td></tr><tr><td>Hierarchies</td><td>❌</td></tr><tr><td>Filters</td><td>❌</td></tr><tr><td>Expressions</td><td>❌</td></tr><tr><td>Aggregations</td><td>❌</td></tr><tr><td>Calculated Fields</td><td>⚠️</td></tr><tr><td>Parameters</td><td>❌</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

## Supported Use Cases

The connector supports multiple lineage scenarios across maps, data layers, database connections, imported files, and spatial transformations. These scenarios describe areas where lineage extraction functions as expected.&#x20;

### Supported Lineage Scenarios

<table><thead><tr><th width="350">Supported</th><th>Details</th></tr></thead><tbody><tr><td>Map to Data Layer Lineage</td><td>Supports lineage from maps to data layers through Layer and LayerChild mapping</td></tr><tr><td>Data Source Table to Data Layer Lineage</td><td>Extracts lineage from source database tables to data layers</td></tr><tr><td>Live Database Connection to Map Lineage</td><td>Supports lineage from live database connections to maps</td></tr><tr><td>Imported File to Map Lineage</td><td>Supports lineage from CSV, Excel, and Shapefile sources to maps</td></tr><tr><td>Column-Level Lineage</td><td>Supports lineage for calculated and derived fields</td></tr><tr><td>Spatial Join and Filter Lineage</td><td>Supports lineage generated through spatial joins and layer filters</td></tr><tr><td>Aggregation and Transformation Lineage</td><td>Supports aggregation and transformation lineage within data layers</td></tr></tbody></table>

{% hint style="info" %}
Column-level lineage support depends on the availability of source metadata and transformation logic.&#x20;
{% endhint %}

## Partial or Limited Coverage

Certain lineage scenarios have partial coverage due to limited metadata availability, transformation complexity, spatial processing behavior, or restricted access to sources. These scenarios may produce incomplete or partially resolved lineage results.&#x20;

### Scenarios

<table><thead><tr><th width="307.3333740234375">Scenario</th><th>Limitation Description</th></tr></thead><tbody><tr><td>Calculated Fields</td><td>Complex or nested expressions may not resolve fully</td></tr><tr><td>Derived Attributes</td><td>Multi-level or conditional transformations may be partially parsed</td></tr><tr><td>Spatial Operations</td><td>Advanced geometry transformations, such as buffers and intersections, are not fully traced</td></tr><tr><td>External Data Links</td><td>Live service or API-based data layers are not captured in lineage</td></tr><tr><td>Dynamic Layer Definitions</td><td>Parameterized or script-generated layers may be skipped during lineage extraction</td></tr><tr><td>Encrypted or Restricted Sources</td><td>Schema extraction may fail when source access is limited</td></tr><tr><td>Missing Layer Metadata</td><td>Prevents complete lineage construction</td></tr><tr><td>Map-Level Lineage Status</td><td>Lineage status may appear incomplete if one or more layers fail to parse</td></tr></tbody></table>

{% hint style="info" %}
Incomplete metadata, restricted access, or unsupported spatial transformations can prevent the generation of a complete lineage.&#x20;
{% endhint %}

## Unsupported Scenarios

The connector does not support lineage extraction for certain mapping behaviors, visualization dependencies, scripting logic, and advanced transformation scenarios due to limitations in the metadata available for access and the processing capabilities.&#x20;

### Unsupported Lineage

<table><thead><tr><th width="326">Not Supported</th><th>Description</th></tr></thead><tbody><tr><td>Map Layer Relationships</td><td>Joins or relationships defined between map layers are not supported</td></tr><tr><td>Hierarchical or Grouped Data Layers</td><td>Hierarchical and grouped layer structures are not captured in lineage</td></tr><tr><td>Map-Level or Dashboard-Level Filters</td><td>Filters applied at the map or dashboard level are not included in lineage</td></tr><tr><td>User-Defined Parameters</td><td>Parameters used in dynamic maps are not supported</td></tr><tr><td>Cross-Map or Cross-Dashboard Dependencies</td><td>Dependencies across multiple maps or dashboards are not tracked</td></tr><tr><td>Custom Scripting</td><td>JavaScript or Python scripts used in data layers or visualizations are not supported</td></tr><tr><td>Complex Multi-Step Expressions</td><td>Conditional or chained calculations are not fully processed</td></tr><tr><td>Inter-Layer Field Dependencies</td><td>Field dependencies across multiple data sources or layers are not supported</td></tr></tbody></table>

{% hint style="info" %}
Unsupported scenarios will not generate lineage and may appear disconnected in lineage visualization.&#x20;
{% endhint %}

## Current Functional Status

This section describes the current lineage coverage and functional behavior supported by the CartoVista connector.&#x20;

<table><thead><tr><th width="196">Status Area</th><th>Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Intermediate coverage across maps, layers, and connected data sources</td></tr><tr><td>Lineage Depth</td><td>Supports layer-level and column-level lineage tracing</td></tr><tr><td>Supported Inputs</td><td>Maps, data layers, live database connections, imported files, and spatial transformations</td></tr><tr><td>Functional Scope</td><td>Lineage extraction works for standard mapping and transformation scenarios</td></tr><tr><td>Limitation Areas</td><td>Complex spatial operations, dynamic layers, restricted metadata, and unsupported scripting logic</td></tr><tr><td>Resulting Output</td><td>Reliable lineage generation for supported scenarios, with partial mapping in limited or unsupported areas</td></tr></tbody></table>

{% hint style="info" %}
The connector provides reliable lineage coverage for standard spatial mapping scenarios. However, advanced spatial operations, dynamic layer generation, and complex transformation logic may result in incomplete lineage extraction.&#x20;
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/connectors/connector-repositories/reporting-tool/cartovista/cartovista-lineage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.