Hi Juergen,
We couldn’t recreate the issue. Here is our test code using v14.2.1:
using System.Globalization;
using ThinkGeo.Core;
const int SourceEpsg = 5650; // ETRS89 / UTM zone 33N (zE-N)
const int TargetEpsg = 25832; // ETRS89 / UTM zone 32N
// EPSG:5650 uses a zone-prefixed easting (33,500,000 m for zone 33).
var sourcePoint = new PointShape(33500000, 4649776);
GdalConfig.ConfigureGdal();
using var gdalConverter = new GdalProjectionConverter(SourceEpsg, TargetEpsg);
gdalConverter.Open();
var gdalPoint = gdalConverter.ConvertToExternalProjection(sourcePoint) as PointShape;
gdalConverter.Close();
var corePoint = ProjectionConverter.Convert(SourceEpsg, TargetEpsg, sourcePoint) as PointShape;
Console.WriteLine($"Source EPSG:{SourceEpsg} (E,N): {sourcePoint.X.ToString(CultureInfo.InvariantCulture)}, {sourcePoint.Y.ToString(CultureInfo.InvariantCulture)}");
Console.WriteLine($"GdalProjectionConverter -> EPSG:{TargetEpsg} (E,N): {gdalPoint?.X.ToString(CultureInfo.InvariantCulture)}, {gdalPoint?.Y.ToString(CultureInfo.InvariantCulture)}");
Console.WriteLine($"ProjectionConverter -> EPSG:{TargetEpsg} (E,N): {corePoint?.X.ToString(CultureInfo.InvariantCulture)}, {corePoint?.Y.ToString(CultureInfo.InvariantCulture)}");
the output:
which aligns well with the expected result:
So can you let me know how to recreate the issue?
And for your questions:
- there’s no known issues, nor specific requirement about epsg: 5650. Check out the changelog here: https://docs.thinkgeo.com/products/desktop-maps/changelog/ to find the projection related updates.
- I would recommend
GdalProjectionConverter, which is more up to date, if you can.
Thanks,
Ben