Re: [Geotools-devel] A patch for whole layer transparency and skipping label rendering

On Mon, Sep 24, 2012 at 7:28 AM, Sebastian Graca wrote: > Hello! > > I have created a patch for GeoTools which implements whole layer > transparency (for layers and labels) and allows to skip label rendering > for a layer. The patch is submitted as a github pull request > https://github.com/geoto

Re: [Geotools-devel] Modification to Parameter class for geoprocesses

On Wed, Sep 26, 2012 at 5:28 PM, Victor Olaya wrote: > > > > Could we have more than one relationship? How do we handle it? > > You mean one parameter related to many other ones? That could be > useful, but I guess it risks making it difficult to handle, since > probably additional information wa

Re: [Geotools-devel] Modification to Parameter class for geoprocesses

> Sounds great to me. I guess it's better to use an enum, instead of > string, but the syntax of those examples is perfect from my point of > view Well I want to see it run first, to make sure we are on the right track. > hmmm, I do not understand this one. The GROUP parameter I was > proposing

[Geotools-devel] [jira] (GEOT-4271) Create new arrow shape suitable for winds and currents

Simone Gi

Re: [Geotools-devel] Modification to Parameter class for geoprocesses

> > Could we have more than one relationship? How do we handle it? You mean one parameter related to many other ones? That could be useful, but I guess it risks making it difficult to handle, since probably additional information was needed to fully describe that more complex relation. Can you put

Re: [Geotools-devel] Modification to Parameter class for geoprocesses

On Wed, Sep 26, 2012 at 3:22 PM, Victor Olaya wrote: > > RELATE > > > > How to describe the nature of the relationship? Using strings below? > Perhaps > > best handled with ENUM. > > > > Parameter SNAPPING = new Parameter("snapping", > > Boolean.class, "Enable Snapping", "True to enable snapping,

Re: [Geotools-devel] Modification to Parameter class for geoprocesses

> RELATE > > How to describe the nature of the relationship? Using strings below? Perhaps > best handled with ENUM. > > Parameter SNAPPING = new Parameter("snapping", > Boolean.class, "Enable Snapping", "True to enable snapping, requires use of > 'distance' parameter", true, 1, 1, new KVP( RELATED,

Re: [Geotools-devel] GeoTiffReader: unable to dispose - file still locked

On Tue, Sep 25, 2012 at 4:23 PM, João Belém wrote: > > Hi GT-devs,while using the GeoTiffReader to read a file and get a > GridCoverage2D for getting the Bounds and width and height of the image, I > realized that after finishing that following method the file (in Windows) > is still locked by th

Re: [Geotools-devel] incorrect transformation with epsg hsql database

On Wed, Sep 26, 2012 at 1:36 PM, Jesse Eichar wrote: > There is one single difference. In the old (working) system the WKT used > Oblique_Mercator where the newer ones use Hotine_Oblique_Mercator. Hmm... the Hotine projection has not been touched in years and it's tested too, strange > > So w

Re: [Geotools-devel] incorrect transformation with epsg hsql database

There is one single difference. In the old (working) system the WKT used Oblique_Mercator where the newer ones use Hotine_Oblique_Mercator. So what should I do? How can I override this definition? And can I update the version in Geotools somehow? In other project I have added a epsg-property w

Re: [Geotools-devel] MemoryDataStore axis order flip intended?

On Wed, Sep 26, 2012 at 5:49 AM, Ben Caradoc-Davies < ben.caradoc-dav...@csiro.au> wrote: > Justin, > > all the test data is in longitude/latitude order (the roads set is similar > and labelled with Manhattan street names!). LabelObstacleTest was broken > because it was setting up the fixture data

Re: [Geotools-devel] incorrect transformation with epsg hsql database

On Wed, Sep 26, 2012 at 10:10 AM, Jesse Eichar wrote: > Hi, > > I am having problems with the EPSG HSQL database. I want to transform > from EPSG:21781 to EPSG:4326. > > When I create the EPSG:21781 CRS with: CRS.decode("EPSG:21781") I get a > Geometry like: 0.935 -82.713 1.166 -82.498 ... > >

[Geotools-devel] incorrect transformation with epsg hsql database

Hi, I am having problems with the EPSG HSQL database. I want to transform from EPSG:21781 to EPSG:4326. When I create the EPSG:21781 CRS with: CRS.decode("EPSG:21781") I get a Geometry like: 0.935 -82.713 1.166 -82.498 ... When I create the Geometry with the ESRI WKT from: http://spatialrefer

[Geotools-devel] [Hudson] Build failed in Hudson: geotools-master-jdbc #102

See -- [...truncated 2494 lines...] at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.execute