<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16535"></HEAD>
<BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px"
id=MailContainerBody leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT color=#a70401 size=2>Martin,</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>Glad you mentioned the Albers projection,
it is one that I found had problems. I am working on my first input to you
- on Albers.</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>I agree that it would be nice if we could all
use the "same" code. One of my problems was that you do not use the
Point2D.Double for your point type. It occurred to me that we might
consider overloading to allow the code to support both point types.</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>Additionally, the current code frequently checks
to see whether the given projection support ellipsoids other than the
SPHERE. Maybe we could look at having a CRS Boolean that could be tested
to see whether the more advanced considerations associated with CRS concerns
needed to processed.</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>Although these things would make the code more
complicated it might allow for a single "library" which could support a far
wider audience.</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>If you think these ideas might be of use let me
know and we can see if we can list out some of the criteria, conditions,
requirements, etc. that we would want to address.</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>Such a beast might be a challenge to document
but it could be worth while.</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV><FONT color=#a70401 size=2>Fred</FONT></DIV>
<DIV><FONT color=#a70401 size=2></FONT> </DIV>
<DIV style="FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A
title="mailto:mtnclimb@gmail.com CTRL + Click to follow link"
href="mailto:mtnclimb@gmail.com">Martin Davis</A> </DIV>
<DIV><B>Sent:</B> Monday, May 31, 2010 10:44 PM</DIV>
<DIV><B>Cc:</B> <A
title="mailto:proj4j@lists.osgeo.org CTRL + Click to follow link"
href="mailto:proj4j@lists.osgeo.org">Proj4j Mail List</A> </DIV>
<DIV><B>Subject:</B> Re: [Proj4j] An approach to working
together</DIV></DIV></DIV>
<DIV><BR></DIV>Fred,<BR><BR>Sorry that you've found that you can't simply use
the current Proj4J<BR>codebase. Perhaps it will be worth revisiting this
decision once<BR>Proj4J has stabilized and become more proven in use. It
seems to me<BR>like there's got to much more common code than there is
differences in<BR>approach (100 complex projection classes far outways any
structural<BR>code that's been changed, I think!)<BR><BR>Anyway, your proposal
of simply sharing algorithm fixes sounds fine,<BR>and quite workable. The
core projection code should be very portable<BR>between both systems, I
expect.<BR><BR>Ideally you can provide test cases which exhibit failure cases
(and<BR>prove that the bug has been fixed). I will add these to the
Proj4j<BR>test suite whereever possible - this is very important to
allow<BR>regression testing going forward.<BR><BR>I don't think there are any
projections which should be ignored. I<BR>seem to recall that there's some
strange issues around the<BR>OrthographicAzimuthalProjection - perhaps to do
with it being out of<BR>synch with the original Proj4 code. But it would
be nice to have this<BR>tested and fixed as needed.<BR><BR>I don't rule out
interest in projections with no inverse and<BR>sphere-only projections.
Probably some comparison should be done with<BR>PROJ4, CSMAP and GeoTools to see
if they are provided there. It would<BR>be nice to support any and all
projections, but priority must be given<BR>to code which will be most likely to
be used.<BR><BR>Look forward to the first round of bug fixes!<BR><BR>You might
have a look at Albers - I think I fixed a bug or two in
there.<BR><BR>Martin<BR><BR><BR>On Mon, May 31, 2010 at 6:42 PM, Fred
Pospeschil<BR><<A
href="mailto:f.w.pospeschil.t.r@charter.net">f.w.pospeschil.t.r@charter.net</A>>
wrote:<BR>> Martin,<BR>><BR>> In looking over our previous emails it
appears that the overall approach you<BR>> need for your CRS work is
considerably different than what I need for my<BR>> project. However,
we both need properly functioning projection code. Given<BR>> that
thought, I tried to bring your code into my GUI test environment.
That<BR>> turned out to be a fools errand due to the way your CRS needs have
caused<BR>> considerable/significant changes to most all of Jerry's
files. Working<BR>> with, or around, these changes appears to require
more work than it is<BR>> worth.<BR>><BR>> Thus, I propose the
following approach to cleaning up Jerry's projection<BR>>
files.<BR>><BR>> On a projection file by projection file basis, I
will send you the results<BR>> of my testing and any fixes I have been able
to make. When I have made<BR>> changes to Jerry's projection file I
will attach a copy of the file.<BR>><BR>> You will do whatever you can to
resolve the error condition/conditions and<BR>> attempt to verify the
correctness of my changes. I would like your fixes to<BR>> be applied
to the file I send you and you return to me. However, I can work<BR>>
with the corrections as they exist in your file - which you will forward
to<BR>> me.<BR>><BR>> Similarly, if your testing reveals errors you
will let me know of the errors<BR>> and any fixes you
develop.<BR>><BR>> Any fixes you send will be re-tested in my GUI
environment and the results<BR>> forwarded to you.<BR>><BR>> Are there
any projections in which you have no interest and I should
ignore?<BR>><BR>> Are you interested in projections which do no have an
inverse capability?<BR>><BR>> Are you interested in projections which
support only the SPHERE ellipsoid -<BR>> if you can call it
that?<BR>><BR>> Let me know if there is anything here that works for
you.<BR>><BR>> Fred<BR>><BR>><BR>><BR>>
_______________________________________________<BR>> Proj4j mailing
list<BR>> <A
href="mailto:Proj4j@lists.osgeo.org">Proj4j@lists.osgeo.org</A><BR>> <A
href="http://lists.osgeo.org/mailman/listinfo/proj4j">http://lists.osgeo.org/mailman/listinfo/proj4j</A><BR>><BR>><BR>_______________________________________________<BR>Proj4j
mailing list<BR><A
href="mailto:Proj4j@lists.osgeo.org">Proj4j@lists.osgeo.org</A><BR><A
href="http://lists.osgeo.org/mailman/listinfo/proj4j">http://lists.osgeo.org/mailman/listinfo/proj4j</A></BODY></HTML>