For deleting features and observations Redbex uses a two step approach. When the user deletes a feature or an observation that feature or observation is first just marked as being deleted and will removed from the database by a purging procedure that runs in the background afterward.

I.e. the feature or observation will be immediately marked as being deleted but will be purged from the Redbex Application Server database at some later (non deterministic) point in time.

This two step approach is implemented for optimizing the system performance especially when deleting big amounts of features or observations.

Data affected when deleting a feature

When a feature is deleted (and eventually) purged following data is irreversibly deleted

•The feature itself (including base data, type specific data, spatial data etc.)

•If the feature is linked by another feature or observation through a property of type feature link, the value of the property will be deleted.

•If the feature is a platform feature all the features belonging to that platform will be released (not be linked to the platform any more)

•If the feature is a group feature all the group members will be released (not member of that group any more)

•If the feature is used in calculated feature algorithm it will be removed (possibly breaking the algorithm)

•If the feature instantiated other features, those instantiated features will be released, i.e. it is not traceable any more where the instantiated feature came from.

•If the feature is member of a platform, group or network or platform it will of course also be removed from that.

•Alias names in alias schemes for this feature

•Any associated data of the feature

•Any property structure configuration of that feature

•Any privileges where the feature is privilege object

•Any approval workflows assigned to the feature will be deleted

•Observations of the feature - see below for more details

Data affected when deleting an observation

When an observation is deleted (and eventually purged) following data is irreversibly deleted

•The observation itself (including base data, type specific data, spatial data etc.)

•Any assigned Approval workflows

•All observation alarms

•Any associated data of the observation