Hi Akos,
I think this discussion should move to the developer list, as it is really
becoming a discussion on how to better add 3d support to the library, and
other devs will have opinions as to where various classes should go.
There have been specific modules dedicated to 3d in the past. Namely
geometry and jts-wrapper in the unsupported modules.
-Justin
On Fri, Feb 24, 2012 at 2:55 AM, Ákos Maróy <[email protected]> wrote:
> Justi,
>
> > GML 3.2 is huge as you know so no we don't do everything, really just
> > the simple geometry stuff and the feature model. Some recent support was
> > added to do curves and surfaces, but mapping them still to the JTS 2d
> > geometry model.
>
> thank you for the explanation.
>
> > When you say "spread out" what exactly do you mean. All the xml parsing
> > and encoding should be contained to a single set of modules.
> >
> > http://svn.osgeo.org/geotools/trunk/modules/extension/xsd/
> >
> > With the gml 3.2 stuff living in the xsd-gml3 module. But the objects
> > that the parser parses into / encodes from are spread out indeed among
> > the other modules in geotools.
>
> yes, I guess this is what I meant with being spread out :) I found some
> objects that 'looked useful' in various packages, for example:
>
> org.geotools.gml3.Curve class, which expects a
> com.vividsolutions.jts.geom.LineString class
>
> org.opengis.geometry.coordinate.GeometryFactory with the
> createGeodesicString() function, etc.
>
> I see the org.opengis.geometry.primitive.Ring class
>
>
> or, when trying out the following code:
>
> GeometryBuilder builder = new GeometryBuilder(DefaultGeographicCRS.WGS84);
>
> GeometryFactory gf = builder.getGeometryFactory();
>
> List<Position> dps = new ArrayList<Position>();
> dps.add(builder.createPoint( new double[] {47.516389, 18.974444}));
> dps.add(builder.createPoint( new double[] {47.515278, 19.021667}));
> dps.add(builder.createPoint( new double[] {47.516389, 18.974444}));
>
> GeodesicString gs = gf.createGeodesicString(dps);
>
>
> this fails at the last line with 'not implemented'
>
>
>
> in essence it is not clear to me what classes should be in the xsd-gml3
> module, what classes are 'around' in other modules.
>
>
> > Well you are certainly welcomed and encouraged to start looking at the
> > xsd modules, and i think you will find that any patches you submit will
> > be reviewed in a timely manner.
>
> thank you for the encouragement.
>
> first, as you see, I'll need a GeodesicString implementation that works.
> where do you suggest I start with that? work with the class above that
> says 'not implemented'?
>
> my initial goal is to create a GML 3.2 surface, shich contains a
> PolygonPatch -> Ring -> Curve -> GeodesicString
>
>
> Akos
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
GeoTools-GT2-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
