NetCDF dimension publishing always lists ranges, point values should be used instead
Description
This happens because the API is setup to allow a mix of ranges and point values, and point values get wrapped into a range to preserve type safety. Recognize ranges with min equal to max and reduce them down to single values before presentation instead
Environment
None
Activity
Andrea Aime
February 15, 2017 at 11:47 AM
Mass closing all resolved issues not modified in the last 4 weeks
This happens because the API is setup to allow a mix of ranges and point values, and point values get wrapped into a range to preserve type safety. Recognize ranges with min equal to max and reduce them down to single values before presentation instead