Source Model Traceability

[MisterGC]

Empower MapViewer users with the ability to trace back to the original source model from the MapViewer's feature model. This enhancement will provide a clearer understanding of the data's original structure and relationships, significantly enriching the MapViewer's analytical utility and usability.

Ideas:

1. Traceability Implementation: Enable users to visualize the pathway from the mapviewer's feature model aspects to their corresponding aspects in the original source model.

2. Interactive Association: Create a user-friendly interface allowing users to trace feature model aspects back to their source model origins.

3. Visual Indicators: Implement visual cues to highlight features in the common model and their source model origins, enhancing traceability.

4. Dynamic Exploration: Allow users to toggle between the common feature model view and its traced source model view, fostering deeper understanding and comparison.

5. Attribute Accessibility: Display the original attributes and metadata from the source model alongside the corresponding features in the common feature model.

6. Source Model Snapshot: Present a transformed representation of the source model, reflecting its original storage format within the MapViewer.

Benefits:

• In-depth Data Comprehension: Users will achieve a thorough understanding of the common feature model and its tracing back to the original source model, bolstering data exploration.

• Robust Analytical Capability: By enabling users to trace and compare the common feature model with its source, we can provide deeper insights and facilitate informed decision-making.

• Seamless Traceability: The new feature will simplify the process of tracing back to original data sources, removing the need for external tools or manual processes.

• User-friendly Navigation: An intuitive interface for tracing associations and switching views will render the MapViewer more accessible and easier to use.

In summary, this feature will enhance the MapViewer by enabling users to trace the origins of data in the common feature model back to its original source model, thereby offering a comprehensive, insightful data exploration experience.

[josephbirkner]

I would see this issue more in mapget, to be honest. We need to be able to attach source model blobs to TileFeatureLayers, and then add source model references to attributes/geometry in an efficient way. On the erdblick side, we need to figure out how the user is supposed to interact with these links in the frontend.

[josephbirkner]

Ideas from @reinco:

• (a) Show complete blob content. One idea is to add tiles as features. When clicking a tile the blob content is shown in the feature info panel.
• (b) if an array id / feature id is shown in a panel allow to expand towards the location in the blob inspector tree view. This could be easy from the raw data view in (1). For example: the raw view tree would have a element with a reference in the blob like 'laneLayer.laneGroup[10].lane[1].laneId'. That reference can be directly looked up in the smart layer blob

[josephbirkner]

Support will be implemented based on ndsev/mapget#75

For any feature aspect which has a SourceDataLink, a corresponding Show Source Data action will be offered in the inspection panel.

Following a source data link will trigger a new inspection action, which replaces the content of the inspection panel with a view of the source data tree. The source data region identified by the source data address is highlighted. The source data layer selection + address is also encoded in the URL, so a link can be easily shared and the existing history-based inspection navigation can be used consistently.

The source data view mainly consists of a PrimeNG TreeTable, as well as links to other Source Data Layers for the same tile. The download button in the Title Bar should lead to a raw source data attachment download.

The TreeTable should support the following columns:

• Bit Offset (Optionally optional)
• Field Name
• Value
• Type (with Developer Portal Link)

Other optional considerations:

• Remember the size of the panel (check for PrimeNG support).
• Pick initial width based on data.