Hi Micheal,
1. The reason I chose not to use an array of doubles as a parameter as
an argument or return type is that what order do you pass in the
parameters is it lon, lat or lat, lon for geographics. I did consider
having getLat/getLon but that would be even more confusing.
In respect to using
Hi Paul,
I have some questions and remarks about your proposition :
1 - why do you use a setX setY method in the interface instead of
something like
Coordinate transform(Coordinate)
Coordinate inverseTransform(Coordinate)
or
double[] transform(double[])
double[] inverseTransform(double[])
I you
Paul,
This is definitely something I would like to talk to you about some
more.I've come up with a very similar interface, but one that skips
the forward and reverse methods you defined. I think we are both
reaching for the same goal.
I'm camping this weekend, but I'll try to look over your e-mai
I've come up with a very simple interface for projection algorithms. The
purpose of this is to be model neutral (not tied to JTS), as such it is
not for use by end users but instead for use in higher level libraries
that would work on JTS geometries.
public interface Projection {
void forward();
