Performance leak for timestamp to numeric coordinate conversion
|Reported by:||pcampalani||Owned by:||pcampalani|
|Keywords:||time conversion performance||Cc:||dmisev, pbaumann|
When a WCS GetCoverage requests specifies temporal subsettings with ISO8601 notation (which shall be within double-quotes), the values are converted to the proper numerical equivalent a priori, based on the temporal CRS associated with the coverage.
Currently the algorithm is based on a simple increase of time units from the origin of the t-CRS, but this can be very expensive when the temporal resolution is much smaller with respect to the origin-subset range, e.g. with Unix time CRS.
An optimal algorithm should be implemented, which flexibly adjusts to different time scales and steps.
Change History (11)
comment:6 Changed 3 years ago by pcampalani
- Cc dmisev pbaumann added
- Priority changed from major to blocker
comment:9 Changed 3 years ago by pcampalani
- Resolution set to fixed
- Status changed from accepted to closed