|
From: Mike A. <ma...@dm...> - 2007-09-27 23:16:41
|
Ricahrd, Thanks for the summary. I'd like to settle on the name before I commit any more code for this, how about cs4js or Coords4js? I'm also not too stuck on 'Proj4js', I would just prefer something other than cscs. We also discussed the best way to load the projection class code, dynamically or not, and don't think we came to any conclusions except we can try experimenting some more. We also discussed the work left to do, including using the full proj4 def string, rather than the subset it was using previously. Some more comments below. Mike Richard Greenwood wrote: > Mike and I met Tuesday and discussed the project. Below is a summary. > > Things that I think Mike and I have an agreement on: > 1. Give it its own name space (once we pick a name). > 2. A single transform function in the form of: > transform(source_cs, destination_cs, point) > 3. Object constructor in the form of: > new cs(EPSG_code | Proj4_string) > It might be tricky to distinguish the epsg code from the proj4 definition string, so I would prefer to keep the constructor simple and just use a code here, for lookup on disk or the web database. > constructor will look for definition files locally and from spatialref.org > 4. Library should be able to run w/o a server or Internet connection. > > To decide: > 1. Project name. I'm not stuck on "cscs" but I would like a name that > reflects coordinate systems and is not limited to projections. > 2. Move the library out of MapBuilder. I'd like to see it move into > Proj4 and pr...@li.... > Or perhaps we can use the OSGeo infrastructure for svn, trac, and mailling lists? > Mike, please add your comments. > > Rich > > |