Re: [Geotools-devel] Update to 8.0 wiki page reminder

I added a section with a table listing the deprecated methods I had to change (and any other well-documented ones I found in the diff): http://docs.codehaus.org/display/GEOTOOLS/Upgrade+to+8.0#Upgradeto8.0-gtopengis%2Cgtreferencing%3Adeprecatedmethodsremoved I have no examples, but simboss should

[Geotools-devel] Hudson build is back to normal : geotools-trunk #3608

See -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3606

From #geotools: jgarnett, I see the problem: simboss removed a bunch of deprecated methods and did not build with -Dall, missing the dependent modules that used the removed methods. jgarnett, I am fixing them now. On 18/05/11 10:45, Ben Caradoc-Davies wrote: > Still broken. Are you

[Geotools-devel] [jira] Created: (GEOT-3594) "Clean up" app-schema after changes in core

"Clean up" app-schema after changes in core --- Key: GEOT-3594 URL: http://jira.codehaus.org/browse/GEOT-3594 Project: GeoTools Issue Type: Improvement Components: data app-schema

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3606

Still broken. Are you looking at it? Did you build with -Dall? On 18/05/11 06:30, Simone Giannecchini wrote: > strange, > I just did a full build after this > http://jira.codehaus.org/browse/GEOT-3592 and it succeeded. > > Going to build again and see if I can reproduce. Sorry for the inconvenienc

[Geotools-devel] [jira] Created: (GEOT-3593) Improve app-schema ORM performance with respect to feature chaining

Improve app-schema ORM performance with respect to feature chaining --- Key: GEOT-3593 URL: http://jira.codehaus.org/browse/GEOT-3593 Project: GeoTools Issue Type: Improvement

[Geotools-devel] geoserver welcome page

Similar in spirt to annoying 52N and GeoMajas; I would like to set up a welcome page for geoserver developers (even if it is just a link off to geoserver docs on the subject). Specially I am looking for words of advice on DataStore / Catalog handling; and if you know common questions people run

Re: [Geotools-devel] 52N roll call?

Well that was a complete bust; taking the email to their development list to see if they are active; will report back with my findings. -- Jody Garnett On Monday, 16 May 2011 at 5:05 PM, Jody Garnett wrote: > Similar to the last email thread; I would like to make sure we have a > "welcome pag

[Geotools-devel] Build failed in Hudson: geotools-trunk #3607

See Changes: [simonegiannecchini] restoring spatialite -- [...truncated 12583 lines...] [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invoc

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3606

strange, I just did a full build after this http://jira.codehaus.org/browse/GEOT-3592 and it succeeded. Going to build again and see if I can reproduce. Sorry for the inconvenience! Regards, Simone Giannecchini --- Ing. Simone Giannecchini GeoSo

[Geotools-devel] Build failed in Hudson: geotools-trunk #3606

See Changes: [simonegiannecchini] GEOT-3592 -- [...truncated 12603 lines...] [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INF

[Geotools-devel] [jira] Created: (GEOT-3592) Remove minor annoying deprecations form geometry classes in referencing and opengis

Remove minor annoying deprecations form geometry classes in referencing and opengis --- Key: GEOT-3592 URL: http://jira.codehaus.org/browse/GEOT-3592 Project: GeoTools

Re: [Geotools-devel] *updated* proposal on multi-valued attributes in filter comparisons

+1 from me (I can't remember if I voted earlier or not) Ian -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows

[Geotools-devel] [jira] Created: (GEOT-3591) GeoTiff file handles not released when running with large heap

GeoTiff file handles not released when running with large heap -- Key: GEOT-3591 URL: http://jira.codehaus.org/browse/GEOT-3591 Project: GeoTools Issue Type: Bug Component

Re: [Geotools-devel] file streams and jai

Ok, i have created http://jira.codehaus.org/browse/GEOT-3591 to capture all the information, with a link to the data dir containing the layer (single geotiff) i am working against. Also attached is a jmeter plan that reproduces the problem for me. Let me know if there is any more relevant info i c

[Geotools-devel] [jira] Created: (GEOT-3590) CartesianAuthorityFactoryTest test failure on win64

CartesianAuthorityFactoryTest test failure on win64 --- Key: GEOT-3590 URL: http://jira.codehaus.org/browse/GEOT-3590 Project: GeoTools Issue Type: Bug Components: core referencing

Re: [Geotools-devel] gt-grassraster IP review

Regarding the tokenizer I am quite sure I checked license > > compatibility and then put the geotools header on top, leaving also > > the old reference. Thinking about it back then it seemed the proper > > way to me, but now I agree with you. I am not sure what should be > > done. Can other license

Re: [Geotools-devel] gt-grassraster IP review

On 17/05/11 16:47, andrea antonello wrote: > Hi Ben, > I am quite sure this is a leftover of a previous JGrass coauthor > (basically I didn't know it was licensed) . I have to check how much > it is needed. Maybe it can be removed. I think rgb.txt is almost in the public domain, by common usage. I

Re: [Geotools-devel] gt-grassraster IP review

Hi Ben, I am quite sure this is a leftover of a previous JGrass coauthor (basically I didn't know it was licensed) . I have to check how much it is needed. Maybe it can be removed. Regarding the tokenizer I am quite sure I checked license compatibility and then put the geotools header on top, leav

Re: [Geotools-devel] gt-grassraster IP review

rgb.txt has its own wikipedia page: http://en.wikipedia.org/wiki/Rgb.txt Maybe this should be the X Consortium license? The grassraster colour table is missing only a few of the 752 named ccolours in the original X consortium rgb.txt: http://cvsweb.xfree86.org/cvsweb/*checkout*/xc/programs/rgb/r

Re: [Geotools-devel] gt-grassraster IP review

Hi Ben, thank you for your great effort. I will have a look at all your comments, check them out properly and come back to you. Thanks again. Andrea On Tue, May 17, 2011 at 9:27 AM, Ben Caradoc-Davies wrote: > Jody and Andrea, > > I have completed my IP review of gt-grassraster. Findings: > > -

[Geotools-devel] gt-grassraster IP review

Jody and Andrea, I have completed my IP review of gt-grassraster. Findings: - All main source code files have GeoTools headers. - JGrassUtilities.java (org.geotools.gce.grassraster.JGrassUtilities) looks like it contains colour tables (names and RGB components) that are directly converted from