Hi Pierrick - welcome Comments inline. > Hi, > > First, let me introduce myself : I'm one of the developers of eXist, an > open source native XML database (http://exist.sourceforge.net/). In > order to make a proof-of-concept for our new modularized indexes, I'm > currently working on implementing spatial indexes for GML files. > Nice stuff. > For this purpose, I'm using Geotools - I'm watching it from its very > beginning -, mainly the GML and the CRS stuff. I've downloaded the > 2.4-M1 binaries (from http://geotools.codehaus.org/2.4-M1) and I rely on > 2.4-M1 javadocs (http://javadoc.geotools.fr/), sometimes following the > links to SVN HEAD to study the code (I wish we had line numbers displayed). > > Everything's going well so far. However, I encounter a few issues. > > I've heard that the feature model is likely to change in the next months > but I only need to access geometries (other stuff around it will - > hopefully - be handled by eXist ;-), at least for now. > Fair enough; please proceeded - the change between FeatureModels should be smooth. Changing to a new feature model freeks everyone out and has done so as long as I have know the project; while there is danger that someone might have funding to do the work in the next couple of months, we have spent so long fussing over it that you can be assured everyone is aware of the dangers. > So my question is about the present and future of Geotools's GML stuff > and, in particular about this long-standing issue : > > http://codehaus01a.managed.contegix.com/browse/GEOT-742 > > Before I start I would like to introduce you to the following page. - http://docs.codehaus.org/display/GEOTDOC/08+XML
As you read that you can see there are four parsers avaialble to you. May I recommend you use the one Justin is working on? We really would like to throw away these SAX and DOM parsers as soon as possible. > ... which makes detection of "wrong" geometries more difficult that it > needs to be (not counting the hard-coded messages on System.err). > > Implementing this RFE would also make my life easier :-) : > > http://codehaus01a.managed.contegix.com/browse/GEOT-1239 > I would not expect any action on this - simply because it is a case Justin's parser handles well. > Should I expect these issues to be fixed "soon" or should I implement > work arounds in eXist's code ? > Could you provide us a patch? Even a ready to go test case can help so we can run through it in a debugger. > Usually, I would have filled patches, just like an open source developer > should do but I still have some difficulties to master Geotools's > development process (namely Maven). > Ah ... well if you can get the code to go in eclipse a patch from there will also work. If you jump on the #geotools channel we can also talk you through maven build questions (last week was a bit of a mess but normally the build is fine). Jody ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
