[Geotools-devel] uomLabels in gml 3.2

2013-07-16 Thread Rini.Angreani
Hi Justin, I am trying to get uomLabels to appear in LineString, based on GML 3.2: http://schemas.opengis.net/gml/3.2.1/geometryBasic0d1d.xsd. (Actually from GML 3.1.0 onwards). I can see if I make changes to AbstractGeometryTypeBinding, it will create the same problem with srsDimension (where

[Geotools-devel] FW: Pull Request to upgrade JAITools

2013-07-16 Thread Brett Walker
-Original Message- From: Michael Bedward [mailto:michael.bedw...@gmail.com] Sent: Wednesday, 17 July 2013 11:18 AM To: Brett Walker Cc: geotools-devel@lists.sourceforge.net; jody.garn...@gmail.com Subject: Re: Pull Request to upgrade JAITools Hi Brett, Thanks for this work. Yes, there

Re: [Geotools-devel] Pull Request to upgrade JAITools

2013-07-16 Thread Michael Bedward
Hi Brett, Thanks for this work. Yes, there were substantial changes to RangeLookupTable and related classes to fix thread safety, so it's no surprise that you had to hack things at the GeoTools end. However, I don't know the CoverageUtilities code at all - it would be best to ask Simone, Andrea o

[Geotools-devel] Pull Request to upgrade JAITools

2013-07-16 Thread Brett Walker
Hi, I have made a pull request to upgrade JAITools to version 1.3.1. To get the build to pass it seems that I had to brutalise a method in CoverageUtilities.java (https://github.com/brett-walker/geotools/commit/35ee8f8434f2dbb435622671f725a08e295df848) A question for Jody or Michael. Do the c

[Geotools-devel] [Hudson] Hudson build is back to normal : geotools-master-jdbc #342

2013-07-16 Thread Hudson
See -- This message is automatically generated by Hudson. For more information on Hudson, see: http://hudson-ci.org/ -- See everything from the browser to

Re: [Geotools-devel] [ExternalEmail] GeoTools / GeoServer Meeting 2013-07-08

2013-07-16 Thread Ben Caradoc-Davies
Should now be fixed: https://jira.codehaus.org/browse/GEOS-5884 Kind regards, Ben. On 11/07/13 13:22, Ben Caradoc-Davies wrote: > Thanks, Justin, i can confirm this failure. > > My bad (or rather, POSIX's perversity); the POSIX for is MDT+6 not MDT-6 > (yes, hours west). (Aren't you in DST until