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
Supported Data Layers
Supported data layer types for lineage extraction must be defined in CrawlerOption.supportingDataLayers.
Connection Priority
Connection priority for lineage processing must be defined in CrawlerOption.connectionsPriorityForLineage.
Authentication
Requires valid API credentials for CartoVista access with Map Gallery User role or higher.
Access Requirements
Requires a valid CartoVista connection ID and domain access to store lineage. Database connections must be pre-crawled for DataTable and column matching.
Tenant Settings
Not applicable
Lineage Options
Semantic table creation and column-level lineage are enabled by default.
Ensure associated database connections are crawled before lineage extraction to support DataTable and column matching.
Incorrect configuration, insufficient permissions, or missing metadata may prevent the connector from identifying the correct lineage path or building complete lineage relationships.
Lineage Components
Maps
✅
Layers
✅
DataTables
✅
DataTable Columns
✅
Slides
✅
Semantic Tables
✅
Renamed Columns
✅
Temp Columns
✅
Semantic Columns
✅
WMS Layers
⚠️
WMTS Layers
⚠️
Grid Layers
❌
Calculated Fields / Formulas
⚠️
Derived Columns
⚠️
Geographic / Spatial Fields
⚠️
Relationships
❌
Hierarchies
❌
Filters
❌
Expressions
❌
Aggregations
❌
Calculated Fields
⚠️
Parameters
❌
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
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.
Supported Lineage Scenarios
Map to Data Layer Lineage
Supports lineage from maps to data layers through Layer and LayerChild mapping
Data Source Table to Data Layer Lineage
Extracts lineage from source database tables to data layers
Live Database Connection to Map Lineage
Supports lineage from live database connections to maps
Imported File to Map Lineage
Supports lineage from CSV, Excel, and Shapefile sources to maps
Column-Level Lineage
Supports lineage for calculated and derived fields
Spatial Join and Filter Lineage
Supports lineage generated through spatial joins and layer filters
Aggregation and Transformation Lineage
Supports aggregation and transformation lineage within data layers
Column-level lineage support depends on the availability of source metadata and transformation logic.
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.
Scenarios
Calculated Fields
Complex or nested expressions may not resolve fully
Derived Attributes
Multi-level or conditional transformations may be partially parsed
Spatial Operations
Advanced geometry transformations, such as buffers and intersections, are not fully traced
External Data Links
Live service or API-based data layers are not captured in lineage
Dynamic Layer Definitions
Parameterized or script-generated layers may be skipped during lineage extraction
Encrypted or Restricted Sources
Schema extraction may fail when source access is limited
Missing Layer Metadata
Prevents complete lineage construction
Map-Level Lineage Status
Lineage status may appear incomplete if one or more layers fail to parse
Incomplete metadata, restricted access, or unsupported spatial transformations can prevent the generation of a complete lineage.
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.
Unsupported Lineage
Map Layer Relationships
Joins or relationships defined between map layers are not supported
Hierarchical or Grouped Data Layers
Hierarchical and grouped layer structures are not captured in lineage
Map-Level or Dashboard-Level Filters
Filters applied at the map or dashboard level are not included in lineage
User-Defined Parameters
Parameters used in dynamic maps are not supported
Cross-Map or Cross-Dashboard Dependencies
Dependencies across multiple maps or dashboards are not tracked
Custom Scripting
JavaScript or Python scripts used in data layers or visualizations are not supported
Complex Multi-Step Expressions
Conditional or chained calculations are not fully processed
Inter-Layer Field Dependencies
Field dependencies across multiple data sources or layers are not supported
Unsupported scenarios will not generate lineage and may appear disconnected in lineage visualization.
Current Functional Status
This section describes the current lineage coverage and functional behavior supported by the CartoVista connector.
Overall Coverage
Intermediate coverage across maps, layers, and connected data sources
Lineage Depth
Supports layer-level and column-level lineage tracing
Supported Inputs
Maps, data layers, live database connections, imported files, and spatial transformations
Functional Scope
Lineage extraction works for standard mapping and transformation scenarios
Limitation Areas
Complex spatial operations, dynamic layers, restricted metadata, and unsupported scripting logic
Resulting Output
Reliable lineage generation for supported scenarios, with partial mapping in limited or unsupported areas
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.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?