Changes between Version 11 and Version 12 of Dev/GribFormat
- Timestamp:
- May 13, 2016, 4:53:09 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Dev/GribFormat
v11 v12 3 3 4 4 Decoding GRIB files in rasdaman can be enabled by specifying `--with-grib` when configuring rasdaman. In this case the [https://software.ecmwf.int/wiki/display/GRIB/Home libgrib_api] library must be installed; this library transparently supports both GRIB 1 and 2. 5 6 == inv_grib (rasql) == 7 8 Petascope should send to rasdaman: 9 10 {{{ 11 UPDATE myCoverage AS m SET m[0:720,0:360,0:1, 0:1] ASSIGN VALUES inv_grib($1, "#messages") 12 }}} 13 14 The format of #messages is as follows: 15 16 {{{#!javascript 17 { 18 "messageDomains": [ 19 "[0:0,0:0,0:719,0:360]", 20 "[0:0,1:1,0:719,0:360]", 21 "[0:0,2:2,0:719,0:360]", 22 .. 23 ] 24 } 25 }}} 26 27 The messageDomains should be ordered to match the message order in the GRIB file. 28 29 The X/Y are required to be the last dimensions as this is efficient and simple (no need to reorder stuff further in rasdaman, besides row-major -> column major for each message). 5 30 6 31 == WCSTImport == … … 106 131 ] 107 132 }}} 108 109 == rasdaman ==110 111 Petascope should send to rasdaman:112 113 {{{114 UPDATE myCoverage AS m SET m[0:720,0:360,0:1, 0:1] ASSIGN VALUES inv_grib($1, "#messages")115 }}}116 117 #messages should be as follows:118 119 {{{#!javascript120 {121 "messageDomains": [122 "[0:0,0:0,0:719,0:360]",123 "[0:0,1:1,0:719,0:360]",124 "[0:0,2:2,0:719,0:360]",125 ..126 ]127 }128 }}}129 130 The messageDomains should be ordered to match the message order in the GRIB file.131 132 The X/Y are required to be the last dimensions as this is efficient and simple (no need to reorder stuff further in rasdaman, besides row-major -> column major for each message).