Currently, there is lack of support for multilingual spatial datasets and OGC services.
Only through proprietary GIS stack (i.e. Esri), can the field names be re-aliased or held in alternate languages via scripting in order to have human-readable descriptions shown in desktop and WebGIS applications in both official languages.
There is a pain-point to not only have FOSS solutions duplicate the aforementioned in geoJSON and in turn OGC formats such as WFS - but to have non-numeric or coded cell values to contain multi-lingual selectable values to fulfil Official Language Acts requirements and have the ability for non-official language outreach.
The current workflow deployment is cumbersome since it involves collecting, maintaining, publishing, and configure more than one spatial dataset and target application for each target language. Furthermore, this method incurs major storage implications because of duplication of efforts.
Not only would PHAC benefit from exploring solutions, but re-use within the whole of government by sharing any methods would be welcomed.
⚒️ Tangible Outcomes
outreach with Open Geospatial Consortium (OGC) contributors who are within the GoC already to gain insights and recommendations how to officially proceed.
👨💻 Intangible Uutcomes
increased collaboration with other GoC agencies such as NRCAN
✔️ Feature List
[ ] [FEAT] - create a script which potentially nests multiple key:value pairs for different languages for the same metric in one field.
👱 Business Client
Nick, Zachary
🎯 Milestone
M2 - Develop Strategic Plan
🟢 Start Date (expected)
16-06-2023
🔴 End Date (expected)
16-06-2024
📋 Detailed Description
Currently, there is lack of support for multilingual spatial datasets and OGC services. Only through proprietary GIS stack (i.e. Esri), can the field names be re-aliased or held in alternate languages via scripting in order to have human-readable descriptions shown in desktop and WebGIS applications in both official languages.
There is a pain-point to not only have FOSS solutions duplicate the aforementioned in geoJSON and in turn OGC formats such as WFS - but to have non-numeric or coded cell values to contain multi-lingual selectable values to fulfil Official Language Acts requirements and have the ability for non-official language outreach.
The current workflow deployment is cumbersome since it involves collecting, maintaining, publishing, and configure more than one spatial dataset and target application for each target language. Furthermore, this method incurs major storage implications because of duplication of efforts.
Not only would PHAC benefit from exploring solutions, but re-use within the whole of government by sharing any methods would be welcomed.
⚒️ Tangible Outcomes
👨💻 Intangible Uutcomes
✔️ Feature List
⛔ Dependencies
No response