Hi there,
In the latest stable release 13.0.0 an error with EPSG:28992 is RE-introduced.
We have had this issue a long time ago and it was fixed.
How is it possible the problem is back now? All my layers are out of location with this new version.
Please fix asap !!
So far I used 13.0.0-beta426
Kind regards,
Guido van den Boom
FYI the correct conversion string is:
+proj=sterea +lat_0=52.15616055555555 +lon_0=5.38763888888889 +k=0.9999079 +x_0=155000 +y_0=463000 +ellps=bessel +towgs84=565.417,50.3319,465.552,-0.398957,0.343988,-1.8774,4.0725 +units=m +no_defs
Hey @G_Vandenboom,
When we released v13, we updated our EPSG list according to https://epsg.io/. On their site, I see that EPSG:28992 was last updated in 2020 and is slightly different from yours. Can I ask where your source is from so that we can update our reference point to the latest?
Thanks,
Kyle
Hey @Kyle_Day,
We actually got it from ThinkGeo about a year ago in ticket 20289.
Seems like espg.io messed up. I don’t know why they updated.
If it ain’t broken, don’t fix it !!
I have already send them an e-mail.
Can you fix it for now and maybe try and help me to convince espg.io has the wrong proj.string.
Kind regards,
Guido van den Boom
Hey @G_Vandenboom,
I’ve updated the proj4string in our beta branch. It should be available on nuget either later tonight or tomorrow for you to test out. I’ll see what I can do about getting espg.io to update on their side as well so we don’t keep running into this issue.
Thanks,
Kyle
