Importing GEOJSON files downloaded from GRID3
When importing GEOJSON files downloaded from http://GRID3.org , it's important to validate the file and ensure it is error-free. This guide provides step-by-step instructions for importing these files and handling any issues that may arise.
Validating the File
Before importing the file, use a validation tool like https://geojsonlint.com to validate it. If the validation tool shows an error pointing you to the "right-hand rule," you can fix it by running the following command in your terminal:
luaCopy codegeojson-rewind < name of file.geojson > name of output file.geojson
This command will fix the issue and create a new output file. Open the output file in a text editor, copy the content, and validate again on https://geojsonlint.com. If there is an error "Line 1: old-style crs member is not recommended, this object is equivalent to the default and should be removed", remove the crs member and save the file. Run validation again to ensure the file is error-free.
Handling Coordinate Data
GRID3 GEOJSON files have three coordinates - x, y, and z - which represent longitude, latitude, and elevation, respectively. It's important to remove the elevation value (0.0) from the payload before importing, as population data cannot be imported against the elevation coordinate. Additionally, if an OU does not have coordinates, importing population data will fail. Only org units represented by polygons are supported for calculating population data.
Other Issues to Note
If there are overlaps when GRID3 geometry is requested on maps, report it as an issue to the developer. GRID3 has more coverage than the initial shape files, and there are no shape files for the zones in white.
If importing data using Earth Engine, remove the elevation value (0.0) from the payload. Note that some values for the same OUs with the same period may have either increased or decreased. If for any reason you have an OU without coordinates, importing population data will fail. This also affects the import for other OUs, especially if you are making selections based on levels. Finally, request for more specific error messages during import from the dev team.
Importing Earth Engine Data
An error may occur while trying to fetch Earth Engine data if the request payload size exceeds the limit of 10485760 bytes. If you encounter this error, you'll need to break down the data into smaller requests to avoid exceeding the payload size limit.
Always ensure that you have the most recent version of the file before importing to ensure a successful import.
This reference guide should help you import GEOJSON files from http://GRID3.org more effectively, while avoiding common errors and issues.