Jody Garnett ha scritto:
> Justin Deoliveira wrote:
>> If you choose the Java 5 option, could you also please vote on whether
>> you would like to make the change to FeatureType (see note below).
>>
>> Also note that if the Java 5 route is chosen it will require that we
>> release 2.4 against java
Hi Jody,
I believe we went over this issue before but its been so long that i
dont quite remember the resolution. Basically the issue I am having is
that the SimpleFeaturePropertyAccessor checks for both the empty string
and for a target/class of Geometry.
I remember when i originally wrote the c
>>
> The Java 5 option is way better :-)
>
> I asked previously, but perhaps it was lost, about renaming
> AttributeType.getName() to AttributeType.name(). Perhaps it is a stupid
> idea, I just like representing derived quantities without java bean
> naming conventions...
I like the convent
Gah... you are correct Jody. Geotools 2.4 will not require java 5. I am
getting confused with my own milestones... Thanks for the clarification.
-Justin
Jody Garnett wrote:
> One quick question:
>
> My understanding was we would release 2.4 as it stands now, upgrade to
> Java 5 and deprecate me
Justin Deoliveira wrote:
> If you choose the Java 5 option, could you also please vote on whether
> you would like to make the change to FeatureType (see note below).
>
> Also note that if the Java 5 route is chosen it will require that we
> release 2.4 against java 5, and not just 2.5.
>
> A. Java
One quick question:
My understanding was we would release 2.4 as it stands now, upgrade to
Java 5 and deprecate methods as you indicate below for 2.5 ... is that
an option?
The concept of releasing GeoTools 2.4 with Java 5 is fine with me; I
just was not aware it was needed.
Cheers,
Jody
> Hel
Hello all,
Below you will find the two alternate plans I have come up with regard
to the api changes needed for the 2.4 feature model. Can each of those
interested who provided feedback (currently Andrea,Jody,and Martin)
please vote on the option which they prefer.
It would also be nice if those
Good stuff.
We especially need more Oracle users with your attitude!
Am curious too about the no-geometry stuff. FYI I created a special
datastore "geometryless" to handle the cases of no geometry, and X,Y or
Lat/Lon columns, which are very common in real business data. Let me
know if there
Martin I have confirmed that we do not need to be using a GeoTools 2.4
release; we are just as happy with a 2.5-M0 release.
So when to branch 2.4, and what to include in it, comes down to a
decision for Justin and yourself to consider.
Cheers,
Jody
Jody Garnett wrote:
> Martin could you let us
Yes you can perform the move; but we will need to set up a wiki page or
two to actually make it supported. Actually can you measure the coverage
- perhaps it is not even ready for supported status?
I am glad you like the "reference" datastore implementation.
Jody
> Hi,
> would it be possible to
Good call Andrea, I have listed myself as the module maintainer for main
... and will update jira to match.
The hard one is "core xml" right now assigned to david zwiers. Jesse and
myself have been patching as best we can, I would like to speak to Tim
Englich and see if he will volunteer (he ha
Because I hand waved a bit in email (I was on webmail and did not have
access to code on the weekend). I thought I should be explicit for Martin:
AbstractCachedAuthority - this is the version of
BufferedAuthorityFactory that *only* is used as super class.
> public IdentifiedObject createObje
Martin Desruisseaux wrote:
> Not really... I don't see the need for a read lock in an Entry, unless
> my modified workflow above if flawed. In my understanding, the
> ReadWriteLock is designed for objects like HashMap in a whole, note
> individual Map.Entry...
With a single write lock for the w
Martin Desruisseaux wrote:
> Cory Horner a écrit :
>> We are focusing on both concurrency *and* avoiding duplication of
>> work in the construction of the Referencing objects. The get()
>> method should block precisely because a write lock has been obtained
>> and someone is in the process of g
That sounds fine Martin; as stated earlier we have a round of
documentation slated for next week which will help us communicate better
on our side.
Incidentally doing the GeoAPI / GeoTools release really helped us last
week - thank you. One problem (that I am sure everyone has) with
GeoTools w
I have modified the proposal description to take away the focus on
performance. I am sorry that was misleading. The bullet point text is
accurate and remains in place.
Cheers,
Jody
-
This SF.net email is sponsored by DB2 Exp
Adrian Custer wrote:
> single instance of a CRS Authority (FactoryOnOracleSQL, for
> example), *we can expect* the code to slow to a crawl...
>
You are correct - mostly my text was just to provide context. The bulk
of my effort has gone into working with my customer to understan
Cory Horner a écrit :
> We are focusing on both concurrency *and* avoiding duplication of work
> in the construction of the Referencing objects. The get() method should
> block precisely because a write lock has been obtained and someone is in
> the process of generating its value.
Yes, I real
Coming to FOSS4G 2007? Help us build the FOSS4G 2007 program!
http://www.foss4g2007.org/presentations/review/
We want the attendees at the Free and Open Source Software for
Geospatial (FOSS4G) conference to help us build the program, by
providing rankings of the abstract submissions.
Go to the
Martin Desruisseaux wrote:
> I understand the sequence of "readLock()", "writeLock()", "get()" and
> "peek()"
> you described. My point is that you don't need the read lock at all for
> achieving exactly what you want to achieve, and consequently ObjectCacheEntry
> don't need to hold a ReadWrit
I don't think switching to java 5 is worth it unless it fixes all the
conflicts which it does not. So... I need to bring this email thread
back into focus. Going to start a new thread for that.
-Justin
Jody Garnett wrote:
> I just went and checked what I said - and apparently it has been too lon
Hello Jan
Jan Jezek a écrit :
> 1) From irregular MappedPositions I generate regular grid where user can
> specify
> the grid steps (for example 10 km). This grid is generated by inverse
> distance
> weighted interpolation and in next weeks I'll try another algorithms.
>
> 2) From this gr
Hi Ian and Andrea,
I wrote down my plan for using a quadtree to cache features :
http://docs.codehaus.org/display/GEOTOOLS/SoC+2007+Caching+data#SoC2007Cachingdata-ideasquadtree
Could you have a look at this ?
I implemented a stub quad tree for this purpose, based on
org.geotools.index.quadtre
Just to be honest, I have to admit that I'm not very good at communicating
myself. In the particular case of this CRS work, my plan is to wait for work
completion before to start a round of (hopefully minor) work myself, with email
before to perform significant change (if any). Right now I see s
Hi,
would it be possible to perform this move?
Property data store is becoming quite an exceptional testing
tool for Geoserver, and we would like to see it in supported
land.
Jody, what do you think?
Cheers
Andrea
-
This SF.n
Hi,
a recent mail on Geoserver devel prompted me to ask that
all inactive contributors gets removed as default targets
from Geotools modules.
For example, we have quite a bit of issues assigned to
James because he's the main module default target, this
is really bad because these issues are destin
Inconsistency in ListAttributeType
--
Key: GEOT-1371
URL: http://jira.codehaus.org/browse/GEOT-1371
Project: GeoTools
Issue Type: Bug
Components: core feature
Affects Versions: 2.3.3
Jody Garnett a écrit :
> writeLock is a more "serious" locking condition (only one is allowed
> in); by using a read lock we can capture many more threads in the "get"
> method (where many threads are allowed in once reading is available
> again). The effect is on if the map allows concurrent ac
Hi my mentors,
Sorry – this one is long.
In recent days I've played with JAI's WarpGrid transformation. I've made a
WarpGridTransform2D that extends existing WarpTranform2D and it just
encapsulates the JAI parameters and constructors into the GeoTools
transformation's
conventions. Finally I'v
29 matches
Mail list logo
