There is messy code when I open a shapefile created by arcgisdesktop, but it shows well in arcgisdesktop. I don't know why.
I hope someone can help me to solves this problem , thanks a lot.
Here is the testfile.
Question
There is messy code when I open a shapefile created by arcgisdesktop
+19- Contributor
Hi @liujisheng, it seems that you encountered the known issue that the FME Shapefile Reader/Writer always handles attribute names with system default encoding. See also here.
The situation could appear if the Shapefile dataset was created by ArcGIS with UTF-8 and the default encoding of your machine was other one (e.g. GB2312/18030 in the case of Chinese Windows).
Unfortunately there is no way to solve it unless you re-create the dataset with the same encoding as the default encoding of the machine you run FME.
Hope this will be fixed as soon as possible. @daleatsafe, @LenaAtSafe
+6- Participant
The encoding of your file is UTF-8. Unfortunately, the current FME can read the attribute value according to UTF-8 according to the cpg file, but by default, the attribute name is read in the default encoding of the OS (In your case, it should be GBK or GB2312).
Please refer to @takashi's answer. This problem has existed for a long time, but unfortunately, it seems that it has still been solved.
https://knowledge.safe.com/questions/55871/esri-shape-files-with-utf-8-encoded-field-names.html
All of them will cause garbled attribute names. To avoid this problem, I think you can try the following method.
1. Use QGIS to convert your Shape to GBK or GB2312 encoded Shape
2. Read the converted Shape with FME
+6- Participant
takashi wrote:
Hi @liujisheng, it seems that you encountered the known issue that the FME Shapefile Reader/Writer always handles attribute names with system default encoding. See also here.
The situation could appear if the Shapefile dataset was created by ArcGIS with UTF-8 and the default encoding of your machine was other one (e.g. GB2312/18030 in the case of Chinese Windows).
Unfortunately there is no way to solve it unless you re-create the dataset with the same encoding as the default encoding of the machine you run FME.
Hope this will be fixed as soon as possible. @daleatsafe, @LenaAtSafe
Oh(^.^).
I also very much hope that this issue can be resolved as soon as possible.
+17- Contributor
Hello all, This still remains a problem and sadly is a challenge for us. We're exploring some options but unfortunately you'll have to workaround for FME 2018. If you look at the last comment on this post https://www.quora.com/Why-doesnt-Microsoft-use-UTF-8-on-Windows-10 -- if you are using Windows 10 and you click that box, your problems may go away. Not 100% the solution but one that may work for you in the short term.
+17- Contributor
takashi wrote:
Hi @liujisheng, it seems that you encountered the known issue that the FME Shapefile Reader/Writer always handles attribute names with system default encoding. See also here.
The situation could appear if the Shapefile dataset was created by ArcGIS with UTF-8 and the default encoding of your machine was other one (e.g. GB2312/18030 in the case of Chinese Windows).
Unfortunately there is no way to solve it unless you re-create the dataset with the same encoding as the default encoding of the machine you run FME.
Hope this will be fixed as soon as possible. @daleatsafe, @LenaAtSafe
+17- Contributor
Sadly this is a very very tough one to win. One hopeful future is this latest Windows 10 feature. If you have Windows 10 and this update, please give that a try. In our early testing it appears to resolve issues like this. Long run we have more work to do in this area, but this new Windows 10 option does provide an alternate and robust way for FME to work well in this type of scenario.
+19- Contributor
fmelizard wrote:
Sadly this is a very very tough one to win. One hopeful future is this latest Windows 10 feature. If you have Windows 10 and this update, please give that a try. In our early testing it appears to resolve issues like this. Long run we have more work to do in this area, but this new Windows 10 option does provide an alternate and robust way for FME to work well in this type of scenario.
Just hope you understand how serious this issue is.
Reply
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.