Opened 9 years ago
Last modified 8 years ago
#1060 closed defect
Common interface for extracting specific structures from decode files — at Version 3
Reported by: | Alex Dumitru | Owned by: | Alex Dumitru |
---|---|---|---|
Priority: | major | Milestone: | 9.3 |
Component: | conversion | Version: | development |
Keywords: | Cc: | Vlad Merticariu, Peter Baumann | |
Complexity: | Medium |
Description (last modified by )
Rasdaman should allow for a common syntax in the decode function that allows to select certain subset structures from the file (e.g. variables in NetCDF, bands in GDAL, fields in GRIB etc).
Some basic example:
select decode(mycol, "NetCDF", "variables=[myVar1, myVar2]") from mycol
Relatively common parameters:
- dataset subset: variable names, message ids, band ids: can be considered a single category. I'm not sure if GRIB's message ids belongs here actually, as we import them as a dimension rather than bands in rasdaman.
- spatial subset: lat/lon, x/y/t, etc. subsets, especially relevant for insitu
- x/y transpose: indicate if x/y should be transposed or is it not relevant (comes up in netCDF and GRIB and has a performance penalty at both decode and encode)
Any others?
Change History (3)
comment:1 by , 9 years ago
Component: | undecided → conversion |
---|---|
Milestone: | → 9.1.x |
comment:2 by , 9 years ago
Cc: | added; removed |
---|
Indeed we should try to consolidate a common interface for decode:
- dataset subset: variable names, message ids, band ids: can be considered a single category. I'm not sure if GRIB's message ids belongs here actually, as we import them as a dimension rather than bands in rasdaman.
- spatial subset: lat/lon, x/y/t, etc. subsets, especially relevant for insitu
- x/y transpose: indicate if x/y should be transposed or is it not relevant (comes up in netCDF and GRIB and has a performance penalty at both decode and encode)
Any other parameters?
comment:3 by , 9 years ago
Description: | modified (diff) |
---|---|
Milestone: | 9.1.x → 9.3 |
Note:
See TracTickets
for help on using tickets.
inv_netcdf supports specifying variable names for example, see #81