JuliaDataCubes / JuliaDataCubes/EarthDataLab.jl

Exporting integer layer uses wrong nodata value

Open
#205 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
34
Forks
14
PR merge metrics
No merged PRs in 30d

Description

When I am exporting a cubefromshape result as a netcdf file the nodata value is -9999. This is not the value of the missing data which is typemin(Int32)+1 = -2147483647

I think, that the nodata value should be determined with help of the defaultval function.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the cubefromshape export path for NetCDF output and inspect how the missing-data value is selected, including the defaultval function. Reproduce an integer-layer export and verify that the NetCDF nodata value matches the missing-data value typemin(Int32)+1 rather than -9999.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.