1,725
edits
m (→Using Webtags) |
mNo edit summary |
||
(13 intermediate revisions by the same user not shown) | |||
= Introduction =▼
For C1 information please see [[Webtags_(preserving_history)|Webtags (preserving history)]] page.
Data gathered by CMX is stored locally in the database (see e.g. [[Dayfile.txt|dayfile]] and [[Standard_log_files|standard logfiles]] and a range of ini files, Extra Sensor files, Airlink logfiles etc...). To make these data - and calculated derivatives - available to the user ''CumulusMX'' (''CMX'') uses a system of Webtags. In short, a ''Webtag'' is a symbolic name which is translated into a value when asked
▲= Introduction =
▲Data gathered by CMX is stored locally in the database (see e.g. [[Dayfile.txt|dayfile]] and [[Standard_log_files|standard logfiles]] and a range of ini files, Extra Sensor files, Airlink logfiles etc...). To make these data - and calculated derivatives - available to the user ''CumulusMX'' (''CMX'') uses a system of Webtags. In short, a ''Webtag'' is a symbolic name which is translated into a value when asked by ''CMX''. So e.g.:
temp -> (process) -> 17.1
= List of all tags =
This chapter is about the
The naming of the webtags can sometimes be confusing
== Inconsistency of tag names ==
The naming of the tags can sometime be confusing. The long history of development of Cumulus(MX) has left its traces and although technically corrections can be made, the effort to do that is such that I won't bet on it happening. So a short guide to what can be expected follows here.
#Inconsistency in use of "Y": The character "Y" has been selected to denote yesterday in tag names. The inconsistency is where it appears. e.g. rfallY, YSunshineHours, Ybeaufort, windAvgY
#Inconsistency in use of "T": Where the "T" is added as indicating the time of the event (High or Low) e.g. leading to T<tag name>TH, this method is not consistently followed and may lead to some confusion. E.g. tempTH (the value for the temperature at its maximum) and TtempTH (for the time of that corresponding value). But also YearDewPointH (years highest dewpoint) and YearDewPointHT for the time of the event i.s.o. TYearDewPointH (which does not exist but which might have been more consistent).
Whatever you find and use, make sure you understand what you are looking at (you may need tests to verify). If the lists below are not correct,
== The local List ==
From version 3.12.0 the complete list of Webtags can be generated from your running CumulusMX instance.
Goto the interface. In the menu go to ''Program settings=>General options'', tick ''List web tags''. The next time that MX is restarted, it will create a file called ''WebTags.txt'' in the same folder as where the executable is found. Unticking that parameter will have the inverse effect and the file will no longer be renewed at restart (though the file is not removed).
The ''WebTags.txt'' file will list all the tags your build of Cumulus can currently handle. This list only contains the bare tag names. Parameters and modifiers will need to be looked up and added to make use of these. This list can be of use if you are using the tags to create your own program or website while interfacing with CumulusMX. It is useful to save it now and then with the CMX version nr in its name. This will make it possible to find the new tags easily through making a difference.
== The full List ==
The full list of Webtags
= Using Webtags =
There are the following methods to ask CMX to do this translation
#Processing files through the running instance of CumulusMX
#Getting the value by using the local interface [[Cumulus_MX_Local_API#General_API_-_HTTP_GET|GET method]].
#Getting the values through the local interface [[Cumulus_MX_Local_API#General_API_-_HTTP_POST|POST method]]
The first method is used in files used as input for the Extra Web Files in CMX which are then processed by CMX if you tick ''process''. The output file then contains the value.<br/>
The second and third method's principal use is to be used programmatically from anywhere you can reach the CumulusMX machine.
'''NOTE''': it is not possible to give Webtag modifiers by using the
There are three bonus methods for getting values out of the CMX database:
#Getting [[Cumulus_MX_Local_API#Predetermined_Data|predetermined data]] (not really with Webtags but useful in this context)
#Using MySQL through the Custom Upload feature
#Using the ''Custom Logs'' feature of CMX (from 3.22 and up) through which you get a timeseries of one or more Webtag(s)
Before using the Webtags, the user must be aware of the formatting.
In the position, in any file to be processed, SQL, or HTTP POST call, where Cumulus is to insert the relevant data, place a web tag in the '''general format''' specified here (follow the links to get to the Parameters page):
<code><#tag_name <nowiki>[</nowiki>[[Webtags/Parameters#Input_modification_Parameters|optional input selection parameters]]<nowiki>]</nowiki> <nowiki>[</nowiki>[[Webtags/Parameters#Output_modification_parameters|optional output modification parameters]]<nowiki>]</nowiki>></code>
Only the [[Cumulus_MX_Local_API#General_API_-_HTTP_GET|GET method]] has another format and does not accept modifiers.
== Processing files ==
The oldest, most common and
The configuration should look like the screenshot below:
== MySQL ==
In the MySQL settings of the Interface there exists the possibility to create Custom Upload queries. This is
<span style="font-family:Courier">INSERT IGNORE INTO `test_daily_summary` (`MaxRainRate`, `LogDate`, `RollOver`)
VALUES ('<#rrateTM>', '<#metdateyesterday format=yyyy-MM-dd>', '(1 * SUBSTRING(<#rollovertime>,0,2))');</span>
Again, the modifiers are discussed
[[Category:Cumulus_MX]]
|