Hi all,
The fix for GEOT-1021 is in. I had to post a new version of the
geoapi-2.1-M1 jar in the repository. Because it is not a snapshot
version maven will not automagically pick it up. So you will have to
manually clear the old version in your repository and then rebuild.
-Justin
--
Justin De
Jody Garnett a écrit :
> Here is the link to the file on the wiki - BUT IT LOOKS STRANGE! I do
> not remember all the mim-type stuff :-P
> - http://docs.codehaus.org/download/attachments/12235/config?version=3
They are normal; this mime-type stuff was there since the begining (but this
"config"
Jody,
The changes I made are in the Graph module--I needed a Delaunay
Triangulation class, and Ian T suggested I write one using the graph module and
commit the triangulation method in when I finished--so the location of the
failures isn't
really a surprise to me. However, I didn't change any p
Source:
http://docs.codehaus.org/pages/viewpage.action?pageId=62876
I don't know anything about goals 1 & 2.
Goal 3 seems appropriately positioned.
Prologue to the rest:
"Features" and "Coverages" ala ISO do not seem to correspond to that which
is served by a Web Feature Service / Web Coverage S
Well here is the thing - I get the a build error in these packages due
to a set up problem:
> [INFO]
>
> [INFO] Building Feature Based Graphs and Networks
> [INFO]task-segment: [clean, install]
> [INFO]
> --
Here is the page:
- http://docs.codehaus.org/display/GEOT/2.4+Using+Subversion
Here is the link to the file on the wiki - BUT IT LOOKS STRANGE! I do
not remember all the mim-type stuff :-P
- http://docs.codehaus.org/download/attachments/12235/config?version=3
Cheers,
Jody
> Well here is the thin
Thanks Jesse updated the providence review to match.
- http://wiki.osgeo.org/index.php/GeoTools_Provenance_Review#Plug-in
Cheers,
Jody
> Done
> On 13-Nov-06, at 1:39 PM, Jody Garnett wrote:
>
>> IP Review resend - as per geotools meeting. Jesse I think this one
>> needs to be fixed before we go
JAMISON CONLEY wrote:
> GAAHH!!!
>
> Sorry about that. I've committed fixes, but the build still fails.
> Instead of the original errors, it's claiming there are test failures
> even though there aren't any tests that apply to the code that I
> changed (which is probably not a good sign in it
Cory Horner wrote:
> Justin Deoliveira wrote:
>
>> H, well the whole reason for the second method is to make sure that
>> implementations do not make assumptions about what the return value
>> should look like. So all the work should really be done in
>> evaluate(Object), and then just converte
GAAHH!!!
Sorry about that. I've committed fixes, but the build still
fails. Instead of the original errors, it's claiming there are test
failures even though there aren't any tests that apply to the code that I
changed (which is probably not a good sign in itself). Ideas, anyone?Jamison Conley
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-2.3.x?log=log20061114171237
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to shar
Justin Deoliveira wrote:
>H, well the whole reason for the second method is to make sure that
>implementations do not make assumptions about what the return value
>should look like. So all the work should really be done in
>evaluate(Object), and then just converted on the fly by
>evaluate(Obje
Summary:
- Bryce is looking at Filter / Expression and the Feature Model
- Justin: can you help answer some questions, he will have more then I
can keep up with
- Simone: can you help us understand RasterSymbolizer, in particular how
it knows to call an operation to extract values; and does it us
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061114155040
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to shar
OK - you've got the conversation to the point I was making in
http://docs.codehaus.org/pages/viewpage.action?pageId=62876
now - that roadmap is just a first cut that needs to be reviewed by the
implementers, but I was trying to capture the nature of progress towards
the solution from a business
No, I think like you say I just check out the revision that matches the
date that geotools updated and create the branch from that. Once I get
ok from the geoapi developers I can get on this.
Doing some testing after I am done would be a great help!! :)
-Justin
Saul Farber wrote:
> Apparently we
Apparently we're thinking at the same speed.
Would it help you any to have .patch files to run against the 2.1-M1
branch, or is it trivial enough that you can do it by hand?
Let me know if I can help.
--saul
Justin Deoliveira wrote:
> Hi Saul,
>
> I can create the 2.1-M1 branch in geoapi and
Justin,
Just a heads up that I went and did "suggestion 2" on my own, figuring
September 15th as the 2.1-M1 cut date from the folder age in the
refractions maven repo. $ svn update -r {2006-09-15}
With just the one fix in FilterVisitor.java to the 2.1-M1 code, I cut a
local release of 2.1-M1,
Hi Saul,
I can create the 2.1-M1 branch in geoapi and apply the patch which will
fix the problem. There aren't many active geotools developers with
geoapi access ( i believe myself, jody, cory, and martin ), so if we can
call agree that we will create the branch only for this emergency fix,
then t
Jody Garnett <[EMAIL PROTECTED]> wrote on 11/13/2006 06:18:06 PM:
> Bryce L Nordgren wrote:
> > We might be able to make Coverage extend feature. We might also just
want
> > to provide a coverage implementation of the Feature interface. The
second
> > one might be more in line with the spirit
Gah!
Well, it's fairly critical mostly because I've got a *lot* of SLD
sitting around that uses != filters. And, I suppose, because this is a
non-trivial problem with the 1.5.x branch. I mean, if geoserver 1.5.x
is ever to be released while based on 2.3.x, then this problem will need
to be f
Hi Saul,
Yes, you are correct, and this interface was indeed just recently added
to geoapi. Unfortunately the fix requires a change to geoapi
FilterVisitor. Which brings us to another issue.
Geootols 2.3.x seems to build against geoapi 2.1-M1 which from what I
can tell has no tag in the geoapi re
Hey geotools wizards,
I was recently setting up some examples for some users of our new 1.5.x
based geoserver install, and came across an example that used to work,
but no longer does.
It was an SLD layer with a UserStyle with a filter like:
http://www.opengis.net/ogc";>
H, well the whole reason for the second method is to make sure that
implementations do not make assumptions about what the return value
should look like. So all the work should really be done in
evaluate(Object), and then just converted on the fly by
evaluate(Object,Class). Making the method fi
Cory Horner wrote:
> Can we lift "final" from the second evaluate method? It seems that
> some implementions may want to return different results based on the
> return type, looking like this:
>
> public Object evaluate(Object object) {
> return evaluate(object, String.class);
> }
>
> public Obj
public abstract class ExpressionAbstract implements Expression {
/** Subclass should overide, default implementation returns null */
public Object evaluate(Object object) {
return null;
}
public final Object evaluate(Object object, Class context) {
Value va
Martin Desruisseaux a écrit :
> In WorldImageWriter, at line 310 and 312, what are 'rotation1' and
> 'rotation2'?
> The variable names are 'rotation', but their value are not rotation angle...
Oh, I guess they are the 'y' and 'x' values in rotation=atan2(y,x)?
Martin
--
Simone Giannecchini a écrit :
Project ID: unknown
POM Location: C:\work\gt-2.3.x\module\pom.xml
Reason: Parse error reading POM. Reason: only whitespace content allowed before
start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1)
The pom.xml file has probably been edited with not
Hi Simone
In WorldImageWriter, at line 310 and 312, what are 'rotation1' and 'rotation2'?
The variable names are 'rotation', but their value are not rotation angle...
Martin
-
Using Tomcat but need to do more? Need
Hi guys,
I just tried to build geotools 2.3.x after an update and here is what happens:
C:\work\gt-2.3.x>mvn clean
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO] ---
On 11/13/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
> Perhaps I can be more blunt Ian,
>
> The color brewer code is not what is of interest here; what is of
> interest is functions that GeoVista uses being broken, the functions
> depended on side-effects and the ability of a feature to find it's
>
31 matches
Mail list logo
