ThinkGeo.com    |     Documentation    |     Premium Support

Projection.ConvertWktToProjString does not work with other than English as CurrentCulture

#1

Hi all,

We have a problematic jpg prj combination with which the call to Projection.ConvertWktToProjString gives a false projection string when using other than English as CurrentCulture.

For example with Finnish culture the returned projString will have commas as latitude decimal delimeters which in my understanding is false format for a projection string. At least it will be shown in wrong place on map.

Here are the differing outputs:
English culture:
"+proj=lcc +lat_1=59.3333333333333 +lat_2=58 +lat_0=57.5175539305556 +lon_0=24 +x_0=500000 +y_0=6375000 +ellps=GRS80 +towgs84=0.0,0.0,0.0,0.0,0.0,0.0,0.0 +units=m +no_defs "
Finnish culture:
"+proj=lcc +lat_1=59,3333333333333 +lat_2=58 +lat_0=57,5175539305556 +lon_0=24 +x_0=500000 +y_0=6375000 +ellps=GRS80 +towgs84=0.0,0.0,0.0,0.0,0.0,0.0,0.0 +units=m +no_defs "

We are using ThinkGeo.Core 13.0.0-Beta335.
Any help is appreciated.

Regards,
Jarno

1 Like
#2

Hey @Jarno_Kalliomaki,

Yeah, I am able to recreate this issue. I pushed an update to our beta packages which will be available on nuget within then next 24 hours. You’ll need to update to the latest version of those packages in order to receive the update.

Thanks,
Kyle

1 Like
#3

Hi @Kyle_Day,

Excellent! We’ll take a look. Our workaround was starting to be a bit tedious. :slightly_smiling_face:

Thanks,
Jarno

#4

Hey @Jarno_Kalliomaki,

Sounds good. Let us know if you run into any issues. The package is up on Nuget now so make sure you get ThinkGeo.Core v13.1.0-beta004 to have those changes.

Thanks,
Kyle

#5

Hi Kyle,

Was just upgrading to latest ThinkGeo packages and can confirm this has been fixed. Thanks, and sorry it took so long.

Regards,
Jarno

#6

Thanks for confirming this Jarno. Good luck and let us know if you have any other questions.

Thanks,
John