asam-ev / qc-framework

Mozilla Public License 2.0
16 stars 8 forks source link

Handling of domain specific issue location types (preserve data and add to reporting) #10

Closed andreaskern74 closed 3 months ago

andreaskern74 commented 8 months ago

Is your feature request related to a problem? Please describe.

The framework shall be independent from specific standards. So, if needed, handling of domain specific things need to be moved to domain specific Checker Libraries.

Nevertheless, it shall be possible that Checkers report domain specific issue locations, e.g. OpenDRIVE <RoadLocation/>, <GeoLocation/> or a <TimeStamp/>. The framework itself has no specific functionality for them, but the information should be preserved during processing the reported information.

Describe the solution you'd like

Beside the standard location types <FileLocation/>, <XmlLocation/> or a <InertialLocation/>, allow any types of elements in the schema. This information shall not be modified in the result pooling.

The properties of the domain specific location shall be reported in the detailed information of an issue.

Example: <RoadLocation id="3" s="5.4" t="0.0"/> should be reported in a form like RoadLocation id="3" s="5.4" t="0.0" in the TextReport Module and in the detailed issue info (left/bottom in GUI) in the ReportGUI.

andreaskern74 commented 8 months ago

This is related to #9