I have noticed in Godiva3 (via TDS5) that the calendar utility does not limit the selectable temporal bounds to those of the dataset being viewed, like was done in TDS4/Godiva2. For example, our "tide_mhi" Hawaii tide model dataset is only available from 2023-12-01T00:00:00Z through 2024-12-31T23:00:00Z:
The Godiva3 viewer, however, will allow you to select years and months before and after this time range. For a new user, it becomes a fishing expedition trying to figure out how far back a dataset goes (how far in the future a forecast goes). Unavailable dates are only signaled by the grayed-out and italicized calendar dates.
In contrast, the Godiva2 viewer (via TDS4) was smarter about limiting the year, month, and hour pull-down menus to within the dataset's available temporal coverage:
This made it much simpler for a user to explore the available time range. Could these smarts be added back into Godiva3, I wonder? Thanks for giving this some thought!
I have noticed in Godiva3 (via TDS5) that the calendar utility does not limit the selectable temporal bounds to those of the dataset being viewed, like was done in TDS4/Godiva2. For example, our "tide_mhi" Hawaii tide model dataset is only available from 2023-12-01T00:00:00Z through 2024-12-31T23:00:00Z:
The Godiva3 viewer, however, will allow you to select years and months before and after this time range. For a new user, it becomes a fishing expedition trying to figure out how far back a dataset goes (how far in the future a forecast goes). Unavailable dates are only signaled by the grayed-out and italicized calendar dates.
In contrast, the Godiva2 viewer (via TDS4) was smarter about limiting the year, month, and hour pull-down menus to within the dataset's available temporal coverage:
This made it much simpler for a user to explore the available time range. Could these smarts be added back into Godiva3, I wonder? Thanks for giving this some thought!