Change the Encoding dropdown to “Unicode (UTF-16)”.Download and install TextWrangler if you don’t already have it.However, there is a free third party application called TextWrangler that does. Unfortunately, the built-in text editor with OSX does not properly save UTF-16 in the way SpatialKey requires.
You can use Notepad, which comes as a core application with Windows, to save the proper format. These errors can often be fixed by saving the CSV file with a specific character encoding.
If you are working with a dataset in SpatialKey and see data that either shows a square icon (Windows) or a diamond with a question mark (Mac) then there was a problem with the CSV upload. There are some manual steps you can take to ensure the best support for the full range of characters in your data. However, this doesn’t always produce perfect results. In most cases if the data looks right on your computer before uploading, it will appear correctly in SpatialKey. SpatialKey supports a wide range of languages and characters in datasets uploaded as CSV files.
