Hello Gerry, Thanx for your help. I am now using the 1.5 version of Geoserver and the projection is good in that version. I heard that it uses a more recent library of EPSG than 1.4 so I think the problem is already solved in the EPSG library itself.
With Regards, Wim Blanken -----Oorspronkelijk bericht----- Van: Gerry Creager [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 13 februari 2007 15:19 Aan: Wim Blanken Onderwerp: Re: [UMN_MAPSERVER-USERS] Projection problem Mapserver/Geoserver/Geotools Wim, Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252; format=flowed If you can provide some more detail on the EPSG error, I can get the=20 info fed back into EPSG for rectification. gerry Wim Blanken wrote: > Hello List, >=20 > =20 >=20 > Maybe a bit off topic but I cannot choose one simple list for this one=85= .. >=20 > =20 >=20 > The following projection problem. In the Netherlands we have a=20 > projection system that is based on double_stereographic (sterea). >=20 > In the proj list there was a flaw with the settings for the EPSG:28992=20 > code. I did not see it until I played around with google earth in=20 > combination with mapservices. >=20 > The alignment is wrong (about 80 meters north and twenty east) >=20 > I believe Jan Hartman from the Netherlands also encountered this=20 > problem. In mapserver It can easily be repaired by changing the=20 > +proj=3Dstere with +proj=3Dsterea. =20 >=20 > =20 >=20 > So the proj string becomes: >=20 > =20 >=20 > =20 >=20 > # Amersfoort / RD New >=20 > <28992> +proj=3Dsterea +lat_0=3D52.15616055555555 +lon_0=3D5.3876388888= 8889=20 > +k=3D0.999908 +x_0=3D155000 +y_0=3D463000 +ellps=3Dbessel +units=3Dm=20 > +towgs84=3D565.2369,50.0087,465.658,-0.406857330322398,0.35073267654256= 3,-1.8703473836068,4.0812=20 > +no_defs <> >=20 > =20 >=20 > =20 >=20 > But Geoserver does not use these proj settings. It uses a WKT list. Has= =20 > anybody any ideas about changing the settings below as that it is the=20 > same as the proj. string above? By changing the false easting and=20 > northing parameters I can align them reasonably good., But I think that= =20 > is not the solution. Is it? >=20 > =20 >=20 > =20 >=20 > 28992=3DPROJCS["Amersfoort / RD=20 > New",GEOGCS["Amersfoort",DATUM["Amersfoort",SPHEROID["Bessel=20 > 1841",6377397.155,299.1528128,AUTHORITY["EPSG","7004"]],AUTHORITY["EPSG= ","6289"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0= .01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4289"]],PR= OJECTION["Oblique_Stereographic"],PARAMETER["latitude_of_origin",52.15616= 055555555],PARAMETER["central_meridian",5.38763888888889],PARAMETER["scal= e_factor",0.9999079],PARAMETER["false_easting",155000],PARAMETER["false_n= orthing",463000],UNIT["metre",1,AUTHORITY["EPSG","9001"]],AUTHORITY["EPSG= ","28992"]] >=20 > =20 >=20 > =20 >=20 > Greetings, >=20 > =20 >=20 > Wim Blanken >=20 > The Netherlands >=20 --=20 Gerry Creager -- [EMAIL PROTECTED] Texas Mesonet -- AATLT, Texas A&M University=09 Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983 Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.441 / Virus Database: 268.17.37/682 - Release Date: 12-2-2007 1= 3:23
