I have not been following the Ecowitt barometer discussion.

As for the database, it already supports three kinds of barometric
pressure: fields 'pressure', 'altimeter', and 'barometer'. See the wiki
article *Barometer, pressure, altimeter
<https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter>* for
the differences between them.

What does relative pressure offer that these fields don't already do? In
any case, it's easy enough for you to add a new field in your own database.
See the section *Adding a new type to the database
<http://www.weewx.com/docs/customizing.htm#add_archive_type>* in the
Customizing Guide.



On Tue, Jan 26, 2021 at 6:34 AM S R <[email protected]> wrote:

> worked like a charm....thank you.
>
> With the Seasons skin, i am not getting any barometer info because the
> template seems to use baromabsin but i see the ecowitt-client in
> interceptor is writing to the pressure field.
> Is it possible to tell the skin via the conf file which is the correct
> field to pull the pressure from?
> also, the ecowitt client also supports baromrelin - relative pressure, can
> we get the db extended to support that field too pls?
>
> On Tuesday, January 26, 2021 at 3:18:19 PM UTC+1 [email protected] wrote:
>
>> Easy fix to allow characters with an umlaut. In the skin.conf file that
>> you are using, change this
>>
>>     [[SummaryByMonth]]
>>         # Reports that summarize "by month"
>>         [[[NOAA_month]]]
>>             encoding = strict_ascii
>>             template = NOAA/NOAA-%Y-%m.txt.tmpl
>>
>>     [[SummaryByYear]]
>>         # Reports that summarize "by year"
>>         [[[NOAA_year]]]
>>             encoding = strict_ascii
>>             template = NOAA/NOAA-%Y.txt.tmpl
>>
>> to this
>>
>>     [[SummaryByMonth]]
>>         # Reports that summarize "by month"
>>         [[[NOAA_month]]]
>>             encoding = utf8
>>             template = NOAA/NOAA-%Y-%m.txt.tmpl
>>
>>     [[SummaryByYear]]
>>         # Reports that summarize "by year"
>>         [[[NOAA_year]]]
>>             encoding = utf8
>>             template = NOAA/NOAA-%Y.txt.tmpl
>>
>>
>>
>> On Tue, Jan 26, 2021 at 12:42 AM gjr80 <[email protected]> wrote:
>>
>>> Yes it would but the current code base is limited to what we can do with
>>> the python string encode() function. However, I have an idea for something
>>> we could do to hopefully improve things, let me discuss with Tom.
>>>
>>> Gary
>>>
>>> On Tuesday, 26 January 2021 at 17:55:23 UTC+10 [email protected] wrote:
>>>
>>>> wouldn't that make more sense to drop the umlaut and Düsseldorf =
>>>> Dusseldorf - that is what other webservices do that can't deal with
>>>> non-ascii characters. would be better than dropping the character 
>>>> completely
>>>>
>>>> On Tuesday, January 26, 2021 at 7:02:00 AM UTC+1 gjr80 wrote:
>>>>
>>>>> NOAA files use strict_ascii encoding
>>>>> <http://weewx.com/docs/customizing.htm#Specifying_template_files> so
>>>>> no umlauts or other accented characters unfortunately. You can change the
>>>>> encoding but as the NOAA format reports are tabulated reports it will mess
>>>>> up the format of the report.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Tuesday, 26 January 2021 at 15:53:23 UTC+10 [email protected]
>>>>> wrote:
>>>>>
>>>>>> The staion name has a German umlaut in it. It shows correctly on the
>>>>>> web pages, but in the NOAA files it misses the letter completely.
>>>>>> e.g. name = "Köln", NOAA file has "Kln"
>>>>>>
>>>>>> On Monday, January 25, 2021 at 11:52:49 PM UTC+1 [email protected]
>>>>>> wrote:
>>>>>>
>>>>>>> dumb question. the climatogical report & summary - Name, is missing "ö"
>>>>>>>> looks like it did not like UTF-8.
>>>>>>>> is there a way to manually fix this?
>>>>>>>>
>>>>>>>
>>>>>>> Not a dumb question at all, but I don't understand it either. What
>>>>>>> "ö"?
>>>>>>>
>>>>>> --
>>>
>> 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 [email protected].
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/614395f3-d991-45f9-ad80-dba7fe59168en%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/614395f3-d991-45f9-ad80-dba7fe59168en%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c7414cf9-7067-4d24-8d8d-1ebeb4bb3892n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/c7414cf9-7067-4d24-8d8d-1ebeb4bb3892n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEC-wPhBCH2ZKdy_ocfECwO52WRH8zU8wZEH6jTZjT1H%3DQ%40mail.gmail.com.

Reply via email to