<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 5 6 2 2 2 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Trebuchet MS";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial Narrow";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple><!--ppd1000033-->
<div class=Section1>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>A fellow OSGeo member suggested that I move
a topic from a private e-mail discussion to this mailing list. I have been talking
with a couple of the guys from GeoTools, a couple of the guys from deegree, and
a couple of guys from OpenJUMP about a shared Java CRS library. There are a lot
of different opinions on the state of current libraries and on how to move
forward on any shared library. Despite this I think there is room to share CRS
definitions, algorithms and test cases among the different projects, and at
some point in the future (maybe a couple of years from now), to share code.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>We would like to continue discussions on the
obstacles and issues we will face in forming and maintaining a shared library
(or other shared resources) over the long run. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>I believe at the current time there are two
(2) main libraries used for CRS work in the Java communities. There is the CRS
code in GeoTools and the CRS code in deegree. I think there may also be some
personal and independent CRS libraries maintained by some well-known and active
Java GIS programmers.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>I have started a wiki page on the OSGeo wiki
to discuss collaboration on a shared Java library for CRS work. On this page I
have created a list of questions about the current implementations of these
existing CRS libraries. I think an important first step in any collaboration is
answering these questions. I have posted a link to the questions for the
deegree CRS code below:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><a
href="http://wiki.osgeo.org/wiki/Java_CRS:_Details_on_Deegree_CRS_Code">http://wiki.osgeo.org/wiki/Java_CRS:_Details_on_Deegree_CRS_Code</a><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>Over the course of the next couple of weeks
I will work on answering these questions for the deegree and GeoTools CRS code.
I’ll be reading over the Javadoc for each library and past e-mail threads
to do this. (I’ll also be annoying members of each project’s
developer mailing list.) I welcome any assistance with this research.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>After I have answered these questions for at
least the GeoTools and deegree CRS code I will try to come up with a plan for
collaboration. This plan will start out with modest goals. I’ll look
first at sharing CRS definitions, algorithms, and test cases. Then I’ll
look at sharing “neutral” utility code. In the final stages of the
plan I’ll look at refactoring common classes and/or interfaces from each
library into a shared library, with the ultimate goal on creating one shared,
low-level Java CRS library.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>I will post this plan here so others can
review and comment on it. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>I’m not sure where all of this will
lead, or if anything will come of it, but I know we can accomplish a great deal
if we can get some of the sharp minds in the different Java GIS projects
working together instead of independently.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>I know some of you want to know why we aren’t
just going to use the GeoAPI interfaces. I don’t know enough about the GeoAPI
code to say that it won’t be used. I think that will need to be part of
our research process. It would make sense to use GeoAPI as a home for common
interfaces if this is possible. I don’t want to reinvent any existing
technology. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>Landon<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'>P.S. – I have subscribed to the
MetaCRS mailing list. I will post messages there about any decisions made on
sharing “programming-language-independent” (PLI) resources like CRS
definitions or test cases.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Arial Narrow"><span style='font-size:
12.0pt;font-family:"Arial Narrow"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Trebuchet MS"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Trebuchet MS"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<BR><BR><FONT face=Arial><FONT size=1><STRONG>Warning:<BR></STRONG>Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.</FONT></FONT></body>
</html>