You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
together with the defaults station_latitude and station_longitude.
The decision to keep these has been a (deliberated) decision during the implementation based on the available information.
Still, more flexibility for the user (while keeping proper defaults) could improve the workflow. As an example, the API supports the md_returnfields: station_cartnorthing and station_carteasting as input as well, returning the coordinates in Lambert 72 instead of the default WGS84. Altough conversion can be done in R as well (see for example this function), the argument usage would simplify the workflow.
However, I do not have information or access to the possible arguments (either custom_attributes or md_returnfields) and the waterinfo documentation does not provide an overview as well. @WillemMaetens, is there such an overview available somewhere?
The text was updated successfully, but these errors were encountered:
Currently, the return-fields for each of the calls are hard-coded in the package
in
get_variables
:in
get_timeseries_tsid
:and in
get_stations
:together with the defaults
station_latitude
andstation_longitude
.The decision to keep these has been a (deliberated) decision during the implementation based on the available information.
Still, more flexibility for the user (while keeping proper defaults) could improve the workflow. As an example, the API supports the
md_returnfields
:station_cartnorthing
andstation_carteasting
as input as well, returning the coordinates in Lambert 72 instead of the default WGS84. Altough conversion can be done in R as well (see for example this function), the argument usage would simplify the workflow.However, I do not have information or access to the possible arguments (either
custom_attributes
ormd_returnfields
) and the waterinfo documentation does not provide an overview as well. @WillemMaetens, is there such an overview available somewhere?The text was updated successfully, but these errors were encountered: