1,643
edits
MeteoCam: Difference between revisions
m
→Inner Working
m (→Inner Working) |
|||
| Line 23: | Line 23: | ||
== Inner Working == | == Inner Working == | ||
=== Manual === | |||
Each realtime refresh time the meteocam image is reloaded. It is advised not to set a too high frequency. One second e.g. is too high. 30 seconds should be OK. | Each realtime refresh time the meteocam image is reloaded. It is advised not to set a too high frequency. One second e.g. is too high. 30 seconds should be OK. | ||
The refresh is done while bypassing the cache so a reload always actually takes place physically. | The refresh is done while bypassing the cache so a reload always actually takes place physically. | ||
For the timelapse videos, when starting up, all available videos with the configured extension are fetched and displayed in the drop down list. The user can select any and when activating the timelapse through the radio button that video starts playing immediately. The default HTML5 video viewer is used which means only ''mp4'', ''webm'' and ''ogg'' are allowed. | For the timelapse videos, when starting up, all available videos with the configured extension are fetched and displayed in the drop down list. The user can select any and when activating the timelapse through the radio button that video starts playing immediately. The default HTML5 video viewer is used which means only ''mp4'', ''webm'' and ''ogg'' are allowed. | ||
=== Ecowitt HP10 === | |||
The file ''meteocamrealtime.txt'' is filled by CMX with the image URL as supplied by Ecowitt and transferred to the server and checked by CUtils. If the URL is different from the previous one the image is fetched and displayed. Note that the frequency by which the HP 10 fetches a new image is configured in the camera. CMX caches the URL and gives one up every 5 minutes even if you did configure the image renewal every fifteen minutes. This is a trade off because the frequency is not published. | |||
== Limitation == | == Limitation == | ||