Webtags: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
1,154 bytes removed ,  09:55, 2 November 2022
m
no edit summary
mNo edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
This page is the new ''Webtags'' page. This page and subpages hold a complete rewrite of the ''Webtags'' page.
= Introduction =
 
For C1 information please see [[Webtags_(preserving_history)|Webtags (preserving history)]] page.  
The information that was on this old ''Webtags'' page has been moved to [[Webtags_(preserving_history)|Webtags (preserving history)]]. You are advised to use that page until this page is ready and this message has been removed. If any questions or remarks please send a PM to [https://cumulus.hosiene.co.uk/memberlist.php?mode=viewprofile&u=9016 HansR] on the forum. Do not use the ''discussion'' tab unless accompanied by a PM: there is  no automated signal to HansR if you use that page.
 
This page and its subpages will document the Webtags from the point of view of the CumulusMX software and not the Cumulus 1 legacy software. Cumulus 1 is no longer maintained and will eventually disappear. If you are still using it, please refer to the original [[Webtags_(preserving_history)|Webtags (preserving history)]] page where @sfws has tried to give both packages equal value. That effort is no longer maintained in this ''Webtags'' page. We hope you will understand this approach.
 
Please do not edit this page while it is being worked on i.e. while this message is still here.
 
<hr/>


= 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 to ''CMX''. So e.g.:
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 to ''CMX''. So e.g.:


Line 19: Line 11:


= List of all tags =
= List of all tags =
This chapter is about the full list of Webtags. The names of the webtags are basically functional i.e. you can guess what the value says. The order of the tags in ''the local list'' is unknown, most likely it is a mix of time of origin, functionality and alphabetical ordering. The order of the tags in the full list is functional i.e. they are grouped by an arbitrary functional partition. Within such group no effort has been made to order according to another ordinal.  
This chapter is about the [[Full list of Webtags]]. The names of the webtags are basically functional i.e. you can guess what the value says. The order of the tags in ''the local list'' is unknown, most likely it is a mix of time of origin, functionality and alphabetical ordering. The order of the tags in the full list is functional i.e. they are grouped by an arbitrary functional partition. Within such group no effort has been made to order according to another ordinal.  


The naming of the webtags can sometimes be confusing
The naming of the webtags can sometimes be confusing
Line 28: Line 20:
== Inconsistency of tag names ==
== 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.
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.
For a short history of inconsistency you may read [[Webtags_(preserving_history)#General_Format_for_Web_Tags|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 "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
Line 45: Line 35:


== The full List ==
== The full List ==
The full list of Webtags carries a lot of additional information so it has its own [[Full list of Webtags|Webtag page]]. It is grouped by functionality without additional ordering. Some description is given where available.
The full list of Webtags has its own [[Full list of Webtags|Webtag page]]. It is grouped by functionality without additional ordering. Some description is given where available.


= Using Webtags =  
= Using Webtags =  
There are the following methods to ask CMX to do this translation both of which will be discussed below (or in a sub-page). The two methods are:
There are the following methods to ask CMX to do this translation all of which will be discussed below (or in a sub-page). The methods are:
#Processing files through the running instance of CumulusMX
#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 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]]
#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 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.
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 get method but it is in the POST method. Check out the differences in the above links.
'''NOTE''': it is not possible to give Webtag modifiers by using the GET method, but it is in the POST method. Check out the differences in the above links.


There are three bonus methods for getting values out of the CMX database:
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)
#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 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)
#Using the ''Custom Logs'' feature of CMX (from 3.22 and up) through which you get a timeseries of one or more Webtag(s)
Line 91: Line 81:


== Processing files ==
== Processing files ==
The oldest, most common and possibly the easiest method for using webtags is processing a file (e.g. a HTML web page or a PHP script) which contains a webtag description like <#temp rc=y>. After processing the output file then contains the value (e.g. 17.1) for that webtag and the complete description, including the brackets have then disappeared.  
The oldest, most common and probably the easiest method for using webtags is processing a file (e.g. a HTML web page or a PHP script) which contains a webtag description like <#temp rc=y>. After processing the output file then contains the value (e.g. 17.1) for that webtag and the complete description, including the brackets have then disappeared.  


The configuration should look like the screenshot below:
The configuration should look like the screenshot below:
Line 98: Line 88:


== MySQL ==
== MySQL ==
In the MySQL settings of the Interface there exists the possibility to create Custom Upload queries. This is n ot the place to treat the use of MySQL extensively, but CumulusMX offers the possibility to use Webtags in such a Custom Upload query definition. The example below should clarify:
In the MySQL settings of the Interface there exists the possibility to create Custom Upload queries. This is not the place to treat the use of MySQL extensively and the custom queries, but CumulusMX offers the possibility to use Webtags in such a Custom Upload query definition. The example below should clarify:


   <span style="font-family:Courier">INSERT IGNORE INTO `test_daily_summary` (`MaxRainRate`, `LogDate`, `RollOver`)
   <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>
     VALUES ('<#rrateTM>', '<#metdateyesterday format=yyyy-MM-dd>',  '(1 * SUBSTRING(<#rollovertime>,0,2))');</span>


Again, the modifiers are discussed below.
Again, the modifiers are discussed on [[Webtags/Parameters|their own page]].
 
[[Category:Cumulus_MX]]

Navigation menu