|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface ChoiceGeometryType
Method Summary | |
---|---|
java.lang.Object |
convert(java.lang.Object obj)
Yet another hack in order to use our FeatureType. |
java.lang.Class[] |
getChoices()
Gets the choices |
Methods inherited from interface org.opengis.feature.type.GeometryType |
---|
getCoordinateReferenceSystem |
Methods inherited from interface org.opengis.feature.type.AttributeType |
---|
getSuper, isIdentified |
Methods inherited from interface org.opengis.feature.type.PropertyType |
---|
equals, getBinding, getDescription, getName, getRestrictions, getUserData, hashCode, isAbstract |
Methods inherited from interface org.opengis.feature.type.GeometryDescriptor |
---|
getCoordinateReferenceSystem, getType |
Methods inherited from interface org.opengis.feature.type.AttributeDescriptor |
---|
getDefaultValue, getLocalName |
Methods inherited from interface org.opengis.feature.type.PropertyDescriptor |
---|
getMaxOccurs, getMinOccurs, getName, getUserData, isNillable |
Method Detail |
---|
java.lang.Class[] getChoices()
java.lang.Object convert(java.lang.Object obj)
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.
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |