SWEREF 99 - EPSG3006 Issue #1071

Closed
Dzermin opened this Issue Sep 27, 2013 · 7 comments

Projects

None yet

2 participants

@Dzermin
Dzermin commented Sep 27, 2013

Hi,

I've tried out a SWEREF 99 WMS and have had issues displaying it correctly. Changing the reference system to the almost equivalent EPSG:32633 displays the map correctly and at the correct zoom levels and such. The only difference being the reference system. Is there an issue with this reference system?

@twpayne
Contributor
twpayne commented Sep 27, 2013

Please explain "ssues displaying it correctly" in more detail.

ol3 will be relying on Proj4js to support these projections, and so ol3 treats both reference systems exactly the same way.

What are the Proj4js definition strings that you are using?

@Dzermin
Dzermin commented Sep 27, 2013

In short using the correct reference system does not display the map at all.

Proj4js.defs["EPSG:3006"] = "+proj=utm +zone=33 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs";
Proj4js.defs["EPSG:32633"] = "+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs";

Practically the map is fine with using the EPSG:32633 considering that the Proj4Js definition is pretty much the same.

@twpayne
Contributor
twpayne commented Sep 27, 2013

Is it possible that the build of Proj4js that you are using does not contain the definition of the GRS80 ellipsoid?

@Dzermin
Dzermin commented Sep 30, 2013

I took the proj4js-compressed file from one of the OL samples. Searching through it does seem to contain a GRS80 definition. I'll try hacking my definition to use the same ellipsoid (I should have done this before...) and see what happens.

@twpayne
Contributor
twpayne commented Mar 17, 2014

Closing due to lack of response.

@twpayne twpayne closed this Mar 17, 2014
@Dzermin
Dzermin commented Mar 17, 2014

Hi, sorry for the lack of response; this issue was solved by using a newer proj4 version, i.e. probably an issue with older versions of Proj4.

@twpayne
Contributor
twpayne commented Mar 17, 2014

Thanks for the update. Glad it's fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment