Why GCTP in Proj4js?

2 messages Options
Embed this post
Permalink
Martin Davis

Why GCTP in Proj4js?

Reply Threaded More More options
Print post
Permalink
Proj4js appears to have some projection algorithms taken from GCTP,
rather than PROJ4.  I'm curious about the reason for this.  Are they
more accurate?  Or easier to port or maintain?

--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs
Mike Adair

Re: Why GCTP in Proj4js?

Reply Threaded More More options
Print post
Permalink
It is simply for historical reasons: the initial implementation of the
forward/inverse methods from the MapBuilder project used the GCTPC code
as a base because it was easier to port.  In theory they should give the
same result but I've converted one or two of those to the PROJ4 code
base because they had different algorithms for spherical/elliptical
spheroids.

Mike

Martin Davis wrote:
> Proj4js appears to have some projection algorithms taken from GCTP,
> rather than PROJ4.  I'm curious about the reason for this.  Are they
> more accurate?  Or easier to port or maintain?
>

--
   Michael Adair
   Senior Software Architect
   DM Solutions Group Inc.

   Office: (613) 565-5056 x26
   [hidden email]
   http://www.dmsolutions.ca
   http://research.dmsolutions.ca


_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs