Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,777
    • Issues 1,777
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 66
    • Merge Requests 66
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #13843

Closed
Open
Opened Jan 30, 2013 by Kitware Robot@kwrobotOwner

netCDF CF reader should be more lenient on time units.

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


In order to specify a dimension as time within the netCDF CF reader, there must be a dimension variable with a units properties containing a string of a known time unit (as per the CF specification). However, that check is currently only looking for the substrings " since " or " until " expecting the units to be in the form of "<time_unit> since " or "<time_unit> until ". However, the reader should also accept strings that match a valid <time_unit>.

The CF convention defines units as anything accepted by the udunits package (http://www.unidata.ucar.edu/software/udunits/). The attached udunits.dat (a text file) should contain a complete list of all time units that should be supported.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#13843