This page is the new Recent History page. This page is part of a complete rewrite of the Webtags page. As long as this message exists please refer to Recent History (preserving history).
This page is Work in Progress until this message is deleted.
If any questions or remarks please send a PM to 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 page where @sfws has tried to give both packages equal value. That effort is no longer maintained in this 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.
Uploading data to a web server outside MX
Please note this Wiki page applies to releases 3.10.1 onwards. NOTE: Earlier MX releases used HTML template files that created web pages locally for uploading to a web server.
This Wiki category page is the entry point to the documentation describing how the JSON format is used in optional web site functionality for updating data to a web server outside Cumulus MX.
The webfiles sub-folder contains the following web pages that are uploaded just once to your web server (obviously if they get changed in a new release, then the new files are uploaded to replace the old ones as another one-off operation).
- Each of these web pages depends on a number of other files (in lib, js, and css sub-folders).
- they also depend on one or more files being uploaded to supply data:
|realtimegaugesT.txt in web sub-folder
|Internet settings -->> Web/FTP Settings -->> Realtime Settings -->> realtimegauges.txt -->> Generate
|Please see SteelSeries_Gauges (although that was written for legacy Cumulus 1)
|historic.htm, trends.htm, selectachart.htm
|Generated in the code
|availabledata.json, graphconfig.json, plus files with data for what to be plotted (e.g. alldailyhumdata.json)
|Internet settings -->> Web/FTP Settings -->> Interval Settings -->>
|availabledata.json and graphconfig.json files must be uploaded just once after you select which graphs you want to plot (so if you for example decide to swap from apparent temperature to feels like, upload the first file again)
|index.htm, monthlyrecord.htm, record.htm, thismonth.htm, thisyear.htm, today.htm, yesterday.htm
|Internet settings -->> Web/FTP Settings -->> Standard File Settings -->> websitedata.json -->> Generate
|please see New Default Web Site Information
|Generated in code
|NOAA Settings -->> all sub-sections
Data Transfer Format
Use of this format is introduced in Cumulus MX, and none of the files in this category are applicable to the legacy 1.9.4 software.
Documentation for local application programming interface
MX uses JSON format (specified as part of MX internal code) for the pages that show weather information in the MX Administrative Interface, on the web server generated by MX.
The Cumulus Wiki pages that document JSON usage in that interface are linked from the link in the heading above, and are not included in this category.
For example, the page that displays weather for today and yesterday uses the 6 formats described on this page.
Links listed below
Please work through all linked pages, and ensure Cumulus MX documentation is completed
MX stores all the xxxx.json files, linked from this Wiki page, in the web sub-folder of your MX installation.
Please note if you are using an older release some files may not be available, and MX development may add files that need to be documented here.
Pages in category "JSON Files"
The following 17 pages are in this category, out of 17 total.