You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've downloaded SOSI files from Kartverkert and I'm trying to convert them to shp using the latest version of sosicon for Linux 64 bits.
Most of the files are encoded in ISO-8859-1, but some of them are UTF8. In this latest case if I run the tool a shape containing all of the points in the file is generated, but the extended characters in the metada are corrupted. If I reencode the file from UTF8 to ISO-8859-1 before running the tool the extended characters in metadata are OK, but the coordinates for the points are in the shape are completely wrong, they're even out of the range for numbers. No error message is displayed in either case.
I've attached a zip contaning both the SOSI files (the original, named 2019adresser_UTF8.sos and the reencoded, named 2019adresser_ISO.sos) and a corresponding folder containing the result file I get after running the tool.
I've downloaded SOSI files from Kartverkert and I'm trying to convert them to shp using the latest version of sosicon for Linux 64 bits.
Most of the files are encoded in ISO-8859-1, but some of them are UTF8. In this latest case if I run the tool a shape containing all of the points in the file is generated, but the extended characters in the metada are corrupted. If I reencode the file from UTF8 to ISO-8859-1 before running the tool the extended characters in metadata are OK, but the coordinates for the points are in the shape are completely wrong, they're even out of the range for numbers. No error message is displayed in either case.
I've attached a zip contaning both the SOSI files (the original, named 2019adresser_UTF8.sos and the reencoded, named 2019adresser_ISO.sos) and a corresponding folder containing the result file I get after running the tool.
Can you please have a look at them?
TIA
DemoFiles.zip
The text was updated successfully, but these errors were encountered: