The process described here completes the workflow by finalizing the data to use for creating products. Certification takes place after all the source data has been reviewed and revised.
Certification identifies the status of features in the database. Every source object is assigned one of these status values:
Status | Assigned |
|---|---|
Under Construction | • To all new features • When a feature representation or attribute information is edited • When a representation is assigned to another usage |
Not Verified | • After editing is complete and the feature is submitted for verification. |
Accepted | • When feature attributes and representation are known to be acceptable. This step is optional. |
Verified | • If a Quality Assurance user decides a feature is acceptable (complete and correct) and ready for a product. |
Rejected | • If a Quality Assurance user decides a feature is unacceptable (incomplete or incorrect) Rejected features must be reprocessed by an editor and re-submitted for verification (status reset to Not Verified). A marker can be created to explain to the editor the reason for the rejection. |
Status can be set when data is bulk loaded into the source database.
Certification can apply to:
• Representations: spatial/positional information
• Attributes: non-spatial/descriptive information
• Feature Certification: both representations and attributes
• Product Feature Certification: product-specific features
Representations and attributes can be treated individually or as a group by certifying both in a single step.
This shows typical workflows for certifying features. User roles determine which certification functions you can perform.

If an attribute value or spatial representation is changed, the attribute or representation status is automatically changed to Under Construction no matter what the previous status was. |
Only the most recent version of features with a status of Verified (as verified in the Source Editor) can be used for products. |
When a product is created, representations extracted from the source database are given the status of Verified in the new product. If other features are added to the product as product-specific features, these are flagged as Under Construction. These features have to be verified.
Related commands
• • | • • |