My last message was too long :-) > gml:AbstractFeatureType > <>--- gml:LocationPropertyType > <>--- gml:AbstractGeometryType
They have this organization because they LocationPropertyType is actually adding value; it is used as a choice between a Geometry and a couple other things :-) There model explicitly wants a choice here between a number of different options; and so we are going to explicitly represent this. If we were doing it in Java code we would need to break out a separate class to handle the situation - so our feature model is no worse then Java. > The information we are trying to convey has only two GeoAPI objects: Modified diagram: Feature <>--the_geom-- Geometry And you can represent that; but for many of the GML models you are looking at they want something more resulting in extra complexity on their side. If you just have that relationship above then there is a very simple representation of that in our feature model. An attribute called "the_geom" of type Geometry Jody ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
