Extending existing localization system

Currently the localization of specific table columns, is performed by the lode-viewer/workaround.js script, which localizes both province names, and ODHF type names.

• In the short term this script needs to be updated to handle additional dataset specific columns.
• In the long term a system for localizing content will need to be designed.

Currently most of our viewers contain a nls config json file which is typically loaded in the entry point of an application and the file's content is assigned to the Core.nls.

I think this approach should be kept, but common localized content could be stored in the web-mapping-components library, and then if an application has new/updated content that needs localization, it can be updated during the above mentioned process. This would eliminate the need for lengthy nls config files for every viewer application, and would provide default localized content as part of the core library.