Besides the common data that can be stored for every feature, the data that can be stored for a feature of a specific feature type is defined by the feature type. The data that can be stored for a feature can be logically divided into the parts listed in table 1.
Data part |
Description |
Base data is data that can be or must be specified for each feature disregarding the feature type. Following data is part of a feature's base data: •Unique Feature ID (an integerassigned by the Application Server). The unique feature ID cannot be changed once the feature is created. •Feature GUID a globally unique id for a feature. Can be assigned when a feature is created or will be automatically set by the Application Server when the feature is created. •Assignment to a domain. The assignment cannot be changed once the feature is created. •Name of the feature. •Textual description of the feature, •Specification of the feature subtype •Approval information |
|
Data that specifies the location, shape and orientation of the feature. If spatial data can be stored for a feature and what type of spatial systems can be used is defined by the feature type. The actual spatial reference system on which a feature's spatial data is based is usually defined when a feature is created, and can be changed afterwards. |
|
Each feature type can define type specific data that can be stored with each feature of that type.Type specific data is an instance of a property structure defined by the feature type. Not all feature types define a property structure for type specific data, i.e. hot all features have type specific data. |
|
Calculation configuration data |
If a feature is a calculated feature, the calculation algorithm and other settings that specify the calculation are stored with the feature. |
Connector configuration data |
If the feature's data source is set to connector the connector configuration data is used to define where the data is read from and might provide additional settings depending on the chosen connector type. |
Relations |
If a feature is of a type of class platform, group or network it can store relations to its member features. |
Configuration data |
Data that configures the internal handling of the feature by the Application server and does not describe natural characteristics of the described phenomenon. Among others this is: •Date of last modification •Date of creation |
