Gabriel,
please also update the Eclipse formatter.xml on the 2.4.x branch.
You could encourage adoption of these Eclipse formatter settings by
adding a paragraph to:
http://docs.codehaus.org/display/GEOT/5.1.1+Coding+Conventions
(or the Eclipse pages)
It would be even nicer if mvn
Jalopy configuration has out-of-date copyright header, broken keys
--
Key: GEOT-1969
URL: http://jira.codehaus.org/browse/GEOT-1969
Project: GeoTools
Issue Type: Bug
I still have no responses. Any objections?
I also propose that we adopt a *FixtureTest convention, like
*OnlineTest, to make fixtures more easily recognised. I do not propose
any changes to the build procedure at this time, so this is a relaxation
of the requirement that all
Ben Caradoc-Davies wrote:
I still have no responses. Any objections?
I think I am still waiting for a proposal.
ie A wiki page similar to the ones listed here:
- http://docs.codehaus.org/display/GEOTOOLS/Proposals
Of importance to me is:
- jira task (you got that)
- tasks with volunteer
Ben Caradoc-Davies ha scritto:
I still have no responses. Any objections?
Sorry, meant to answer, got sidetracked by other stuff.
However, I'm not really sure it should be the developer to decide
whether the server is under his control. It's usually
only the maven user that knows.
Say I want
Jody Garnett ha scritto:
It supports 3D data (indeed we wrote it for LRS data which included
measures as well as xyz). This work lead into some of the first steps
towards coordiante sequence.
You are correct that I have not optimized it at all; indeed I almost
stayed functional in my
Andrea Aime wrote:
the JDBC driver that does that part of the work, I cannot optimize it.
JGeometry seems to have a fast path that avoids the STRUCT entirely and
parses the byte[] directly instead, that's why I find it interesting.
That is great news; by all means let us try this one out :-)
Jody Garnett wrote:
I think I am still waiting for a proposal.
ie A wiki page similar to the ones listed here:
- http://docs.codehaus.org/display/GEOTOOLS/Proposals
Of importance to me is:
- jira task (you got that)
- tasks with volunteer available for each one
- api change BEFORE /
Hi all,
According to question in users list (below) - I would like to fix the Krovak
projection to be compatible with ESRI definition. Problem is that ESRI
definition is solving the axis swapping by defining the X_scale, Y_Scale and
XY_Plane_Rotation parameters like this:
JDBCDataStore should log sql statements
---
Key: GEOT-1970
URL: http://jira.codehaus.org/browse/GEOT-1970
Project: GeoTools
Issue Type: Improvement
Components: data gml
Reporter:
JDBCDataStore should not encode a WHERE clause if filter equals Filter.INCLUDE
--
Key: GEOT-1971
URL: http://jira.codehaus.org/browse/GEOT-1971
Project: GeoTools
JDBCFeatureReader should build features, not wrap result sets
-
Key: GEOT-1972
URL: http://jira.codehaus.org/browse/GEOT-1972
Project: GeoTools
Issue Type: Bug
Affects
[
http://jira.codehaus.org/browse/GEOT-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-995:
-
reopening to mark it is fixed for RC0
Reinsert/remove gt2- prefix in all module name
[
http://jira.codehaus.org/browse/GEOT-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-1953:
--
reopening to mark it fixed as per RC0
Break unsupported modules down into profiles
[
http://jira.codehaus.org/browse/GEOT-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-1905:
--
reopening to mark it fixed as per RC0
unsup/oracle-spatial needs to clarify testData.sql
[
http://jira.codehaus.org/browse/GEOT-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-1718:
--
reopening to mark it fixed as per RC0
Allow ArcSDEDataStore to edit the default version when a sde
[
http://jira.codehaus.org/browse/GEOT-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-1608:
--
reopening to mark it fixed as per RC0
Do not allow to edit ArcSDE featuretypes with no primary key
[
http://jira.codehaus.org/browse/GEOT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-1712:
--
reopening to mark it fixed as per RC0
Introduce DataAccess superclass for DataStore and generics on
[
http://jira.codehaus.org/browse/GEOT-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Roldán reopened GEOT-1792:
--
reopening to mark it fixed as per RC0
ArcGridReader can't read ArcGrid ASCII file without file
On Mon, 2008-08-25 at 10:25 -0700, Jody Garnett wrote:
I have set up a proposal here:
- http://docs.codehaus.org/display/GEOTOOLS/Move+to+another+Server
We have talked about moving to another server - the above is a proposal
to do so.
...
The proposal outlines two options: CodeHaus or
JDBCDataStore does not honor Query.getMaxFeatures()
---
Key: GEOT-1974
URL: http://jira.codehaus.org/browse/GEOT-1974
Project: GeoTools
Issue Type: Bug
Components: data h2
ContentFeatureSource does not honor coordinate system forcing
-
Key: GEOT-1975
URL: http://jira.codehaus.org/browse/GEOT-1975
Project: GeoTools
Issue Type: Bug
Hi list,
I'm leveraging on the Temporal implementations available on the temporal
unsupported module.
Today I'm comparing some DefaultInstant calling the equals method.
I have noticed that in case of different instances of DefaultInstant having
anyway the same identical position, the check returns
Andrea Aime a écrit :
I see. Yet, say I cache the results. I can use a (Class, Hints) key
for the cache, but what about being notified that a new factory
iterator has been added since the last scan? Otherwise the cache
would contain stale results, wouldn't it?
True. But there is already a
The GeoTools 2.5-RC0 release candidate is available for download:
* http://geotools.codehaus.org/2.5-RC0
The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is
centred around making a new Feature model available. The new feature model is
based on formal GeoAPI
Ciao Simone,
Thanks very much for this. Can I check that I've understood a few
things correctly?
* Do I understand correctly that you have three potential ways to read NetCDF:
- Flat plugins, no geospatial metadata (is this what GeoServer uses
right now?)
- Smart plugins, which wrap flat
Hey Gabriel,
1) I take it you fixed the distribution issues, is that right?
2) The release notes should note that much of the stuff added in the
milestones has now been removed from the distribution: e.g. new Swing
widgets, geometry as supported module, gpx datastore, jaxb annotations.
3) who
Ben Caradoc-Davies wrote:
What do I need if just adding an optional flag for fixtures? Instead
of my refactored two-class solution, I could just add a
skip.on.failure={true,false} flag to extend the functionality of
OnlineTestCase, as proposed by Andrea.
That also sounds good. In this
Adrian Custer wrote:
Hey Gabriel,
1) I take it you fixed the distribution issues, is that right?
I am not sure we did; the assembly continues to pick up everything as I
understand it.
2) The release notes should note that much of the stuff added in the
milestones has now been removed
SQLDialect.getMapping needs to provide a sql connection as well
---
Key: GEOT-1976
URL: http://jira.codehaus.org/browse/GEOT-1976
Project: GeoTools
Issue Type: Improvement
Martin Desruisseaux ha scritto:
Andrea Aime a écrit :
I see. Yet, say I cache the results. I can use a (Class, Hints) key
for the cache, but what about being notified that a new factory
iterator has been added since the last scan? Otherwise the cache
would contain stale results, wouldn't it?
The GeoTools 2.5-RC0 release candidate is available for download:
Will this version get pushed to the maven repository ?
Try here:
- http://maven.geotools.fr/repository/org/geotools/gt-api/
Thanks. Is there a reason why gt-mysql 2.5-RC0 was not released yet:
Stephen More ha scritto:
The GeoTools 2.5-RC0 release candidate is available for download:
Will this version get pushed to the maven repository ?
Try here:
- http://maven.geotools.fr/repository/org/geotools/gt-api/
Thanks. Is there a reason why gt-mysql 2.5-RC0 was not released yet:
Hi Adrian,
On Tuesday 26 August 2008 11:40:44 am Adrian Custer wrote:
Hey Gabriel,
1) I take it you fixed the distribution issues, is that right?
No, we weren't able to in time. The Readme contains a note about it:
https://sourceforge.net/project/shownotes.php?group_id=4091release_id=621379
On Tue, 2008-08-26 at 07:46 -0700, Jody Garnett wrote:
Adrian Custer wrote:
Hey Gabriel,
1) I take it you fixed the distribution issues, is that right?
I am not sure we did; the assembly continues to pick up everything as I
understand it.
Well then what happens for (2) depends on
It was our intention to deploy them to maven; but not make them
available for download. Looks like we are still having fun sorting out
the build system with respect to unsupported modules.
You may wish to confirm/deny the presence of gt-mysql in the GeoTools
2.5-RC0 download. Andrea is correct
Yes Daniele you can commit your fix but I suggest you the logical test
if (object instanceof DefaultInstant super.equals(object)) instead
the only one super.equals(object) check, sorry it was a mistake for
the equal method in many subclasses.
Thanks
Regards.
Mehdi Sidhoum
Daniele
On Tue, Aug 26, 2008 at 11:24 AM, Jody Garnett wrote:
You may wish to confirm/deny the presence of gt-mysql in the GeoTools
2.5-RC0 download. Andrea is correct about the supported status trade off.
There is no 2.5-RC0 for gt-mysql.
There is no 2.5-RC0 for gt2-mysql.
If you are able to run
Hi Mehdi,
I have just noticed your committs.
I have a doubt: I guess the equals method should also return true when
different instances of a DefaultInstant class have the same identical
position.
Using the super.equals(object) will call a Object.equals(object) checking
the reference is the same
It looks like svn / m2 etc are back up :-)
And some good news; the sys admins managed find a couple IP address (in
our service providers logs) that were responsible for the downtime.
These IP addresses are now blocked - looks like a yahoo crawler got
stuck in our server and did not know how to
Move filter capabilities from datastore factory to dialect
--
Key: GEOT-1977
URL: http://jira.codehaus.org/browse/GEOT-1977
Project: GeoTools
Issue Type: Improvement
SQLDialect encode/decode geoemtry methods need improvements
---
Key: GEOT-1978
URL: http://jira.codehaus.org/browse/GEOT-1978
Project: GeoTools
Issue Type: Improvement
JTSGeometryFactory failure to resolve GeometryFactory
-
Key: GEOT-1979
URL: http://jira.codehaus.org/browse/GEOT-1979
Project: GeoTools
Issue Type: Bug
Reporter: Jody Garnett
Hi list,
this will sound strange, but since I tend to stay in the udig life and
not to get my hands too dirty in geotools, this comes all new to me.
I followed some fighting of the coverage gods in the past. But what I
noticed only recently is that there are two separate efforts on the
coverage
andrea antonello wrote:
My impressions is that the two trails are somewhat different:
- imageio-ext seems to be dedicated to imagery and its optimization in
visualization
- coveragio seems to be more scientific and with the need to follow
strick the standards
I agree that this is a very
2008/8/27 Jody Garnett wrote:
PS. Nice western reference; I am the messenger
PPS. Don't shoot the messenger
oh, I thought it was an Elton John reference :)
-
This SF.Net email is sponsored by the Moblin Your Move
Small clarification Andrea,
You will find they are both working off the GeoAPI Grid Coverage
Exchange model (ie Format and GridCoverageReader etc...). We have tried
to update it to match the ISO Coverage model (when it became apparent
that the OGC had dropped the Grid Coverage Exchange
47 matches
Mail list logo
