Non-Conformance Report
A Task Results report is generated by Check Rules task(s) run in a Session, which is then available to view and to download as JSON. When added to a Session, the Non-Conformance Report Data Store will generate features from all the task results report that precede it. These can subsequently be exported to a data format supported by 1Integrate (see Supported Data Stores).
Note: This combines the results of all task results and will not contain any amendments created from any Actions that precede it. So fixed objects that occur after the Rule has been run, will still have objects created for them in the Non-conformance Data Store.
Both non-spatial and spatial non-conformances are included, and all contain:
-
The ID of the failing feature (if the data store can determine which attribute is the ID).
-
Details of the rule that failed.
-
The feature class.
-
The geometry or attribute names.
-
All reported attribute values encoded in JSON.
Non-conformance Attributes
The following attributes can be reported on when performing a non-conformance report.
Note: Each attribute name will be preceded by the "sys_" or "sys:" depending on the data store e.g. "sys_attributes" or "sys:feature_id".
|
Attribute |
Description |
|---|---|
|
attributes |
A comma separated list of attributes and their values; the failing attribute(s), a geometry (minimum bounding rectangle) and any attributes selected for reporting. |
|
attribute_names |
A comma separated list of the attribute(s) that fail a Rule when the non-conformance is from a non-spatial check. |
|
error_message (error non-conformances only) |
A description of the error that occurred. |
|
feature_class |
The |
|
feature_id |
The ID of the non-conforming root feature, if the Data Store can specify which attribute is the unique id. Not all Data Stores are able to specify which attribute represents a unique ID. Note: Setting a unique key will ensure the feature_id is populated. You can set a unique key on the Data Store by right-clicking on an attribute and selecting “Set Unique Key. |
|
gothic_id |
An internal system ID for the feature, unique within the Session. |
|
rule_auto_description |
A description of the Rule against which the feature did not conform. |
|
rule_name |
The name provided for the Rule. |
|
rule_path |
The location of the Rule in the folder structure. |
|
geometry (spatial non-conformances only) |
A point or multi-point geometry pinpointing the location of the spatial non-conformance. Geometry is calculated from the inferred hotspot which is either:
|
