[kepler-dev] GIS workflow and display
David Welker
david.v.welker at gmail.com
Fri Apr 3 13:42:16 PDT 2009
Hi Chris,
One thing to keep in mind is that if you develop your own module, you do
not necessarily need to convince others to upgrade to a new jar right
away. What you can do is just use the jump-1.2.jar in your new module,
and it will be used not only for any additional work you do, but by
Kepler itself. (But, people doing unrelated work that do not use your
new module will still use the jump-1.1.jar.) This should be fine as long
as version 1.2 is backwards compatible. Additionally, keep in mind that
even if version 1.2 is not completely backwards compatible, you can
override the Kepler classes that are not backwards compatible in your
module without actually touching those classes in the core module.
Ultimately, if your changes make sense, they can be merged into the core
of Kepler. But, from your perspective, you do not need to wait or engage
in any sort of complicated negotiation process to add a module that will
use Kepler with your preferred version of this jar. That is one of the
major advantages of the build system that Kepler now uses.
Let me know if you have any questions about this process.
David
> Hi,
> I am interested in developing a workflow with a GIS display.
> In the developer version from trunk, I have used the "GML Displayer" actor,
> which appears to be based on Jump 1.1.1 [util/lib/jar/jump-1.1.1.jar].
> The version documentation for Jump, shows that version 1.2
> supports displaying GeoTIFF as a layer. [1]
> Ultimately I would like to display images and points as layers.
> What can I do to assist in upgrading Kepler to support this?
>
> Chris
>
> 1. http://www.vividsolutions.com/jump/download.htm
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
>
More information about the Kepler-dev
mailing list