ChoiceGeometryType (Geotools modules 30-SNAPSHOT API)

All Superinterfaces:

AttributeDescriptor, AttributeType, GeometryDescriptor, GeometryType, PropertyDescriptor, PropertyType

All Known Implementing Classes:

ChoiceGeometryTypeImpl
```
public interface ChoiceGeometryType
extends GeometryType, GeometryDescriptor
```

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`Object`	`convert(Object obj)`	Yet another hack in order to use our FeatureType.
`Class<?>[]`	`getChoices()`	Gets the choices

Methods inherited from interface AttributeDescriptor
getDefaultValue, getLocalName

Methods inherited from interface AttributeType
getSuper, isIdentified

Methods inherited from interface GeometryDescriptor
getCoordinateReferenceSystem, getType

Methods inherited from interface GeometryType
getCoordinateReferenceSystem

Methods inherited from interface PropertyDescriptor
getMaxOccurs, getMinOccurs, getName, getUserData, isNillable

Methods inherited from interface PropertyType
equals, getBinding, getDescription, getName, getRestrictions, getUserData, hashCode, isAbstract

- Method Detail
  - getChoices
```
Class<?>[] getChoices()
```
    Gets the choices
    
    Returns:
    
    the potential types
  - convert
```
Object convert(Object obj)
```
    Yet another hack in order to use our FeatureType. Converts object to the "real" attribute type.
    Best to explain by Example.
    Consider a choice between Polygon and MultiPolygon. It doesn't make sense to be a Geometry Attribute Type since normal attribute type inspection will allow users/clients to set Points and lines as legal attribute. For parsing purposes, this make the FeatureType a little more accurate. It is not perfect of course since The choice Line, Polygon and MultiPolygon still has to be of Type Geometry but it is a little better.