-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arki-query --sort
option doesn't sort correctly by timerange
#282
Comments
Ok, it's actually a bit more complicated than that: In general:
And this is probably the reason it ends up in the last grib. |
Ok, at the moment sorting of timeranges is mostly lexicographical sorting of the timerange type and components. From this ticket I understand it's not that useful, and that we could define a better sorting. Let's then figure out how to define a better sorting for timeranges. There are currently 4 types of timeranges:
Some, but not all of them, can be converted to Timedef. Comparison needs to be defined for any combination of all of them. A possible trategy could be to define a comparison function between timedef, then compare first everything that can map to timedef, and everything that cannot map to timedef can be sorted later lexicographically. Would that help? If so, how do we sort Timedefs? |
This sounds good, I don't know if it's feasible but to keep backward compatibility it could be added a syntax to the Another partially related aspect is that at the moment there's no way to see the
|
Trying to sort by timerange results in forecast at +0 as the last grib (it should be the first one).
Attaching a test grib (the first query can use the same grib as a source)
qualcosa.tar.gz
The text was updated successfully, but these errors were encountered: