Page History

...

• cdi_get_metadata and bbox_get_metadata are meant to inquire which odv files are available at the server. *_get_metadata returns a json object with 6 columns: EDMO_code for the institute where the data originate, LOCAL_CDI_ID for the unique local identifier at the data centre and filename for the file name. The files are stored at the server using the convention $DATAROOT$/<EDMO_code>/<filename>.txt. cdi_get_metadata also returns 3 meta-data columns: the meta-data time and location (lon,lat).
  *_get_metadata returns the table in efficient json format for fast machine processing.

  Code Block
  http://localhost/cgi-bin/pywps.cgi?service=wps&request=Execute&Identifier=cdi_get_metadata&DataInputs=[]l&version=1.0.0

  A working example on our test server is (note this url may be dysfunctional now and then, as it is a test server)http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=odvGetCDI&cdi_get_metadata=\[\]&version=1.0.0]}}

• cdi_get_parameters and bbox_get_parameters are meant to inquire one file/database to find which variables are actually available in that file/database (the file should be one of the ones returned by cdi_get_metadata). The functions return a json object (fast for machine processing) with the P01 quantity code in sdn_name, the P06 units in sdn_units and the column name in column_name. The column_name has to be used in the subsequent plotting processes, it is equal to (i) the sdn_code for data columns, (ii) 'QV:" + sdn_code for flag columns and (iii) the standardized odv column name for the first 8 meta-data columns.

  Code Block
  http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=cdi_get_parameters&DataInputs=[EDMO_code=632;LOCAL_CDI_ID=world_N50W10N40E0;suffix=_20060101_20070101]&version=1.0.0

  A working example on our test server is (note this url may be dysfunctional now and then, as it is a test server)
  http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=cdi_get_parameters&DataInputs=\[EDMO_code=630;LOCAL_CDI_ID=CTDCAST_79___42;filename=CTDCAST_79___42_20110223_120553\]&version=1.0.0

The remaining WPS wrappers for plotting one odv file/folder have the same name as the associated pydov functions. They have

• common parameters names for specifying a plot:
  • either the boudning box (for PostgreSQL/PostGIS backend only) or EDMO_code, LOCAL_CDI_ID and filename to select a specific odv file
  • parameter for the column
  • clim0, clim1 for the (x/y/color) axis limits of the chosen parameter
  • log10 for plotting the parameter on log scale.
• specific parameter which differ per function:
  • box_plot_map and cdi_plot_map to be applied to one available column from a remote odv file. It has a specific optional argument colorcmap to select a color map. A working example on our test server is (note this url may be dysfunctional now and then, as it is a test server)
    http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=cdi_plot_map&DataInputs=\[EDMO_code=632;LOCAL_CDI_ID=world_N50W10N40E0_20070101_20080101;filename=world_N50W10N40E0_20070101_20080101;parameter=PSSTTS01;clim0=10;clim1=20;colormap=jet;\]&version=1.0.0
    The map functions can return kmz files or png files, which can be chosen by adding the WPS keyword responsedocument. The available options are listed in the getCapabilites return document, in this case default image/png and application/vnd.google-earth.kmz. Note that this is a WPS keyword, and hence appears outside the DataInputs (square brackets). Note that mimetype is a property of WPS keyword responsedocument, which is denoted with the =@. Requesting kmz hence requires padding: &responsedocument=Parameters=@mimetype=application/vnd.google-earth.kmz to the url.
    http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=cdi_plot_map&DataInputs=\[EDMO_code=632;LOCAL_CDI_ID=world_N50W10N40E0_20070101_20080101;filename=world_N50W10N40E0_20070101_20080101;parameter=PSSTTS01;clim0=10;clim1=20;colormap=jet;\]&responsedocument=Parameters=@mimetype=application/vnd.google-earth.kmz&version=1.0.0.
  • box_plot_profile and cdi_plot_profile to be applied to one available column from a remote odv file. It has specific optional argument z to select the y-axis, otherwise the index is the y-axis. A working example on our test server is (note this url may be dysfunctional now and then, as it is a test server)
    http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=cdi_plot_profile&DataInputs=\[EDMO_code=630;LOCAL_CDI_ID=CTDCAST_79___42_20110223_120541;filename=CTDCAST_79___42_20110223_120541;parameter=PSALPR02;z=PRESPS01;clim0=30;clim1=36\]&version=1.0.0
  • box_plot_timeseries and cdi_plot_timeseries to be applied to one available column from a remote odv file. A working example on our test server is (note this url may be dysfunctional now and then, as it is a test server)
    http://dtvirt5.deltares.nl/wps?service=wps&request=Execute&Identifier=cdi_plot_timeseries&DataInputs=\[EDMO_code=632;LOCAL_CDI_ID=world_N50W10N40E0;filename=world_N50W10N40E0_20070101_20080101;parameter=PSSTTS01;clim0=10;clim1=20;\]&version=1.0.0

The above processes and the input/output arguments can be inquired with the general WPS getCapabilites request

...