You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
EDDTableAggregateRows range for time is not the min/max of all the child.
Also other variables, like latitude and longitude have this problem.
Some variables are not affected by this problem and the min/max value is calculated from all the child
To Reproduce
Create a "EDDTableAggregateRows" datasets with two (or more) child of type ""EDDTableFromErddap"
Time of the first datasets must be different from the other. As an example, first child has time from 2013-01-01 to 2020-03-31 and the second one has data from 2024-01-01 to today
The "EDDTableAggregateRows" time will be from 2013-01-01 to 2020-03-31
Hi!
I've (probably) found the problem in the code for the time variable in the EDVTimeStamp class.
I'll make some test and if all is fine I'll make a pull request with the changes.
I'm still working on the same problem for latitude, longitude and depth variables.
Hi @ChrisJohnNOAA, the bug fix is ready.
Sadly I've trouble running the tests. I've changed only EDDTableAggregateRows.java class, but the tests fail for EDVTimeStampTests. I think this is something related to the language settings of my pc.
Is it fine to make a pull request without a succesful test?
Yeah, go ahead and make the pull request. I'm aware that some tests can fail on other machines and have been trying to find and fix those to make them more reliable.
Describe the bug
EDDTableAggregateRows range for time is not the min/max of all the child.
Also other variables, like latitude and longitude have this problem.
Some variables are not affected by this problem and the min/max value is calculated from all the child
To Reproduce
With real data, if you create this dataset:
https://er1webapps.emodnet-physics.eu/erddap/tabledap/TS_SLEV_TAD_15 time is 2013-06-07T09:00:00Z to 2013-06-13T09:57:15Z
https://er1webapps.emodnet-physics.eu/erddap/tabledap/TS_SLEV_TAD_800 time is 2022-09-01T00:03:00Z to 2023-12-19T11:03:00Z
The EDDTableAggregateRows TS_SLEV_TAD time is 2013-06-07T09:00:00Z to 2013-06-13T09:57:15Z (instead of 2013-06-07T09:00:00Z to 2023-12-19T11:03:00Z)
Same problem with latitude and longitude.
Other variable (like SLEV) min/max are calculated in the right way.
Expected behavior
time range, latitude and longitude of the EDDTableAggregateRows dataset to be the min / max of all the child datasets
Screenshots
not applicable
Server
I'm using ERDDAP Version 2.23 in a docker container using axiom/docker-erddap:2.23-jdk17-openjdk image
Desktop (please complete the following information):
Additional context
None
The text was updated successfully, but these errors were encountered: