This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
NCSS Point Collections date problems #378
Comments
lesserwhirls
added a commit
to lesserwhirls/thredds
that referenced
this issue
Feb 8, 2016
Fixed Unidata#378 The update function would update the local state of the available date/time range of the dataset in the catalog, but this was not being properly checked in the request validation. Note that this will not scale well, as the validation bean checks the date/time range on the CompositePointDataset object, which only gets updated on server restart.
lesserwhirls
added a commit
to lesserwhirls/thredds
that referenced
this issue
Feb 8, 2016
Fixed Unidata#378 The update function would update the local state of the available date/time range of the dataset in the catalog, but this was not being properly checked in the request validation. Note that this essentially doubles the check of the date/time range.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When making an NCSS request against a PointFeature collection, when giving it request for newer data (since the server started up), it incorrectly says that the request does not overlap with the actual data date range. The metadata for the collection agrees properly with the data on disk.
The text was updated successfully, but these errors were encountered: