Yes cscs did have that problem. However the Proj4js version loads only the projection class code required based on the projection definition so you never need to worry about that. If you know beforehand what projections your app will be dealing with, you can also load the code statically.
The other option is to compress all the projection code and always load it all, but then you end up with lots of code that will never get used. The advantage of the Proj4js approach is that as long as the Proj4 initialization parameters are available somewhere (statically on disk, or in a Web Service like spatialreference.org, or a local interface to PostGIS) any projection can be handled. Mike Christopher Schmidt wrote: > On Mon, Sep 17, 2007 at 12:50:08PM -0700, Paul Ramsey wrote: > >> I like the simplicity, but having the actual math transformation code >> in the CRS object will cause huge amounts of duplication n'est pas? >> > > I have no idea. I don't transform coordinates on the client. I'm simply > putting it out there so that persons interested in such a thing can duke > it out at FOSS4G after having studied each other's proposals. > > I believe that cscs -- the prior version of Proj4js -- did, indeed, > suffer the problem you describe, but I'm not sure. > > Regards, > _______________________________________________ Users mailing list Users@openlayers.org http://openlayers.org/mailman/listinfo/users