Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Bad reading nooa monthly e yearly report
Moderator: mcrossley
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Bad reading nooa monthly e yearly report
Hi, everyone,i see the noaa monthly and yearly report that show stranger simbol next to C°(indicated by the red arrow) maybe i can correct but how?
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12697
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Bad reading nooa monthly e yearly report
How are you viewing them?
It is a difference in character encoding schemes between the file and viewer.
It is a difference in character encoding schemes between the file and viewer.
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Re: Bad reading nooa monthly e yearly report
this is the files report that cumulus mx show in reports interface and in the remote file on te my web site,how can modificate?
- mcrossley
- Posts: 12697
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Bad reading nooa monthly e yearly report
I'd need to see your web page to advise, you need to post a link.
How have you configured MX to save the report - using UTF-8 encoding or not?
How have you configured MX to save the report - using UTF-8 encoding or not?
- HansR
- Posts: 5874
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bullseye
- Location: Wagenborgen (NL)
- Contact:
Re: Bad reading nooa monthly e yearly report
@Mark: Actually, it may be a bit different, funny thing is, I checked it myself this morning and was wondering what had happened. It is originally coded as on the page as: 'weird char' °C. I think it has originally been a two byte char where the intention was to do it correctly with a ° But the weird char remained and the °seems to have been placed in between. If you look at the source of the page you will see this. I am not sure where the reports are generated. I have a different layout but the char is there as well.
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
- mcrossley
- Posts: 12697
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Bad reading nooa monthly e yearly report
The NOAA file should not use HTML encoding, this is a plain text file.
If you have an encoding mismatch between the NOAA file contents and a HTML page you display it in then you will get these odd characters - it is not a corruption in the file itself. Open the file in a text editor and it will display correctly because it will adapt its encoding based on what it finds in the file.
The MX Admin interface uses HTML5 and UTF-8 encoding (the standard for HTML5), so if the NOAA reports are generated in ASCII encoding, you will see odd characters, there is not a lot I can do about that.
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Re: Bad reading nooa monthly e yearly report
http://www.collineaprutinemeteodue.alte ... MO1119.txt
I use UTF-8 encoding but I send the NOOA files online with the extra web file interface because using the interface where you set the files nooa the same does not work for uploads (the reason I have not yet figured it out)
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Re: Bad reading nooa monthly e yearly report
No wait I did it already, I opened the file with windows 10 notepad but the strange character is there, I was about to delete it manually but then I stopped because I thought I would do damage ....mcrossley wrote: ↑Thu 07 Nov 2019 10:19 amThe NOAA file should not use HTML encoding, this is a plain text file.
If you have an encoding mismatch between the NOAA file contents and a HTML page you display it in then you will get these odd characters - it is not a corruption in the file itself. Open the file in a text editor and it will display correctly because it will adapt its encoding based on what it finds in the file.
The MX Admin interface uses HTML5 and UTF-8 encoding (the standard for HTML5), so if the NOAA reports are generated in ASCII encoding, you will see odd characters, there is not a lot I can do about that.
- mcrossley
- Posts: 12697
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Bad reading nooa monthly e yearly report
Please zip up the files and attach them here so I can examine the encoding being used.
- mcrossley
- Posts: 12697
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Bad reading nooa monthly e yearly report
I'm wondering if the FTP process is corrupting the files, try ticking the "binary" option in the extra files configuration.
Some FTP servers can corrupt UTF-8 when doing "Text" transfers - they only use basic ASCII encoding.
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Re: Bad reading nooa monthly e yearly report
You do not have the required permissions to view the files attached to this post.
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Re: Bad reading nooa monthly e yearly report
-
- Posts: 106
- Joined: Wed 10 Feb 2016 8:43 pm
- Weather Station: Oregon Scientific wmr-200
- Operating System: Windows 10 - Android
- Location: U.S.
Re: Bad reading nooa monthly e yearly report
Another question I noticed in the dashboard interface but also in gauge (below I posted the image with the red arrow indicating the maximum value shown) the maximum value of the wind speed is 40 Km / h, as you can 'change this value?
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12697
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Bad reading nooa monthly e yearly report
A can of worms!
Short answer yes, in gauges.js
Change "windScaleDefMaxKmh" to what ever you want. (line 119 in the interface version of gauges.js)
But the code will change the max value depending on the data it is given - it will automatically increase the value as the wind speed approaches the current max value - and and what numbers will give a nice spread of figures and tickmarks.
- HansR
- Posts: 5874
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bullseye
- Location: Wagenborgen (NL)
- Contact:
Re: Bad reading nooa monthly e yearly report
It probably is not a CMX problem but a web template issue.mcrossley wrote: ↑Thu 07 Nov 2019 10:19 amThe NOAA file should not use HTML encoding, this is a plain text file.
If you have an encoding mismatch between the NOAA file contents and a HTML page you display it in then you will get these odd characters - it is not a corruption in the file itself. Open the file in a text editor and it will display correctly because it will adapt its encoding based on what it finds in the file.
The MX Admin interface uses HTML5 and UTF-8 encoding (the standard for HTML5), so if the NOAA reports are generated in ASCII encoding, you will see odd characters, there is not a lot I can do about that.
I just checked where it comes from - I use the Saratoga template myself - and the part of the code that displays the report is a bit upgraded by beteljuice. He entered the following code on three places :
Code: Select all
$rpt = preg_replace('|<|Uis','<',$rpt);
$rpt = preg_replace('|>|Uis','>',$rpt);
$rpt = preg_replace('|°|Uis','°',$rpt);
echo $rpt;
I think beteljuice must take a look at it.
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3