Hi Pierrick, In geotools 2.4 there are two parsers / encoders for gml. Sadly the first ( which has been around for a while ), is not that well maintained. And these bugs are scheduled against it.
I have been working on second generation of the parser. Documentation here: http://docs.codehaus.org/display/GEOTDOC/05+XML+Parsing+and+Encoding http://docs.codehaus.org/display/GEOTDOC/XML+Developers+Guide I tried both of these files with the "new" parser and is doesn't throw exceptions. However I notice that the first file (Test.xml) is not valid gml. Two issues i found were: 1. the bounds on the feature collection uses gml:Null, where as it should be just "null" according to the gml2 schema 2. the "location" elements are of type point property, which can only contain "gml:Point" elements. The airports.gml file works fine though. -Justin Pierrick Brihaye wrote: > 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. > > 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. > > 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 > > ... 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 > > Should I expect these issues to be fixed "soon" or should I implement > work arounds in eXist's code ? > > 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). > > Cheers, > > p.b. > > > ------------------------------------------------------------------------- > 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 -- Justin Deoliveira The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- 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
