WCST_Import InsertCoverage with first datetime slice as bound on old recipes

[Bang Pham Huu]

For old recipes (time_series_regular, time_series_irregular) and the time values is from file name, the GML with InsertCoverage request missed the initializing bound for time axis, e.g:

request: http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=InsertCoverage&coverageRef=file:///tmp/47c5d43e_7655_4cfb_ba6b_fcbfb8de1d76.gml&tiling=ALIGNED [0:1000, 0:1000, 0:2]&pixelDataType=Byte&useId=existing


and bound from GML file:
<lowerCorner>-90.0 -180.0 0</lowerCorner>
<upperCorner>90.0 180.0 0</upperCorner>

with the General Recipe such as insert 3D coverages from 2D netCDF files, it is

http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=InsertCoverage&coverageRef=file:///tmp/3a6243f7_35b0_4320_a9fd_410372f66a47.gml&tiling=ALIGNED [0:0, 0:1023, 0:1023]&pixelDataType=Float32&useId=existing

and bound from GML file:
 <lowerCorner>"2003-01-01T00:00:00+00:00" 19.99999811100305640455682134 -169.9999988885801611558766324</lowerCorner>
 <upperCorner>"2003-01-01T00:00:00+00:00" 29.99999888899694359544317866 -160.0000011114198388441233676</upperCorner>

The initializing time value is important for new Petascope as if it is 0 and time translated from datetime to days is like: 150000 the CRScomputer will return 150000 for grid bounds. It does not have this problem with the General recipe as the first time slice was added as bound when creating coverage.