Proposed Syntax: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(New page: ===Proposed Syntax=== There are at least two good ideas floating around for a syntax for building the server-side function URL -- the one used by the F-TDS/GDS servers and the one used by ...) |
No edit summary |
||
| Line 11: | Line 11: | ||
For example: | For example: | ||
http://f-tds.noaa.gov/tds/dodsC/data/sst.jnl_expr_{}{native:let sst_x5= | <nowiki>http://f-tds.noaa.gov/tds/dodsC/data/sst.jnl_expr_{}{native:let sst_x5=[d=1, sst*5.0];sst_5x/(170W)(120W)RANGE/Y/(5S)(5N)RANGE[X/Y]average/}</nowiki> | ||
Revision as of 20:37, 28 September 2007
Proposed Syntax
There are at least two good ideas floating around for a syntax for building the server-side function URL -- the one used by the F-TDS/GDS servers and the one used by Ingrid. Because the Ingrid function syntax as build from scratch it doesn't carry any of the baggage of the GDS/F-TDS dependencies on GrADS and Ferret. But, since we have a lot of experience and service build on top of GDS and F-TDS we should retain those parts that make that parsing easy for those services. Therefore, we propose we adopt the following hybridization of these two.
- The native function syntax will be that of Ingrid.
- The function expression will be separated from the data URL with the string "_expr_".
- A set of {} braces will be used to list other data sources needed for the calculation. (This can be empty).
- The function specification will in the second set of curly braces using the notation from Ingrid.
- Multiple "lines" of commands will be separated by a ";"
- Native script statements can be mixed into the list of statements into the list of function command pre-pended with the string "native:".
For example:
http://f-tds.noaa.gov/tds/dodsC/data/sst.jnl_expr_{}{native:let sst_x5=[d=1, sst*5.0];sst_5x/(170W)(120W)RANGE/Y/(5S)(5N)RANGE[X/Y]average/}
