Re: [weewx-development] Re: Intent to Implement: Aviation Unit System

2020-06-02 Thread Derek Harding
Great comments, thanks. 

On 3 June 2020 2:32:05 pm NZST, gjr80  wrote:
>Hi,
>
>2.5 years and no activity (and no related changes to the WeeWX
>codebase) so 
>I would say the thread is fairly well dead.
>
>I would go back to the 2nd post in the thread. WeeWX has a built-in
>unit 
>conversion/formatting system. This system supports unit 
>conversion/formatting options for tags in reports as well as providing 
>suitable hooks into the WeeWX API for unit conversion/formatting for
>3rd 
>party WeeWX services that may produce output independent of the WeeWX 
>reporting system. The unit system merely defines the units used for 
>different field types stored in the database, for almost all users this
>is 
>irrelevant as default display units for reports can be set in either
>the 
>WeeWX or skin config files and a properly written 3rd party service
>will 
>provide similar control via a config file. At the end of the day WeeWX 
>could store data as apples, oranges and bananas and as long as WeeWX
>knows 
>how to convert apples, oranges and bananas to (say) C or F, hPa or
>inHg, 
>m/s or knots or km/h or mph the user will be completely unaware of the 
>units used to store the data. The Units section 
> in the Customization
>Guide 
>provides some more insight into the unit system used by WeeWX.
>
>Gary
>
>On Tuesday, 2 June 2020 14:42:16 UTC+10, Derek Harding wrote:
>>
>> Hi,
>>
>> Is this thread dead or have you developed a more aviation-focussed 
>> offering? I am currently running Wview and an Oregon WMR88 at my
>local 
>> aerodrome and wish to migrate to Weewx but don't want to re-invent
>the 
>> wheel!
>>
>> -- 
>> Clear skies and no turbulence,
>> Derek
>>
>> On Tuesday, 12 September 2017 22:46:49 UTC+12, mwall wrote:
>>>
>>>
>>> from jamesshannon on 11sep2017:
>>>
>>> Hi,
>>>
>>> I'm just discovering weewx and want to say hi. I'm working on a
>project 
>>> to set up a weather monitoring solution for airports. As you can
>imagine, 
>>> weewx provides a ton of functionality. Since I was planning on
>writing this 
>>> in Python, it was a no-brainer to leverage weewx.
>>>
>>>
>>> That means that you can expect lots of questions and comments and 
>>> sometimes commits from me. :) However, I realize that your focus
>isn't 
>>> aviation so for things that are more aviation-weather-monitoring vs 
>>> home-weather-monitoring, I figure I'll run my proposal by you first
>to get 
>>> your input.
>>>
>>>
>>> In this case I'm interested in adding a new unit system for
>aviation. 
>>> It'll be similar to the US, but with a few changes -- windspeed in
>knots, 
>>> for example.
>>>
>>>
>>> I could, of course, do the conversions myself after StdConvert runs
>(or 
>>> replace StdConvert), but I feel like it makes sense to build this
>in. 
>>> Thoughts?
>>>
>>>
>>>
>
>-- 
>You received this message because you are subscribed to the Google
>Groups "weewx-development" group.
>To unsubscribe from this group and stop receiving emails from it, send
>an email to weewx-development+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>https://groups.google.com/d/msgid/weewx-development/5ebbd022-9eac-4bf6-a727-eeb46a085a65%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CC143123-8522-44D6-BBDB-C7CCCBDC99DE%40gmail.com.


[weewx-development] Re: Intent to Implement: Aviation Unit System

2020-06-02 Thread gjr80
Hi,

2.5 years and no activity (and no related changes to the WeeWX codebase) so 
I would say the thread is fairly well dead.

I would go back to the 2nd post in the thread. WeeWX has a built-in unit 
conversion/formatting system. This system supports unit 
conversion/formatting options for tags in reports as well as providing 
suitable hooks into the WeeWX API for unit conversion/formatting for 3rd 
party WeeWX services that may produce output independent of the WeeWX 
reporting system. The unit system merely defines the units used for 
different field types stored in the database, for almost all users this is 
irrelevant as default display units for reports can be set in either the 
WeeWX or skin config files and a properly written 3rd party service will 
provide similar control via a config file. At the end of the day WeeWX 
could store data as apples, oranges and bananas and as long as WeeWX knows 
how to convert apples, oranges and bananas to (say) C or F, hPa or inHg, 
m/s or knots or km/h or mph the user will be completely unaware of the 
units used to store the data. The Units section 
 in the Customization Guide 
provides some more insight into the unit system used by WeeWX.

Gary

On Tuesday, 2 June 2020 14:42:16 UTC+10, Derek Harding wrote:
>
> Hi,
>
> Is this thread dead or have you developed a more aviation-focussed 
> offering? I am currently running Wview and an Oregon WMR88 at my local 
> aerodrome and wish to migrate to Weewx but don't want to re-invent the 
> wheel!
>
> -- 
> Clear skies and no turbulence,
> Derek
>
> On Tuesday, 12 September 2017 22:46:49 UTC+12, mwall wrote:
>>
>>
>> from jamesshannon on 11sep2017:
>>
>> Hi,
>>
>> I'm just discovering weewx and want to say hi. I'm working on a project 
>> to set up a weather monitoring solution for airports. As you can imagine, 
>> weewx provides a ton of functionality. Since I was planning on writing this 
>> in Python, it was a no-brainer to leverage weewx.
>>
>>
>> That means that you can expect lots of questions and comments and 
>> sometimes commits from me. :) However, I realize that your focus isn't 
>> aviation so for things that are more aviation-weather-monitoring vs 
>> home-weather-monitoring, I figure I'll run my proposal by you first to get 
>> your input.
>>
>>
>> In this case I'm interested in adding a new unit system for aviation. 
>> It'll be similar to the US, but with a few changes -- windspeed in knots, 
>> for example.
>>
>>
>> I could, of course, do the conversions myself after StdConvert runs (or 
>> replace StdConvert), but I feel like it makes sense to build this in. 
>> Thoughts?
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/5ebbd022-9eac-4bf6-a727-eeb46a085a65%40googlegroups.com.


[weewx-development] Re: Intent to Implement: Aviation Unit System

2020-06-01 Thread Derek Harding
Hi,

Is this thread dead or have you developed a more aviation-focussed 
offering? I am currently running Wview and an Oregon WMR88 at my local 
aerodrome and wish to migrate to Weewx but don't want to re-invent the 
wheel!

-- 
Clear skies and no turbulence,
Derek

On Tuesday, 12 September 2017 22:46:49 UTC+12, mwall wrote:
>
>
> from jamesshannon on 11sep2017:
>
> Hi,
>
> I'm just discovering weewx and want to say hi. I'm working on a project to 
> set up a weather monitoring solution for airports. As you can imagine, 
> weewx provides a ton of functionality. Since I was planning on writing this 
> in Python, it was a no-brainer to leverage weewx.
>
>
> That means that you can expect lots of questions and comments and 
> sometimes commits from me. :) However, I realize that your focus isn't 
> aviation so for things that are more aviation-weather-monitoring vs 
> home-weather-monitoring, I figure I'll run my proposal by you first to get 
> your input.
>
>
> In this case I'm interested in adding a new unit system for aviation. 
> It'll be similar to the US, but with a few changes -- windspeed in knots, 
> for example.
>
>
> I could, of course, do the conversions myself after StdConvert runs (or 
> replace StdConvert), but I feel like it makes sense to build this in. 
> Thoughts?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/d6df16b1-c644-46d9-905d-bc4d3d8ae60f%40googlegroups.com.