[Geotools-devel] Backporting anchor support for point symbolizer

2015-01-08 Thread Andrea Aime
Hi, this commit on trunk added support for anchorpoint in point symbolizer, which brings us one bit closer to SE 1.1 compliance: https://github.com/geotools/geotools/commit/d62d12e9686b062c82972b45cc54788318599a75 I would like to backport it to the 12.x series. The patch seems large, but if you

Re: [Geotools-devel] Upgrading epsg database

2015-01-08 Thread Justin Deoliveira
Cool, thanks for the info guys. I'll work on this over the next few days to try and get something in for the freeze. On Thu, Jan 8, 2015 at 12:28 AM, Andrea Aime wrote: > On Thu, Jan 8, 2015 at 12:35 AM, Justin Deoliveira > wrote: > >> Hey folks, >> >> I was curious as to what our current polic

[Geotools-devel] Build failed in Jenkins: geotools-master #503

2015-01-08 Thread monitor
See Changes: [tbarsballe] Fix getBounds for diff containing deleted features [jody.garnett] clean up warnings and test bbox handling -- [...truncated 133669 lines...] [ERROR]

[Geotools-devel] [jira] (GEOT-4979) MarchingSquareVectorizer areEqual method should use proper param

2015-01-08 Thread Daniele Romagnoli (JIRA)
Title: Message Title Daniele Romagnoli created an issue

[Geotools-devel] Moving to gt-property-ng - Final migration

2015-01-08 Thread Torben Barsballe
After the latest batch of geotools changes, both geotools and geoserver will now work with gt-property-ng instead of gt-property (Barring a single test failure in AggregatingDataStore, for which a fix can be found here: https://github.com/geotools/geotools/pull/675). In order to complete this chan

Re: [Geotools-devel] Moving to gt-property-ng - Final migration

2015-01-08 Thread Andrea Aime
On Thu, Jan 8, 2015 at 7:53 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > After the latest batch of geotools changes, both geotools and geoserver > will now work with gt-property-ng instead of gt-property (Barring a single > test failure in AggregatingDataStore, for which a fix can

Re: [Geotools-devel] Moving to gt-property-ng - Final migration

2015-01-08 Thread Torben Barsballe
Are we all in agreement to replace gt-property with gt-property-ng? Does anyone have any concerns? Should the old gt-property implementation be completely eliminated, or moved to an unsupported module? Torben On Thu, Jan 8, 2015 at 11:46 AM, Jody Garnett wrote: > Agreed, AbstractDataStore has

Re: [Geotools-devel] Moving to gt-property-ng - Final migration

2015-01-08 Thread Andrea Aime
On Thu, Jan 8, 2015 at 9:13 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > Are we all in agreement to replace gt-property with gt-property-ng? Does > anyone have any concerns? > If everything works in geotools and geoserver, I'd say we have a pretty good test coverage and as a resul

[Geotools-devel] Jenkins build is back to normal : geotools-master #504

2015-01-08 Thread monitor
See -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your h

[Geotools-devel] gt-app-schema - Test Failures

2015-01-08 Thread Torben Barsballe
While migrating the new property-ng implementation to be used by geotools, I ran into a new test failure in gt-app-schema On line 133

[Geotools-devel] [jira] (GEOT-4980) Clean up entries when removing a feature table.

2015-01-08 Thread Jared Erickson (JIRA)
Title: Message Title Jared Erickson created an issue

Re: [Geotools-devel] gt-app-schema - Test Failures

2015-01-08 Thread Jody Garnett
Hi Torben: Ben was our usual contact for app schema stuff. Perhaps we can step through the same test with the original property datastore implementation and see how it was working (I won't claim to know how it was supposed to work). Jody -- Jody Garnett On 8 January 2015 at 15:51, Torben Barsba

Re: [Geotools-devel] Backporting anchor support for point symbolizer

2015-01-08 Thread Jody Garnett
Thanks Andrea I am keen to see our SE 1.1 story improved over time. I had a look at the commit, added a few comments. I am fine with the work, was a bit startled to see this functionality added to SLD 1.0 documents and internal SLD schema. I understand we made our core SLDParser relaxed enough to