Mark Presling wrote:
Thankyou so much for getting that into 2.2.x! Now I have a question for
the GeoServer people specifically...
I am currently using GeoServer 1.3.1. Therefore, I will need to upgrade.
Here are my questions about this:
1. Is the upgrade path from 1.3.1 to 1.3.3 likely to ca
[ http://jira.codehaus.org/browse/GEOT-821?page=all ]
Chris Holmes reopened GEOT-821:
---
just reopening to attach a jar.
> FilterFilter loses characters content
> -
>
> Key: GEOT-821
>
Thankyou so much for getting that into 2.2.x! Now I have a question for
the GeoServer people specifically...
I am currently using GeoServer 1.3.1. Therefore, I will need to upgrade.
Here are my questions about this:
1. Is the upgrade path from 1.3.1 to 1.3.3 likely to cause me any grief
on the
Maybe I'm just being pedantic, but it seems to me that we are missing
the point a little here.
Axis order appears in serialisations of coordinate tuples, triples etc.
So, the three places where it may occur are :
a) in the source data
b) in the serialised input/output (eg GML)
c) in the interna
Hey folks,
The 2.2.x branch appears to be broken, so in order to keep it alive, i'm
kicking out ext/go and ext/mappane from the build (in ext/pom.xml).
Please go forth and fix these :)
for ext/go:
[INFO] Compilation failure
c:\java\geotools\2.2.x\ext\go\src\org\geotools\geometry\array\Compres
The Geotools axis order policy appears to be:
in 2.2 and earlier, the order of coordinates One and Two is
long/lat
Users are expected to transform their data to fit
in 2.3 and later, the order of coordinates follows the crs
U
and the final part in which simboss suggests it would be better to port
the in-house apps (geoserver/udig) to sort out the bugs and acuster
suggests we release and fix bugs as we port apps.
simboss, you ought to figure out what you are going to need
for 2.3
and see if we can't grab what you need
After the meeting Andrea, Adrian and Simone said:
(22:01:34) *aaime:* Sorry, what is the issue about the javadocs?
(22:02:52) *acuster:* there are two
(22:03:20) *acuster:* one for 2.2.0 is to make sure that the Geotools
javadocs point into GeoAPI 2.0 and not 2.1 (which was the case in the
last
Hi David,
It is an alternative to whats there, biggest differnt is the use of the
eclipse schema modelling library (XSD). However the two technologies
accomplish the same goal.
The end goal for the time being is to support parsing filter 1.1 and
gml3. Not sure if this conflicts with any of jes
A sloppy weekly meeting:
1) Nothing said against YourKit
2) 2.2.0 good to go (except it doesn't compile right at this instant)
3) 2.2.0 still scheduled to go out after rgould's exams (unless you
decide to release before)
4) WFS will be made permissive to incorrect requrests (but with some
mumbling
Hi all,
Some of you might be aware of the xml parsing work that has been going
on over the last while. It was used last year as part of ows-3, and
intended to be used this year in ows-4.
At the moment the code is off on a udig branch, i would like create a
new module ( or an ext ) for it on ge
Chris, Mark:
I've applied the patch to 2.2.x and trunk, and added a test case to ensure
the characters(char[], int, int) method contract is respected (not loosing
content).
don't know if Mark is building from source, in any case he would need a
gt-main jar to get it working.
Cheers,
Gabriel.
So this has been going through Jira but I am not sure that is sufficient
- http://jira.codehaus.org/browse/GEOT-902
Andrea, can we work through these problems before doing anything on
trunk with JMapPane?
> Futher Cleanup:
> ---
> There is still some minor cleanup to be done,
+1
Ian Turton wrote:
Geovista studio has just adopted Yourkit as our profiler of choice so
I'm +1 on this as it will help us out a lot.
Ian
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;377 Br
indeed,
http://jira.codehaus.org/browse/GEOT-821
going to apply the patch to 2.2.x and trunk right now.
Gabriel
On Monday 31 July 2006 17:59, Chris Holmes wrote:
> I think it may actually have to do with the limitations of the SAX
> parser, but I thought we had a workaround for it. Like it'll o
Guys,
I'm gonna miss the meeting again... sorry.
Family dinners, too many celebrations these days (anniversaries and the like).
Anyway, I do have some open questions on the ml. If you can discuss them,
I'll pick up from the irc logs tomorrow :-)
Cheers
Andrea
--
I think it may actually have to do with the limitations of the SAX
parser, but I thought we had a workaround for it. Like it'll only chunk
a certain number of characters at once.
Gabriel, I feel like you may have had this bug and/or a fix for it? I
know someone did. Maybe it didn't get port
Geovista studio has just adopted Yourkit as our profiler of choice so
I'm +1 on this as it will help us out a lot.
Ian
--
Ian Turton
http://www.geotools.org
http://pennspace.blogspot.com/
-
Take Surveys. Earn Cash. Influenc
>
> Ian,
> I've pasted most of your MapViewer.java code into the demo/introduction
> on which I am working. Therefore, I would need your go ahead to change
> this file into the public domain.
>
No problem
Ian
--
Ian Turton
http://www.geotools.org
http://pennspace.blogspot.com/
Ian Turton ha scritto:
> On 7/31/06, Andrea Aime <[EMAIL PROTECTED]> wrote:
>> Ian Turton ha scritto:
>>
>> >>
>> > That would be fine. The filter stuff is still work in progress but I
>> > think the ability to do highlighting and selection is useful.
>>
>> Good. What surprises me a little is that
On 7/31/06, Andrea Aime <[EMAIL PROTECTED]> wrote:
> Ian Turton ha scritto:
>
> >>
> > That would be fine. The filter stuff is still work in progress but I
> > think the ability to do highlighting and selection is useful.
>
> Good. What surprises me a little is that apparently there's a full set of
Ian Turton ha scritto:
> On 7/31/06, Andrea Aime <[EMAIL PROTECTED]> wrote:
>> Hi Ian,
>> yesterday I did add mappane to ext and made it compile against trunk.
>> I was wondering if I can hack on it a little...
>> What I would like to do is:
>> * apply a patch to make it handle properly non standar
On 7/31/06, Andrea Aime <[EMAIL PROTECTED]> wrote:
> Hi Ian,
> yesterday I did add mappane to ext and made it compile against trunk.
> I was wondering if I can hack on it a little...
> What I would like to do is:
> * apply a patch to make it handle properly non standard axis orientations
>(some
Hi Mark,In eclipse when you run uDig you can set tracing on and make sure that tracing for the WFS plugin is checked and the request will be printed to the uDig console. That should give an indication of whether the problem is caused by the client or the server.JesseOn 30-Jul-06, at 7:46 PM, Mark
Hi Ian,
yesterday I did add mappane to ext and made it compile against trunk.
I was wondering if I can hack on it a little...
What I would like to do is:
* apply a patch to make it handle properly non standard axis orientations
(something I already done in the coverage_branch, not sure it has
Simone Giannecchini ha scritto:
> I don't want to be tedious but I think that before saying +1 we should
> probably ask all active developers if they have any similar software
> to suggest and probably write a couple of lines saying why that
> software is so good :-) (I'd do the same for YourKit).
Thanks Luca ;-) Your response was exactly what I needed :-)
I will update the review.txt file and we will mark you down for three
gold stars on the module matrix page ;-)
- http://docs.codehaus.org/display/GEOTOOLS/Module+Matrix
(the star system is outlined at the end of the page)
You will find
Everything seems pretty clear .. two files were marked (C) 2005 Institut
de Recherche pour le Développement but that was about it.
Jody
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay pa
Adrian Custer wrote:
> Hey Ian and all,
>
> By placing all demo/ files in the public domain, we would provide
> Geotools users with files from which they could start, regardless of
> their ultimate aims with the library.
>
Understood, not really for or against it, I would not mind the feedback
On Mon, 2006-07-31 at 11:15 +0200, Simone Giannecchini wrote:
> I don't want to be tedious but I think that before saying +1 we should
> probably ask all active developers if they have any similar software
> to suggest and probably write a couple of lines saying why that
> software is so good :-) (
>> Which class is deprecated? The deprecation was removed as far as I know
>> (it was added when I thought the Feature Model was
>> straightened out for GeoTools 2.1, but I could not make sense of the
>> alternative so the deprecation should of been removed).
>>
> ==> The deprecation is in
Hey Ian and all,
By placing all demo/ files in the public domain, we would provide
Geotools users with files from which they could start, regardless of
their ultimate aims with the library.
(1) None of these files are part of the library, but merely examples of
how to use the library. Therefore
>On 7/30/06, Andrea Aime <[EMAIL PROTECTED]> wrote:
> Hi all,
> I'd like to apply for a YourKit profiler license for Geotools, but they do
> ask for their logo to be put on our home page.
> That's something I can't decide about myself, I only can tell yourkit as
> a profiler is
> much more comforta
Thanks for the clarifications jody.
On Mon, 2006-07-31 at 11:05 +0200, Jody Garnett wrote:
> Adrian Custer wrote:
> > The approach seems to have two branches, via FeatureTypeFactory
> > or via FeatureTypeBuilder but neither seems complete.
> >
> > AttributeTypeFa
Adrian Custer wrote:
> Hey all,
>
> Making Features is a mess in 2.2.x ; I'd like to resolve this.
>
>
> >From the Javadocs, both GeoAPI and Geotools appear to provide approaches
> to building Features but both are problematic.
>
> 1) Does the GeoAPI approach even work?
>
No - there is
Andrea Aime wrote:
> Hi all,
> I'd like to apply for a YourKit profiler license for Geotools, but they do
> ask for their logo to be put on our home page.
>
That is not a problem, we already have a small stable of glyphs. Before
you leap though please check with codehaus, they may already
have
Hello Mr. Askren,
Glad you are using free software! I'm unsure if you received any reply
to your posting so here's a status report.
You are right that we lost all the gui code in the early release
candidates of 2.2. However, we have just added back a very simple GUI
which should clarify how thin
Adrian Custer wrote:
> Thanks Andrea,
> FeatureTypes... did indeed clean up the deprecation.
>
> To everyone,
> We need to have a meta discussion about factories, not just for
> features but to bring the referencing factories inline and have a
> standard policy.
I have had this discussion, and
Thanks for getting back to me Jean:
I have had to drop JScience from my application (which made me sad as it
was exactly what was looking for to minimize risk). I have looked into
retro weaver before but it did not look like
a sensible solution for the GeoAPI / GeoTools relationship - but perhap
Jody Garnett ha scritto:
> Morning Chris,
>
> Contacting you about the MySQL datastore, some files were missing
> headers but everything seems in order. If you can confirm when the
> module was created that would be cool. I usually try to provide some
> module history in terms of what was made
Morning Chris,
Contacting you about the MySQL datastore, some files were missing
headers but everything seems in order. If you can confirm when the
module was created that would be cool. I usually try to provide some
module history in terms of what was made available for each geotools
version
Justin Deoliveira ha scritto:
> Jody and I spent a lot of time coming up with this api on FM as andrea
> stated. In the process came up with some decent guidelines as to what a
> factory should do vs a builder.
>
> However with FM having no path to trunk this doesn't help us much.
Hum, can you
42 matches
Mail list logo
