Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [udig-devel] JGrass and uDig & DIVA-GIS

Dear Andrea,
 
I am Reinhard Simon from the International Potato Center. We are working too on an application being moved on to uDig called DIVA-GIS. Our focus is on georeferencing support, biodiversity analysis and plant/variety distribution prediction tools. I''ve, too, an interest in piping models some time down the road.
I noticed your reference to an open modeling standard. Do you think the standard is generic enough to link biodiverisity or species models with other models (climate, water,..)?
An alternative I've been reflecting about is using workflow engines - do you have any experience there or thoughts on relative merits?
 
Best regards,
 
Reinhard

________________________________

From: udig-devel-bounces@xxxxxxxxxxxxxxxxxxxxx on behalf of Antonello Andrea
Sent: Wed 1/24/2007 6:00 PM
To: User-friendly Desktop Internet GIS
Subject: Re: [udig-devel] JGrass and uDig



* [A.D. 24/01/07 07:41], jeichar@xxxxxxxxxxxxxxx <jeichar@xxxxxxxxxxxxxxx> probably wrote:
> Ok Slightly more informed now.
>
> As far as I know wednesday is a good time for me to meet.  I assume you are some
> 9 hours later than us who live on the Pacific? 

Yes, it should be 9.

> So perhaps 10:00 PST? Although
> if you would like I could get online at 7:00 PST as well.

Just to be sure I don't miss my first meeting :)

Is this ok?
Victoria (Canada - British Columbia)    Wednesday, January 31, 2007 at 10:00:00 AM      UTC-8 hours PST
Rome (Italy)    Wednesday, January 31, 2007 at 7:00:00 PM       UTC+1 hour CET

For me 7:00 PST is also ok.

> Integration into uDig should not be such a big problem.  We have carefully
> designed the catalog and Renderers for just this sort of issue.  For example I
> have added OSSIM to uDig.  The only reason we don't have public OSSIM plugins is
> because of problems getting the libraries required OSSIM to be recognized by
> eclipse (and the problem of building/obtaining all the libraries). 
>
> I will be happy to give you support in doing this.

This is good news, thanks for proposing. I'll need to have some start
help to not get stuck in the swamp too early.

> This will allow you to display the raw data.  Next you will need a style.  The
> StyleConfigurator extension point allows you to hook into uDig and define a
> style for your data.  Again you will have very few dependencies outside of your
> own library to do this.

What about the rendering? How is it done for the coverage maps?

> Finally we have an operation framework that allows operations to be run on
> objects in the uDig workbench.  They will typically be what ever object (or
> objects) selected by in a view. 

This is the most interesting for us. I've seen that taking mouse
interaction is easy and clean. However we need to have a set of command
modules that do the analises. Very important will be that they can also
be piped one after the other. Also one of our aims is to gain OpenMI compliance
(http://www.openmi.org/) for the modules. I can't understand very well
in which space those modules should reside. I'm not sure, but it doesn't
seem to me that udig has analisys tools that are out of the GIS base,
like the ones we would like to introduce.

> Obviously there are numerous details here I am skipping.

I had the feeling it all was too easy :)

> One issue we will
> encounter is that the Rendering framework will be re-designed soon.  But
> hopefully the API changes will be minimal.  The ETA for this is not certain but
> I expect it to occur just after 1.1 is released.

Alright, I was hoping to do not have to deal with the rendering system
in a first iteration, in which I would like to migrate the analysis
tools and be able to work with them (I need them for my job :)).

Andrea


>
> Jesse
>
> Quoting Antonello Andrea <andrea.antonello@xxxxxxxxx>:
>
> >
> > Hi list,
> > I'm Andrea Antonello, coordinator of JGrass.
> > For those that do not know JGrass at all, it is a GIS heavily dedicated to
> > hydrogeomorphologic issues. While it is very advanced in that field, we
> > have problems on everything regarding vectors (features) and in general
> > to keep uptodate the more generic GIS related base.
> >
> > Lots of changes are going on at the moment in the JGrass team and
> > architecture. One thought and wish of mine would be that to join the
> > uDig development and merge all the raster algorythms into it, as well as
> > everything suitable from JGrass. Following the last coverage changes in
> > geotools, I guess this should be possible and would bring positive
> > additions to both groups. Please take into consideration that this would
> > anyway mean a hughe amount of work from our side.
> > To understand if this could be in fact feasible, I would need to talk
> > to someone (or the IRC channel) about advantages and if and how this
> > could be achieved.
> >
> > Please let me first of all know if the uDig team is interested in this and to
> > who I may talk to about this issue.
> >
> > Best regards,
> > Andrea
> >
> > _______________________________________________
> > User-friendly Desktop Internet GIS (uDig)
> > http://udig.refractions.net
> > http://lists.refractions.net/mailman/listinfo/udig-devel
> >
>
>
>
>

--
____________________________________________________________________________
HydroloGIS - Environmental Safety Modelling
Siemens Str. 19 via Siemens
I-39100 Bozen - Bolzano
www.hydrologis.com

Andrea Antonello
Environmental Engineer
PhD Student at www.uniurb.it
JGrass, Free Open Source GIS www.jgrass.org
tel.     +39 0471 068065 
mobile:  +39 328 8497722
fax:     +39 36 328 8497722
email:   andrea.antonello@xxxxxxxxxxxxxx

"Let it be as much a great honour to take as to give learning,
if you want to be called wise."
Skuggsja' - The King's mirror - 1240 Reykjavik
____________________________________________________________________________
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel


<<winmail.dat>>


Back to the top