> How can we specify irregular depth values using WCS spec?
>
> E.g.(in metres) 5,30, 50, 100, 200, 400
-5, -30, -50, -100, -200, -400
See Example 2, pg. 53, OGC 06-042 ; WMS 1.3.0
> sorry to bother with my requests ... actually I'm going to develop a new
> small project where I should
As per request in todays IRC, there are now 2 javadoc artifacts on the
sourceforge download page.
javadoc-core.zip: just modules (~10M)
javadoc-full.zip: everything (~34M)
Should we update the release procedure to make this standard practice
for releases?
-Justin
--
Justin Deoliveira
The Open
On 14-Aug-06, at 10:28 AM, Jay D. Askren wrote:
> It appears the link to "geotools-bin-2.2.0.zip" is broken. Also, it
> seems that Geotools has gone through a lot of refactoring lately. Is
> there still a lot of refactoring to be done in the near future, or are
> the apis relatively stable now?
Cory Horner wrote:
> Justin Deoliveira wrote:
>
>
>> Just following instructions, I know that every release that gets put out
>> of geotools 2.2.x, i am forced to update the version of geotools
>> referenced by geoserver. If the udig team has a magic 2.2.x going down,
>> please tell me about it.
Justin Deoliveira a écrit :
> After this, I believe the intended focus is intended to be stability,
> stability , stability. Geotools has received much criticism for its api
> changes in the past. While these efforts going on are important to the
> longevity of the project, it makes it hard to attr
Hi Jay,
Thanks, the link has been fixed.
As for api changes, there are two major development efforts on the
horizon. The first has to do with the grid coverage api, the second with
the feature model.
The grid coverage work has been completed on trunk. And I believe the
target for it is 2.3. I am
It appears the link to "geotools-bin-2.2.0.zip" is broken. Also, it
seems that Geotools has gone through a lot of refactoring lately. Is
there still a lot of refactoring to be done in the near future, or are
the apis relatively stable now? I'm wondering if I code to the current
api, will my appl
Justin Deoliveira wrote:
>Just following instructions, I know that every release that gets put out
>of geotools 2.2.x, i am forced to update the version of geotools
>referenced by geoserver. If the udig team has a magic 2.2.x going down,
>please tell me about it.
>
>
uDig also updates the versio
On Mon, 2006-14-08 at 18:18 +0200, Jody Garnett wrote:
> Justin Deoliveira wrote:
> > Just following instructions, I know that every release that gets put out
> > of geotools 2.2.x, i am forced to update the version of geotools
> > referenced by geoserver.
> Um, indeed? So when we put out a version
GeoTools 2.2.0 is now available for download!
- http://geotools.codehaus.org/2.2.0
This is the latest release in the stable Geotools development stream.
Notable improvements / bug fixes include:
- WFS client improvements
- JDBC filter processing
- Documentation QA and cleanup
- PostGIS concurrent
Justin Deoliveira wrote:
> Just following instructions, I know that every release that gets put out
> of geotools 2.2.x, i am forced to update the version of geotools
> referenced by geoserver.
Um, indeed? So when we put out a version it gets a number: 2.2.0, 2.2.1,
2.2.3. The branch is not "out"
Well as I have said I changed it to 2.2.0 and all looks well I have
reported a bug and in JIRA... but that is another issue
Kind Regards
Clint Lewis
Justin Deoliveira wrote:
> Just following instructions, I know that every release that gets put out
> of geotools 2.2.x, i am forced to update th
Just following instructions, I know that every release that gets put out
of geotools 2.2.x, i am forced to update the version of geotools
referenced by geoserver. If the udig team has a magic 2.2.x going down,
please tell me about it.
-Justin
Jody Garnett wrote:
> Justin Deoliveira wrote:
>> How
Justin Deoliveira wrote:
> How long have you been building against this version. Is it
> 2.2.x-SNAPSHOT or 2.2.x? I know had the same problem with geoserver but
> had to suck it up and keep up with version changes on the branch.
>
I think uDig was also targeting 2.2.x (aka the branch). I am not
How long have you been building against this version. Is it
2.2.x-SNAPSHOT or 2.2.x? I know had the same problem with geoserver but
had to suck it up and keep up with version changes on the branch.
-Justin
Clint Lewis wrote:
> Hi,
>
> We are running our application against version 2.2.x and ther
Note this bug only shows up as fatal when a DefaultFeatureCollection is
used to store several kinds of features, for the moment use a
java.util.List.
Jody
> Hi,
>
> I found a bug that caused some problems. Apparently the Logger is
> calling the incorrect method, it should call getLogger(String
Hi,
I found a bug that caused some problems. Apparently the Logger is
calling the incorrect method, it should call getLogger(String name)
instead of getAnonymousLogger(String resourceBundleName) since the
resouceBundle of "org.geotools.feature.collections" does not exists. I
create a JIRA issu
java.util.MissingResourceException
--
Key: GEOT-922
URL: http://jira.codehaus.org/browse/GEOT-922
Project: GeoTools
Issue Type: Bug
Components: core main
Affects Versions: 2.2.0
Repor
Hi,
We are running our application against version 2.2.x and there was a
version change to 2.2.1-SNAPSHOT and this causes a problem since our
application now will not get the latest code released.
We expected the branch version to remain at 2.2.x but it was changed to
2.2.1-SNAPSHOT.
In the s
19 matches
Mail list logo
