Re: [weewx-user] Display METAR Data in Seasons 4.6.2
In the Customization Guide (https://www.weewx.com/docs/customizing.htm) it explains the use of skin.conf vs weewx.conf. See Customizing reports | Options | Processing order Here is the recommendation: "Although it is possible to modify the options at any level, as the user of a skin, it is usually best to keep your modifications in the WeeWX configuration file (weewx.conf) if you can. That way you can apply any fixes or changes when the skin author updates the skin, and your customizations will not be overwritten." I do all my skin.conf additions in weewx.conf so they are not overwritten when the skin or weewx itself is upgraded. I also like having all my modifications in one place instead of scattered around the weewx directory structure. There is a note just above the recommendation that explains the hierarchy differences between the .conf files, specifically "options specified in weewx.conf must use two extra sets of brackets" which is why my example above has more brackets than the original author's example. On Friday, June 2, 2023 at 6:02:32 PM UTC-6 Nate Bargmann wrote: > * On 2023 02 Jun 18:44 -0500, Michael Bruski wrote: > > In reviewing the steps provided by MikeQ above, I see an issue with step > > 3. The search_list_extensions under the [[[CheetahGenerator]]] section > > should not be modified in weewx.conf but in skin.conf. If you don't find > > the search_list_extensions line in that section, just add it. The > original > > author made it clear in his write-up that the METAR data will not be > found > > by the skin unless you call the user.metargenerator.MyMetarSearch > function > > from within the skin. > > > I was indeed adding the extension line in the skin.conf as I already > have an extension for extended statistics in use. > > > Also, the [MetarReport] block is appended at the end > > of the skin.conf file. Notice single square bracket. Your list of > > airports will be encapsulated in double square brackets following the > > section heading. For example: > > > > [MetarReport] > > refresh_interval = 5 > > [[KBOI]] > > [[KONO]] > > ... > > That mirrors what I have near the end of the skin.conf file, after the > ImageGenerator and before the Generators sections. > > I think everything in the skin files was working, the errors originally > seemed to come from some module being called from within > metargenerator.py as the text of the error messages are slightly > different from what is in that file to be sent to syslog. > > - Nate > > -- > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f2f3423c-75d0-4409-a0f4-4cb409bf9ac8n%40googlegroups.com.
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
* On 2023 02 Jun 18:44 -0500, Michael Bruski wrote: > In reviewing the steps provided by MikeQ above, I see an issue with step > 3. The search_list_extensions under the [[[CheetahGenerator]]] section > should not be modified in weewx.conf but in skin.conf. If you don't find > the search_list_extensions line in that section, just add it. The original > author made it clear in his write-up that the METAR data will not be found > by the skin unless you call the user.metargenerator.MyMetarSearch function > from within the skin. I was indeed adding the extension line in the skin.conf as I already have an extension for extended statistics in use. > Also, the [MetarReport] block is appended at the end > of the skin.conf file. Notice single square bracket. Your list of > airports will be encapsulated in double square brackets following the > section heading. For example: > > [MetarReport] > refresh_interval = 5 > [[KBOI]] > [[KONO]] > ... That mirrors what I have near the end of the skin.conf file, after the ImageGenerator and before the Generators sections. I think everything in the skin files was working, the errors originally seemed to come from some module being called from within metargenerator.py as the text of the error messages are slightly different from what is in that file to be sent to syslog. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/20230603000227.n6n5fwj66r6upfm7%40n0nb.us. signature.asc Description: PGP signature
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
In reviewing the steps provided by MikeQ above, I see an issue with step 3. The search_list_extensions under the [[[CheetahGenerator]]] section should not be modified in weewx.conf but in skin.conf. If you don't find the search_list_extensions line in that section, just add it. The original author made it clear in his write-up that the METAR data will not be found by the skin unless you call the user.metargenerator.MyMetarSearch function from within the skin. Also, the [MetarReport] block is appended at the end of the skin.conf file. Notice single square bracket. Your list of airports will be encapsulated in double square brackets following the section heading. For example: [MetarReport] refresh_interval = 5 [[KBOI]] [[KONO]] ... On Friday, June 2, 2023 at 6:44:12 PM UTC-4 Nate Bargmann wrote: > * On 2023 02 Jun 15:48 -0500, Michael Bruski wrote: > > Attached is a diff file for my current changes. Note that this also > > disables the request for TAF data as I request that separately using > > tafgenerator.py. > > I've no need to separate the two so I just modified line 101 in the > original file as that seemed to be the only substantive change and I > still get the same failure so I've shelved this idea until such time as > it is fixed. > > - Nate > > -- > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a5926a98-9810-4c8d-bf6a-cf161fba66ddn%40googlegroups.com.
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
* On 2023 02 Jun 15:48 -0500, Michael Bruski wrote: > Attached is a diff file for my current changes. Note that this also > disables the request for TAF data as I request that separately using > tafgenerator.py. I've no need to separate the two so I just modified line 101 in the original file as that seemed to be the only substantive change and I still get the same failure so I've shelved this idea until such time as it is fixed. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/20230602224404.yuugtz6kldihhw2o%40n0nb.us. signature.asc Description: PGP signature
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
Attached is a diff file for my current changes. Note that this also
disables the request for TAF data as I request that separately using
tafgenerator.py.
In Seasons/skin.conf just tack another couple lines at the end for example:
[TafReport]
[[kbwi]]
and append ", user.tafgenerator.MyTafSearch" to the search_list_extensions
in the same file.
I'll submit another pull request on github to get these changes in.
My taf.inc for the Seasons skin is also attached.
On Friday, June 2, 2023 at 4:07:24 PM UTC-4 Michael Bruski wrote:
> I actually did the python3 rewrite and provided it to the original author
> to post on github. I may have changed my local copy sometime later to fix
> a problem with the URL but can't say for sure. I have about 7 lines in my
> generator that are commented out. I know I didn't post further updates to
> the author. I could post my current code block for statsHTMLTable() here
> but don't know how to go about getting it formatted correctly.
> Either that or send me your email address and I'll send it to you the file.
>
> I also created a tafgenerator based on the metargenerator so that I can
> post that separately from the METAR blocks.
>
>
> On Friday, June 2, 2023 at 3:15:14 PM UTC-4 MikeQ wrote:
>
>> I'm running the same thing. I don't think you will find anything in
>> debug mode since metargenerator.py seems to be running and it logs to
>> syslog directly. I am not a python programmer, but I think you will need
>> to add some additional "syslog.syslog(syslog.LOG_INFO,..." code to find
>> out exactly what is happening in def statsHTMLTable(self, airport): when it
>> tries to get the metar.
>>
>> On Friday, June 2, 2023 at 12:58:21 PM UTC-6 Nate Bargmann wrote:
>>
>>> * On 2023 02 Jun 13:31 -0500, MikeQ wrote:
>>> > One more thought - what version of Python are you running? The
>>> original
>>> > weewx-metar code was written in 2018 for Python2 and was re-written 2
>>> years
>>> > ago for Python3. The current version in master on github is the
>>> Python3
>>> > version.
>>>
>>> I am running on Amrbian (Debian) Bullseye which has Python 3.9.2. Would
>>> the extension benefit from running Weewx with debug mode enabled?
>>>
>>> - Nate
>>>
>>> --
>>> "The optimist proclaims that we live in the best of all
>>> possible worlds. The pessimist fears this is true."
>>> Web: https://www.n0nb.us
>>> Projects: https://github.com/N0NB
>>> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/76bc97d5-ccd5-4163-9e48-f683509b82fbn%40googlegroups.com.
# -*- coding: UTF-8 -*-
#
# Copyright (c) 2017-2018 Daniel Macías Perea
#
# Distributed under the terms of the GNU GENERAL PUBLIC LICENSE
#
# Derived metargenerator.py by Michael Bruski (AJ9X)
# Runs under Python3 and WeeWx version 4
#
# None of the local airports in my immediate vacinity provide TAFs.
# This extension allows me to display a TAF(s) for larger Airport(s) around
# me that do provide them. The results in this table are display separately
# from the metar table. I have also modified the URL in my copy of
# my copy of metargenerator.py to turn off the check for TAFs. Likewise,
# the URL in this generator turns off the check for METARs.
#
# To distinguish TAF backup files from METAR backup files, this generator
# will produce filenames in the form "icao.taf". Use the data tag
# $iaco_taf to include them in your report just as you would use
# $iaco_metar to display a METAR.
#
"""Extends the Cheetah generator search list to add TAF data tables.
To use it, add this generator to search_list_extensions in skin.conf:
[CheetahGenerator]
search_list_extensions = user.tafgenerator.MyTafSearch
#
# HTML TAF obtained from aviationweather.gov
#
[TafReport]
# Taf Airports to generate
refresh_interval = 5
[[kbwi]] # Create a new Cheetah tag which will have a _taf suffix: $kbwi_taf
[[kmdt]]
"""
from weewx.cheetahgenerator import SearchList
from weewx.tags import TimespanBinder
from datetime import datetime
import time
import os.path
import weeutil.weeutil
import syslog
import random
import requests
import re
class MyTafSearch(SearchList):
def __init__(self, generator):
SearchList.__init__(self, generator)
self.taf_dict = generator.skin_dict['TafReport']
self.refresh_interval = int(self.taf_dict.get('refresh_interval', 5))
self.cache_time = 0
self.search_list_extension = {}
def get_extension_list(self, valid_timespan, db_lookup):
"""For
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
I actually did the python3 rewrite and provided it to the original author to post on github. I may have changed my local copy sometime later to fix a problem with the URL but can't say for sure. I have about 7 lines in my generator that are commented out. I know I didn't post further updates to the author. I could post my current code block for statsHTMLTable() here but don't know how to go about getting it formatted correctly. Either that or send me your email address and I'll send it to you the file. I also created a tafgenerator based on the metargenerator so that I can post that separately from the METAR blocks. On Friday, June 2, 2023 at 3:15:14 PM UTC-4 MikeQ wrote: > I'm running the same thing. I don't think you will find anything in debug > mode since metargenerator.py seems to be running and it logs to syslog > directly. I am not a python programmer, but I think you will need to add > some additional "syslog.syslog(syslog.LOG_INFO,..." code to find out > exactly what is happening in def statsHTMLTable(self, airport): when it > tries to get the metar. > > On Friday, June 2, 2023 at 12:58:21 PM UTC-6 Nate Bargmann wrote: > >> * On 2023 02 Jun 13:31 -0500, MikeQ wrote: >> > One more thought - what version of Python are you running? The original >> > weewx-metar code was written in 2018 for Python2 and was re-written 2 >> years >> > ago for Python3. The current version in master on github is the Python3 >> > version. >> >> I am running on Amrbian (Debian) Bullseye which has Python 3.9.2. Would >> the extension benefit from running Weewx with debug mode enabled? >> >> - Nate >> >> -- >> "The optimist proclaims that we live in the best of all >> possible worlds. The pessimist fears this is true." >> Web: https://www.n0nb.us >> Projects: https://github.com/N0NB >> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 >> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c2cbf0b9-8ab7-45cd-90f6-e49a1616f2dbn%40googlegroups.com.
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
I'm running the same thing. I don't think you will find anything in debug mode since metargenerator.py seems to be running and it logs to syslog directly. I am not a python programmer, but I think you will need to add some additional "syslog.syslog(syslog.LOG_INFO,..." code to find out exactly what is happening in def statsHTMLTable(self, airport): when it tries to get the metar. On Friday, June 2, 2023 at 12:58:21 PM UTC-6 Nate Bargmann wrote: > * On 2023 02 Jun 13:31 -0500, MikeQ wrote: > > One more thought - what version of Python are you running? The original > > weewx-metar code was written in 2018 for Python2 and was re-written 2 > years > > ago for Python3. The current version in master on github is the Python3 > > version. > > I am running on Amrbian (Debian) Bullseye which has Python 3.9.2. Would > the extension benefit from running Weewx with debug mode enabled? > > - Nate > > -- > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2e9e5148-aba1-4306-877f-886e68c88e8en%40googlegroups.com.
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
* On 2023 02 Jun 13:31 -0500, MikeQ wrote: > One more thought - what version of Python are you running? The original > weewx-metar code was written in 2018 for Python2 and was re-written 2 years > ago for Python3. The current version in master on github is the Python3 > version. I am running on Amrbian (Debian) Bullseye which has Python 3.9.2. Would the extension benefit from running Weewx with debug mode enabled? - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/20230602185815.d3xae5wcgozivatw%40n0nb.us. signature.asc Description: PGP signature
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
One more thought - what version of Python are you running? The original weewx-metar code was written in 2018 for Python2 and was re-written 2 years ago for Python3. The current version in master on github is the Python3 version. On Friday, June 2, 2023 at 11:53:20 AM UTC-6 Nate Bargmann wrote: > * On 2023 02 Jun 12:36 -0500, MikeQ wrote: > > Did you test the URL from the box running WeeWX? I'm wondering if you > have > > a DNS or some other connectivity problem on that box. You could try > > running: > > > > curl > > -s > https://www.aviationweather.gov/adds/metars?station_ids=KBIE+_trans=translated_metars=on=most+recent+only_tafs=on=Get+Weather > > > > and see if you get the html response for the page. > > I had to quote the URL to keep the shell from interpreting the special > characters and once I did that, I did get the HTML page. This is from > the computer running Weewx. > > > Here is the output: > > > 8<-- > > http://www.w3.org/TR/REC-html40/strict.dtd;> > > > ADDS - METARS form results > > > > CELLPADDING=3 CELLSPACING=0> > > > Aviation Digital Data Service (ADDS) > Output produced by METARs form (1746UTC02 June 2023) > found at http://www.aviationweather.gov/metar/data/;> > http://www.aviationweather.gov/metar/data/ > > > > > > > METAR text: > > > KMYZ 021735Z AUTO 15003KT 10SM SCT110 27/20 A3000 RMK AO2 > LTG DSNT W > > > > > Conditions at: > > > KMYZ > (MARYSVILLE , KS, US) observed 1735UTC02 June 2023 > > > > > Temperature: > > > 270C (81F) > > > > > Dewpoint: > > > 200C (68F) [RH=66] > > > > > Pressure (altimeter): > > > 3000inchesHg (10160mb) > > > > > Winds: > > > from the SSE (150degrees) at 3MPH (3knots; > 1.5ms) > > > > > Visibility: > > > 10 or moremiles(16+km) > > > > > Ceiling: > > > at least 12,000 feet AGL > > > > > Clouds: > > > scattered clouds at 11000 feet AGL > > > > > Weather: > > > automated observation with no human augmentation;there may or may not > be significant weather present at this time > > > > > > > > > > > > >8-- > > > Perhaps the next step is that I need to look at the extension code and > try to figure out where it is failing. Sigh... > > - Nate > > -- > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/257f8159-e891-4d2e-bb26-8853b0efcad5n%40googlegroups.com.
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
* On 2023 02 Jun 12:36 -0500, MikeQ wrote: > Did you test the URL from the box running WeeWX? I'm wondering if you have > a DNS or some other connectivity problem on that box. You could try > running: > > curl > -s > https://www.aviationweather.gov/adds/metars?station_ids=KBIE+_trans=translated_metars=on=most+recent+only_tafs=on=Get+Weather > > and see if you get the html response for the page. I had to quote the URL to keep the shell from interpreting the special characters and once I did that, I did get the HTML page. This is from the computer running Weewx. Here is the output: 8<-- http://www.w3.org/TR/REC-html40/strict.dtd;> ADDS - METARS form results Aviation Digital Data Service (ADDS) Output produced by METARs form (1746UTC02 June 2023) found at http://www.aviationweather.gov/metar/data/;> http://www.aviationweather.gov/metar/data/ METAR text: KMYZ 021735Z AUTO 15003KT 10SM SCT110 27/20 A3000 RMK AO2 LTG DSNT W Conditions at: KMYZ (MARYSVILLE , KS, US) observed 1735UTC02 June 2023 Temperature: 270C (81F) Dewpoint: 200C (68F) [RH=66] Pressure (altimeter): 3000inchesHg (10160mb) Winds: from the SSE (150degrees) at 3MPH (3knots; 1.5ms) Visibility: 10 or moremiles(16+km) Ceiling: at least 12,000 feet AGL Clouds: scattered clouds at 11000 feet AGL Weather: automated observation with no human augmentation;there may or may not be significant weather present at this time >8-- Perhaps the next step is that I need to look at the extension code and try to figure out where it is failing. Sigh... - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/20230602175314.d3y4olbb7rgqptnj%40n0nb.us. signature.asc Description: PGP signature
Re: [weewx-user] Display METAR Data in Seasons 4.6.2
Did you test the URL from the box running WeeWX? I'm wondering if you have a DNS or some other connectivity problem on that box. You could try running: curl -s https://www.aviationweather.gov/adds/metars?station_ids=KBIE+_trans=translated_metars=on=most+recent+only_tafs=on=Get+Weather and see if you get the html response for the page. On Friday, June 2, 2023 at 6:37:45 AM UTC-6 Nate Bargmann wrote: > I just added this extension and while I added it to my Standard skin, I > don't think that is where the problem lies. I see the following from > the logs: > > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: request URL - > https://www.aviationweather.gov/adds/metars?station_ids=KMYZ+_trans=translated_metars=on=most+recent+only_tafs=on=Get+Weather > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: error: Cannot get > Metar Report (KMYZ_metar). Recovering the last file saved. > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: error: There could > not be found an older Metar Report. Skipping! > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: request URL - > https://www.aviationweather.gov/adds/metars?station_ids=KBIE+_trans=translated_metars=on=most+recent+only_tafs=on=Get+Weather > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: error: Cannot get > Metar Report (KBIE_metar). Recovering the last file saved. > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: error: There could > not be found an older Metar Report. Skipping! > Jun 02 07:25:29 wxbox weewxd[5488]: metargenerator.py: Generated 0 metar > tables in 0.01 seconds > > When I open either URL as shown in the log I get a valid METAR Web page > (see attached screen shots), yet I am getting "Error - No METAR > available" in the generated Web page. > > I am using the latest metargenerator.py from the Git clone of the > referenced repository. Perhaps I need to open an issue on GitHub for > this extension? > > - Nate > > -- > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4d573c2a-b169-4508-b936-5a1a5f780135n%40googlegroups.com.
