Re: [Geotools-devel] Encoding GML and Xlink

2010-05-20 Thread Rini Angreani
Hi all, Resurrecting this old thread. I've discussed this with Ben, who suggested to add an option for the users to enable automatic xlink:href at their own risk (of slowness). The issue has been raised here: GEOT-3094. I think it's a good idea, as done for GEOT-3046. Should we go ahead and do

Re: [Geotools-devel] Encoding GML and Xlink

2010-05-20 Thread Andrea Aime
Rini Angreani ha scritto: Hi all, Resurrecting this old thread. I've discussed this with Ben, who suggested to add an option for the users to enable automatic xlink:href at their own risk (of slowness). The issue has been raised here: GEOT-3094. I think it's a good idea, as done for

Re: [Geotools-devel] Encoding GML and Xlink

2010-05-20 Thread Rini Angreani
Excellent. I'll make sure our developer tries to make this as memory efficient as possible. Otherwise we can display a message to warn users for the impact if it can't be helped. Cheers Rini -- View this message in context:

Re: [Geotools-devel] Encoding GML and Xlink

2010-04-22 Thread Rob van Swol
To answer my own questions again: in my schema the namespace declaration xmlns:xlink="http://www.w3.org/1999/xlink" was missing! And from a previous post: The gml:boundedBy element can be left out by using ApplicationSchemaConfiguration config = new

Re: [Geotools-devel] Encoding GML and Xlink

2010-04-22 Thread Rini Angreani
Hi all, Sorry for the late reply, I completely missed this discussion thread before. Rob, this is a known problem in our internal JIRA, but I neglected to create an issue in Geotools JIRA. At the moment, it will always do it for complex attributes only, because I only put the code that does

Re: [Geotools-devel] Encoding GML and Xlink

2010-04-21 Thread Rob van Swol
Hi, To answer my own question: 1) changing SurfacePropertyType into GeometryPropertyType inĀ  the schema and creating an empty Geometry does the trick! 2) looking at the code I discovered that the check on existing id's is done based on the id of the feature NOT on the id of the geometry! I am

Re: [Geotools-devel] Encoding GML and Xlink

2010-04-21 Thread Andrea Aime
Ben Caradoc-Davies ha scritto: Andrea, is XSIdRegistry turned off for simple features, for performance and memory reasons? I recall a discussion ... Not sure. I remember at one point something that kept in memory every id of every feature encoded was added that increased dramatically both

Re: [Geotools-devel] Encoding GML and Xlink

2010-04-21 Thread Rob van Swol
Hi, Perhaps I have not found the complete solution yet, because I just noticed that a href attribute is used where I would expect a xlink:href attribute. Also the xlink namespace definition is missing. Am I still doing something wrong? Thanks for your reaction. Regards, Rob van Swol On

Re: [Geotools-devel] Encoding GML and Xlink

2010-04-21 Thread Ben Caradoc-Davies
On 21/04/10 14:58, Rob van Swol wrote: 1) changing SurfacePropertyType into GeometryPropertyType in the schema and creating an empty Geometry does the trick! Well done, Rob, that is an excellent result! -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO

[Geotools-devel] Encoding GML and Xlink

2010-04-20 Thread Rob van Swol
Hi, I have a simple GML3 Application schema which I use to encode a featurecollection to a gml document. However I do not succeed in getting duplicate gml:id's in geometry elements to be replaced by xlink:href attributes. Even worse: duplicate id's are accepted while I thought that the