Decode CSV header row field names so that they correctly validate

jwalgran commented 7 years ago

The CSV reader encodes non-ASCII characters as UTF-8, which was causing the header row field validation to fail. Decoding the CSV field names before comparing them to the field names stored in the database resolves the issue.

Testing

Create a new instance centered on Los Angeles
Add a new text custom field to Tree named Localização
Import this CSV that includes a Tree: Localização column: import-with-unicode.csv.zip

The the file should validate successfully and trees added to the map should have values in the Localização field.

Connects to https://github.com/OpenTreeMap/otm-addons/issues/1467

coveralls commented 7 years ago

Coverage remained the same at 83.844% when pulling f603e39d1515976d6a3dd15d0501ff7b2202b4ee on jwalgran:feature/import-unicode-headers into 0cabbd4cdf64a93186cd77ddbc08bb632a614cac on OpenTreeMap:develop.

dboyer commented 7 years ago

Fields with symbols are not displaying correctly in Excel. No need to fix that now.

OpenTreeMap / otm-core

Decode CSV header row field names so that they correctly validate #3219

Testing