You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the definition of attributes requires to specify a Domain, a Range, a default value, and a null_value?
This should be ok for numerical attributes (price, performance) but not for other types of attributes such as for example a simple "note" (a string). For example the Glencoe tool supports a "note" attribute in the features for documentation.
How can this be modeled within the current Attributes definition?
The text was updated successfully, but these errors were encountered:
Currently, the definition of attributes requires to specify a Domain, a Range, a default value, and a null_value?
This should be ok for numerical attributes (price, performance) but not for other types of attributes such as for example a simple "note" (a string). For example the Glencoe tool supports a "note" attribute in the features for documentation.
How can this be modeled within the current Attributes definition?
The text was updated successfully, but these errors were encountered: