Andreas, Since we are still using the mapbuilder SVN for proj4js, I think it's best to use the mapbuilder JIRA for bug reports. I've added a 'proj4js' component for that so they can be assigned to that component until there is a project of it's own for projection related stuff.
For this specific issue, you should definitely be using the toWGS84 parameters but I'm not sure why it doesn't work going to 900913. The test case for it that I have going to and from WGS84 is accurate within about 5mm. However comparing Proj4 and Proj4js code now for the mercator projection, I'm seeing some differences and the the lat_ts parameter isn't supported. I'll have a look into that ASAP. Mike Andreas Hocevar wrote: > Hi, > > first of all, which is the preferred way of reporting bugs for > Proj4js? Because I do not know better, here is a bug report. > > Recently, I created the new mergeModels example in Mapbuilder trunk. > For this example, I have data in EPSG:31285. There is a proj def file > for that projection in Mapbuilder trunk, but it is not the latest > version of the proj4 definition. The latest version, which is already > online at spatialreference.org, contains +toWGS84 parameters for a > 7-parameter transformation. But if I use this new version, the > conversion to EPSG:900913 results in coordinates that are several km > shifted to south. > > This can easily be tested with the mergeModels examples, when the proj > def is updated with the transformation parameters. > > Mike, it would be great if you could investigate/fix this. > > Thanks! > Andreas. > > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
