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

Status

Assignee

Andrea Aime

Reporter

Andrea Aime

Triage

None

Fix versions

Affects versions

None

Components

Priority

Medium
Configure