Hi,
I have updated the page about the unsupported/temporal module:
modules/unsupported/temporal none sg: daniele
dr: ok.
Assign it to me
Cheers,
Daniele
On Wed, May 13, 2009 at 10:23 AM, Michael Bedward
MapLayerEvent constructor for SELECTION_CHANGED
---
Key: GEOT-2480
URL: http://jira.codehaus.org/browse/GEOT-2480
Project: GeoTools
Issue Type: Bug
Components: core render
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1578/changes
Changes:
[mbedward] GEOT-2480
--
[...truncated 1803 lines...]
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
Running org.geotools.coverage.CategoryTest
Tests
Jody I took a deeper look to Catalog interface and I got dazed and confused.
Again I agree on having a central repository interface but a redesign is not
a matter of adding some methods.
Some thoughts
1) I am missing the clean concept of namespace handling
2) It must be possible to write
Remove deprecated GridRange implementations
Key: GEOT-2481
URL: http://jira.codehaus.org/browse/GEOT-2481
Project: GeoTools
Issue Type: Improvement
Affects Versions: 2.6-M2
Sorry my previous reply fell of the list ... here is a proposal for a
refreshed Repository interface:
public interface Repository {
/**
* Search for the DataAccess (or DataStore) providing access
* to the indicated typeName.
* p
* This lookup method is not namespace aware;
Ciao guys,
I have been putting together this proposal:
http://docs.codehaus.org/display/GEOTOOLS/GridEnvelope+subclasses+replacing+deprecated+GridRange+subclasses
to start cleaning up things in geotools coverage module. This time is
the turn of GridRange subclasses which become deprecated all of
Sounds good to me. So you do have a patch for the arcsde module? if so
please send it my way for my to test it cause I don't think your testing
included running the arcsde gce tests.
Thanks,
Gabriel
Simone Giannecchini wrote:
Ciao guys,
I have been putting together this proposal:
I do not feel I understand what this change covers ... what is this
data structure used for -
I am trying to pick up some context here; it appears as if the
replacement is 2d only? GridEnvelope2D
Are we not trying for a multiple dimensional expression of range here?
rectangle has getWidth and
While knowing very little about coverages I read over the proposal and
it looks good to me. It gets my +1.
Simone Giannecchini wrote:
Ciao guys,
I have been putting together this proposal:
Ciao Jody,
the problem is that there is not much to understand :-).
I am trying to clean up a work left halfway, triggere by an unilateral
change in geoapi.
To simplify, in the past we where using GridRange implementations then
all at a sudden I notice that they were deprecated and replaced with
I see; in general for this kind of technical debt stuff we may not
need a change proposal; especially as you are now the module
maintainer. There is nothing stratigic here right - just trying to
clean up work that was not completed.
So while I still do not feel I get it; the reference to a 2d
Well, ask away so that we can clarify.
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob:+39 333 8128928
The imagemosaic-jdbc also is influenced. But I am lucky, I have only two
references, one of them in tests.
Its ok for me.
Justin Deoliveira writes:
While knowing very little about coverages I read over the proposal and
it looks good to me. It gets my +1.
Simone Giannecchini wrote:
Ciao Christian,
you can try the patch I have sent and let me know.
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
You are right jody, nothing strategic, just clean up.
However, I think that making this change clear is quite helpful since
it impacts coverage plugins and client applications like GeoServer
(and udig as well), therefore I preferred to see if anyone had any
problems with it.
Simone.
+1
Sorry for being slow I missed the vote starting - isn't this what
geotools-admin is for?
Ian
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a
Hi Simone,
thanks for the patch.
I've applied it and everything seems to be going well. Also, the timing
is just good cause I'm starting to work over
http://jira.codehaus.org/browse/GEOS-2748, and need to check how I
compute the resulting envelope of a query.
all in all the patch works.
Hello all
Simone Giannecchini a écrit :
to start cleaning up things in geotools coverage module. This time is
the turn of GridRange subclasses which become deprecated all of a
sudden last summer with very little communication.
Just for completness for those who read the list, those classes
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1579/changes
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Ciao Martin,
nice seeing that you are still lurking on this list.
I have put the email link on purpose to show that there had been
little communication (which is different from no communication at all
as you know). Nevertheless, me, likewise the other coverage plugins
developers (gabriel,
Well it is not super important ... can you just talk me through this
second code example:
import org.geotools.coverage.grid.GeneralGridEnvelope;
GridEnvelope2D originalGridRange=...
final int w = originalGridRange.getSpan(0);
final int maxx = originalGridRange.getHigh(0)+1;
GridEnvelope2D
It probably is Ian; I had for gotten about geotools-admin due to its
lack of use; my bad.
Jody
On Fri, May 15, 2009 at 3:05 AM, Ian Turton ijtur...@gmail.com wrote:
+1
Sorry for being slow I missed the vote starting - isn't this what
geotools-admin is for?
Ian
Thanks for accepting the nomination; Welcome to the PMC - and thank
you for volunteering.
As mentioned earlier the role is not that stressful; on paper the
responsibilities are to vote on the change proposals that go through.
I am afraid to start you out with we have a proposal that is confusing
Just to follow up - Christian and I sorted out some things over IRC;
and he is reviewing a patch right now.
Jody
On Thu, May 14, 2009 at 10:52 PM, Jody Garnett jody.garn...@gmail.com wrote:
Sorry my previous reply fell of the list ... here is a proposal for a
refreshed Repository interface:
2009/5/15 Jody Garnett wrote:
Well it is not super important ... can you just talk me through this
second code example:
Like Jody, I'm also confused by the second code example...
But I've no problems with supporting the cleanup Simone - thanks.
Michael
+1, looks good to me.
Simone Giannecchini wrote:
Ciao guys,
I have been putting together this proposal:
http://docs.codehaus.org/display/GEOTOOLS/GridEnvelope+subclasses+replacing+deprecated+GridRange+subclasses
to start cleaning up things in geotools coverage module. This time is
the
Support property interpolation in app-schema mapping files
--
Key: GEOT-2482
URL: http://jira.codehaus.org/browse/GEOT-2482
Project: GeoTools
Issue Type: Improvement
Where should we put end-user documentation for app-schema applications
of GeoServer? We have bits and pieces on the seegrid twiki, but this
should me migrated either the GeoServer or GeoTools wikis.
app-schema configuration consists largely of creating a data directory,
the most tricky part of
29 matches
Mail list logo
