This component uploads newly modified or generated data to a remote server. Generally, this action occurs periodically on remote acquisition systems to transfer the data they log to the main processing server.
Usage
da.transfer.upload [switches…] [station…]
Switches
- --flush[=BOOLEAN]
-
When enabled, this causes a flush of the acquisition system before initiating the actual data transfer. This is used to attempt to transmit as much data as is available now instead of potentially still having some buffered for later transmission.
Default: Disabled
- --profile=STRING
-
This is the profile name to execute. Multiple profiles can be defined to allow a single station to upload data to multiple destinations at potentially different intervals. Consult the station configuration for available profiles.
Default: aerosol
- --quiet[=BOOLEAN]
-
If set then no progress output is displayed and any confirmation prompts are bypassed.
Default: Disabled
- --wait=NUMBER
-
This is the maximum time to wait for another upload process to complete, in seconds. If there are two concurrent processes for the same station and profile, the new one will wait at most this many seconds before giving up without uploading new data. If this is set to undefined, it will wait forever for the other process to complete.
Default: 30 seconds
This option only accepts numbers greater than or equal to 0. Undefined values are permitted, to indicate that the option is set but not to a specific value.
Arguments
- station
-
This argument is used to specify the station used to look up variables that do not include a station as part of an archive read specification. The station is the three letter GAW station code of the location, such as
BND
. The argument accepts multiple stations specified as regular expressions and separated by:
or;
or,
. For exampleBND,MLO
and(BND|MLO)
are two ways of selecting both the BND and MLO stations.The special value
allstations
may also be specified to select all stations.
Examples
- Upload all pending aerosol data
-
This will upload all pending data in the "aerosol" profile. This will not force the acquisition system (if any) to flush data, so the total upload may be slightly behind real time (the data will still be uploaded later once it is written).
da.transfer.upload