Changes between Version 6 and Version 7 of Dev/GribFormat


Ignore:
Timestamp:
May 13, 2016, 8:34:57 AM (8 years ago)
Author:
Dimitar Misev
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Dev/GribFormat

    v6 v7  
     1== WCSTImport ==
    12WCSTImport will send this information to Petascope:
    23{{{#!xml
    … …  
    8990}}}
    9091
     92== rasdaman ==
    9193
    92 Petascope should send back to rasdaman:
     94Petascope should send to rasdaman:
    9395
    9496{{{
    95 UPDATE myCoverage AS m SET m[0:720,0:360,0:1, 0:1] ASSIGN VALUES decode($1, "{{messages}}")
     97UPDATE myCoverage AS m SET m[0:720,0:360,0:1, 0:1] ASSIGN VALUES decode($1, "#messages")
    9698}}}
    9799
    98 Messages should be as follows:
     100#messages should be as follows:
    99101
    100102{{{#!javascript
    … …  
    108110}
    109111}}}
    110 The X/Y are required to be the last dimensions as this is efficient and simple (no need to reorder anything in rasdaman.
    111112
    112113The messageDomains should be ordered to match the message order in the GRIB file.
    113114
    114115X and Y seem to be in the reverse order (like in netcdf), and it's necessary to transpose them in rasdaman, otherwise the data is rotated. So you have to consider this in petascope, the order should be Lon/Lat, not as it is Lat/Lon in the file.
     116
     117The X/Y are required to be the last dimensions as this is efficient and simple (no need to reorder anything in rasdaman.