You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In GeoSight, indicators can be of 3 types: 1) Integer, 2) Float, 3) Category. Type 1 and 2 are numbers, type 3 is string. From the dashboard view, users can download the data in Excel or GeoJSON formats:
Problem
When exporting to GeoJSON, all value in the Value column are represented as strings not numbers, thus cannot be directly used for visualization e.g. as a choropleth map in other GIS systems, e.g. in QGIS:
Similarly, when exporting to Excel, all values are formated as strings and need to be converted to number before they can be analyzed (e.g. summed).
These require from users a few additional steps, especially in GeoJSON they need to create new columns and calculate new values based on strings. This is often time consuming and may require additional skills from end users. As a result, many users cannot work effectively with data downloaded from GeoSight.
Proposed solution
When exporting to GeoJSON, if all indicators are number-based (integer or float) - export values in GeoJSON as numbers, not strings (i.e. without double quotes.
When exporting to Excel, export all number-based values as numbers, so that Excel will rezognize them as numbers
Overview
In GeoSight, indicators can be of 3 types: 1) Integer, 2) Float, 3) Category. Type 1 and 2 are numbers, type 3 is string. From the dashboard view, users can download the data in Excel or GeoJSON formats:
Problem
When exporting to GeoJSON, all value in the Value column are represented as strings not numbers, thus cannot be directly used for visualization e.g. as a choropleth map in other GIS systems, e.g. in QGIS:
{ "type": "FeatureCollection", "features": [{ "type": "Feature", "geometry": { "type": "MultiPolygon", "coordinates": [[[[44.23612530500003, 10.472074538000072], ...[44.23612530500003, 10.472074538000072]]]] }, "properties": { "ucode": "SOM_0001_0001_V1", ... "adm1_ucode": "SOM_0001_V1", "adm1_type": "Admin Level 1", "adm0_ucode": "SOM_V1", "adm0_type": "State", "IndicatorCode": "SAMPLE_IND_A", "IndicatorName": "Sample Indicator A", "Value": "69", "Date": "" } },
Note:
"Value": "69"
Similarly, when exporting to Excel, all values are formated as strings and need to be converted to number before they can be analyzed (e.g. summed).
These require from users a few additional steps, especially in GeoJSON they need to create new columns and calculate new values based on strings. This is often time consuming and may require additional skills from end users. As a result, many users cannot work effectively with data downloaded from GeoSight.
Proposed solution
See sample files exported from https://geosight.unicef.org/project/demo-geosight-project:
Demo GeoSight Project.xls
Demo GeoSight Project.json
Expected, fixed GeoJSON:
Demo GeoSight Project - numbers.json
Values are represented as numbers, and the file can be directly used in GIS tools, e.g. QGIS, for mapping:
The text was updated successfully, but these errors were encountered: