[MS4W-Users] Missing EPSG:3785 Spherical mercator in 3.0 Beta 7

[Jeff McKenna]

Lars Westerlind wrote:
> The epsg file says:
> ...
> Unable to translate coordinate system EPSG:3783 into PROJ.4 format.
> #
> # Unknown
> # Unable to translate coordinate system EPSG:3784 into PROJ.4 format.
> #
> # Unknown
> # Unable to translate coordinate system EPSG:3785 into PROJ.4 format.
> #
> # Unknown
> # Unable to translate coordinate system EPSG:3786 into PROJ.4 format.
> #
> # Unknown
> # Unable to translate coordinate system EPSG:3787 into PROJ.4 format.
> #
> # Unknown
> # Unable to translate coordinate system EPSG:3788 into PROJ.4 format.
> #
> # Unknown
> ...
> 
> But when entering 
> <3785> +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0
> +y_0=0 +k=1.0 +units=m +nadgrids=@null
> Manually it works as I see it.
> 
> To me it looks as some temporary error just when the release was produced. Can anyone check if it's the same problem with other releases? MapServer is of 5.4.2 in this case, ms4w of 3.0 Beta 7.
> 
> Or, please correct me if another code than epsg:3785 is adviced.
> 
> /Lars
> 
> -----Ursprungligt meddelande-----
> Från: ms4w-users-bounces at lists.maptools.org [mailto:ms4w-users-bounces at lists.maptools.org] För Lars Westerlind
> Skickat: 06 October 2009 08:24
> Till: ms4w
> Ämne: [MS4W-Users] Missing EPSG:3785 Spherical mercator in 3.0 Beta 7
> 
> Hi,
> Yet another newbie question.
> I need to display the typical shorelines files, which apparently have
> Spherical Mercator EPSG:3785 projection. And with an entry as
> <3785> +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0
> +y_0=0 +k=1.0 +units=m +nadgrids=@null
> In the epsg everything works well.
> 
> But,
> The file does not contain this, nor EPSG codes 3763-9999 correctly. Is
> there a reason, or just a mistake when producing that version (Beta 7)?
> Or, should I use something different? 
> 
> Reason for asking is that I want to make my mapfiles compatible with
> future releases of ms4w.
> 

Hi Lars,

I've checked and this problem is not just with MS4W 3.0...I see that 
PROJ 4.7.0 was recently released, and it's epsg file doesn't have this 
problem.  So MS4W will be upgraded to use this PROJ 4.7.0 release (you 
can follow along the progress, and report testing results in the ticket 
at: http://bugzilla.maptools.org/show_bug.cgi?id=2106)

Thanks for reporting this.

-jeff

-- 
Jeff McKenna
FOSS4G Consulting and Training Services
http://www.gatewaygeomatics.com/