date:20220117

Re: [weewx-user] safety of wind instruments on metal pole on roof?

2022-01-17 Thread John Smith

On Tue, 18 Jan 2022 at 17:11, Les Niles  wrote:

> What about using a fiberglass pole instead?  The wires to the instruments
> could still potentially attract lightning, but probably wouldn’t carry
> enough current to start a fire — might blow out the weather station
> electronics, but not burn down the house.  Max-gain Systems
>  sells fiberglass rods and tubes in various lengths
> and diameters.
>

I had a near hit that blew the windspeed/direction port on a davis ISS, so
direct hits aren't the only worry.

-- 
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/CAGTinV6osu7bU6-y12WDLJUsuXEsy-mydddDngtmgAvvwD7WMg%40mail.gmail.com.

Re: [weewx-user] safety of wind instruments on metal pole on roof?

2022-01-17 Thread Les Niles

What about using a fiberglass pole instead?  The wires to the instruments could 
still potentially attract lightning, but probably wouldn’t carry enough current 
to start a fire — might blow out the weather station electronics, but not burn 
down the house.  Max-gain Systems  sells fiberglass rods 
and tubes in various lengths and diameters.  

  -Les



> On 17 Jan 2022, at 12:03, morr...@gmail.com  wrote:
> 
> Not strictly weewx related, but:
> 
> Any safety concerns with mounting my wind speed and direction instruments on 
> a 1.25" galvanized steel pole, 6 feet above the roof line? 
> 
> I currently have a prototype anemometer about 20 feet in the air. It's well 
> away from our house so solar powered, which is proving a challenge.
> 
> We get a bit of lightning here, but there are tall trees near our house, and 
> I've never heard of a direct hit in the neighborhood.
> 
> Thanks for any experience/anecdotes.
> 
> -- 
> 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/e7a23b4f-51af-4513-a31f-af9e64e4f527n%40googlegroups.com
>  
> .

-- 
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/D99852A4-B115-4924-82FB-A3AE73DCA3FB%402pi.org.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

2022-01-17 Thread storm...@gmail.com

First, not starting any arguments. Second the chart is over a 48 Hr period, 
sample at 5 minutes intervals.  Both my stations had basically shown the 
same increase and decrease for each wave. And according to the following  
link: https://twitter.com/akrherz/status/1482436390105272320, the direct 
wave passed through the area around 15:00 UTC (10:00 AM) and the second 
wave (much strong) from the opposite direction  passed through the 
area around 05:10 UTC (12:10 AM) Jan 16.  

On Monday, January 17, 2022 at 10:51:05 PM UTC-5 ln77 wrote:

> I think you’re looking at the wrong time period.  The initial, direct wave 
> arrived at the U.S. west coast — about 8400 Km from Tonga — around 4:00am 
> Pacific time on Jan 15.  It should take 3-1/2 to 4 hours to travel the 
> additional 4600 Km to your location.  That, plus the 4 hour time 
> difference, would put it at around 12:00 noon your time on Jan 15, not Jan 
> 16.  The long path wave should’ve arrived at your location something like 
> 13-14 hours later, or shortly after midnight on Jan 16.  The second trip 
> around the Earth of the initial wave would be something like 32-36 hours 
> after the first arrival, or 20:00-24:00 your time on Jan 16.  What you’ve 
> plotted here misses all of those.  
>
>   -Les
>
>
>
> On 17 Jan 2022, at 11:58, morr...@gmail.com  wrote:
>
> Not sure I am really seeing it here in maritime Canada. We're about 13000 
> km from Tonga.
>
> Attached is a gnuplot command file and its output is:
>
>

-- 
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/d0009835-c280-4ede-8754-2c9354950cc5n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

2022-01-17 Thread Les Niles

I think you’re looking at the wrong time period. The initial, direct wave arrived at the U.S. west coast — about 8400 Km from Tonga — around 4:00am Pacific time on Jan 15. It should take 3-1/2 to 4 hours to travel the additional 4600 Km to your location. That, plus the 4 hour time difference, would put it at around 12:00 noon your time on Jan 15, not Jan 16. The long path wave should’ve arrived at your location something like 13-14 hours later, or shortly after midnight on Jan 16. The second trip around the Earth of the initial wave would be something like 32-36 hours after the first arrival, or 20:00-24:00 your time on Jan 16. What you’ve plotted here misses all of those.
-Les

On 17 Jan 2022, at 11:58, morr...@gmail.com wrote:Not sure I am really seeing it here in maritime Canada. We're about 13000 km from Tonga.Attached is a gnuplot command file and its output is:

--
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/52D74246-A0DA-4F09-8CE2-8C146E76DE84%402pi.org.
The pressure pulse should have arrived about 12:00 local time. There is a little pressure increase at about 12:10.Use the command file to read from weewx database:rm barometer.png; sqlite3 weewx.sdb "select datetime, barometer from archive where datetime > 164232 and datetime < 1642384200 order by dateTime;" | gnuplot barometer.gnupand modify as needed for your own location.

barometer.gnup
Description: Binary data

[weewx-user] Re: When did the blast wave of the eruption "hit" your station?

2022-01-17 Thread storm...@gmail.com

Check early morning Jan 16, when the wave came the opposite direction. 
Might of capture that wave.  They say the second wave was stronger on the 
east coast.

[image: Eruption Pressure Blips.png]  

On Monday, January 17, 2022 at 10:24:20 PM UTC-5 robcr...@gmail.com wrote:

> [image: TongaPressureWave.jpg]
> Seattle, Washington! I noticed it the same day, but didn't read y'all's 
> comments till now. Pretty cool. :-)
>
> On Sunday, January 16, 2022 at 2:46:25 AM UTC-8 michael.k...@gmx.at wrote:
>
>> As you may have noticed, there was a huge vulcano eruption in the 
>> southern pacific. The blast wave hit central europe yesterday n the evening 
>> around 20:10 CET.
>>
>> You can observe a steep rise in pressure at the time:
>> [image: 2022-01-16 11_40_47-Das Wetter in Rif - Brave.png]
>> You can see the spike in weewx stations around the world...
>>
>

-- 
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/ce6a3a60-1f40-4e08-8000-26aea498c84cn%40googlegroups.com.

[weewx-user] Re: When did the blast wave of the eruption "hit" your station?

2022-01-17 Thread Rob Cranfill

[image: TongaPressureWave.jpg]
Seattle, Washington! I noticed it the same day, but didn't read y'all's 
comments till now. Pretty cool. :-)

On Sunday, January 16, 2022 at 2:46:25 AM UTC-8 michael.k...@gmx.at wrote:

> As you may have noticed, there was a huge vulcano eruption in the southern 
> pacific. The blast wave hit central europe yesterday n the evening around 
> 20:10 CET.
>
> You can observe a steep rise in pressure at the time:
> [image: 2022-01-16 11_40_47-Das Wetter in Rif - Brave.png]
> You can see the spike in weewx stations around the world...
>

-- 
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/3faa153a-3bd0-4e2c-a24e-f7347bf68978n%40googlegroups.com.

Re: [weewx-user] Re: Storing Text as a record, wee_import and mysql UPDATE

2022-01-17 Thread Glenn McKechnie

Thanks Gary, I appreciate it.

Hopefully UPDATE won't raise any serious weewx issues.
I look forward to seeing it raised as an issue :)

On 18/01/2022, gjr80  wrote:
> Correct, wee_import will not accept text only fields. When we put together
> wee_import we only included support for numeric fields; text fields were
> omitted, perhaps not intentionally, but more likely because no real
> consideration had been given to including them in the schema. That being
> said, it should be a fairly simple process to modify wee_import to support
> text fields, at least for CSV imports anyway. Having had a quick wee_import
>
> refresher this morning I am thinking we could support something like
> ANComment
> = ANComment, text in the field map. Let me look at this further and see
> what I can come up with.
>
> As for supporting UPDATE, that will require further thought as I suspect
> that will introduce a number of wider issues. I'll probably raise an issue
> for that one.
>
> Gary
> On Monday, 17 January 2022 at 23:14:00 UTC+10 Glenn McKechnie wrote:
>
>> Working with TEXT records.
>>
>> I've gone through the wiki entry
>> https://github.com/weewx/weewx/wiki/Storing-text-in-the-database
>> and that all works well. I can add TEXT to the database and display it
>> in the weewx skin. So far so good.
>>
>> Using a modified filepile.py, I can add what I want via the new_archive
>> record hook. What I can't seem to do is add historical data that is in
>> TEXT form, via weewx. Fair enough, it makes sense.
>>
>> I figured wee_import may be a solution so I crafted a csv file and used
>> wee_import but it baulks on the text field. The csv files,
>> /var/tmp/weewxaddnotes.csv has the contents...
>>
>> timestamp,extraTemp1,extraTemp2,ANComment
>> 1641729300,23.0,22.0,"Test.\\nThen test again"
>>
>> It appears to be wanting a weewx_unit_name and I'm missing a clue stick.
>> I can't find a name that it will accept without error. If the
>> weewx_unit_name field is left blank (only the csv_field_name is given)
>> it gives the following.
>>
>> Obtaining raw import data for period 1 ...
>>  Unable to parse source-to-WeeWX field map.
>>  No units specified for source field 'ANComment' in
>> /home/weewx/csv.conf.
>>  Nothing done, exiting.
>>
>> Which makes sense as I had the following...
>>
>> [[FieldMap]]
>> dateTime = timestamp, unix_epoch
>> interval =
>> barometer =
>> pressure =
>> altimeter =
>> inTemp =
>> outTemp =
>> extraTemp1 = extraTemp1, degree_C
>> extraTemp2 = extraTemp2, degree_C
>> ANComment = ANComment
>>
>> If I tell wee_imports to ignore the ANComment entry, as follows...
>> ANComment =
>> then everything else imports as expected so it's falling over on the
>> ANComment field
>>
>> ignore_invalid_data in the csv.conf file is tantalizing close (a numeric
>> field containing non-numeric data) but I don't want it skipped or
>> halted. I want it accepted.
>>
>> Can I write anything into that 2nd field that will allow a TEXT entry to
>> skip the conversion process, and allow it to be written as-is to the
>> database?
>>
>> On reflection, even if I can use wee_import to add the data I want. I
>> need to get it correct and complete the first time as once a RECORD is
>> written (and all it's fields filled) then I can't update it later
>> without going the manual route as weewx appears to be missing an inbuilt
>> sql UPDATE archive method. That or I can't find it.
>>
>> And, that's probably so we don't shoot ourselves in the foot.
>>
>> But it sure would be nice to write a historical record using weewx or
>> preferably wee_import (with all their built in sanity checks) and then,
>> if needed later, be able to update any missing fields, or correct errant
>> values without going back to the command line.
>>
>> I understand the risk of blindly updating existing records, but in this
>> case they are all known empty or new fields, and if they do have
>> something in them then it needs changing anyway!
>> Caveat Emptor or something along those lines! :-)
>>
>>
>> As an aside. I'm doing this as I have a whole host of manual rain
>> records that should be entered as they are sanity checks on the
>> automatic gauges, weewx seems as good a place as any to store them.
>> At the same time I'll be adding extraTemp values that I've recorded
>> from the haystack.
>> It'd be nice to plot them, and change them, as they use existing
>> fields - extraTemp1 etc.
>>
>> Along with that, a TEXT comment as to why some readings appear as they
>> do would be useful, or where the floods were after the recent epic
>> rainfall, or why the rain values appear to be stuffed, or which area of
>> the haystack the probe is at.
>> The latest Tongan earthquake is probably another example given the
>> recent barometric burps it caused.
>>
>> The possibilities expand as I write.
>> So I better go.
>>
>> But... In summary.
>>
>> wee_import appears to baulk on the new add TEXT method. Is there a quick
>> fix?
>>
>> The ability to sql UPDATE any

[weewx-user] Re: Storing Text as a record, wee_import and mysql UPDATE

2022-01-17 Thread gjr80

Correct, wee_import will not accept text only fields. When we put together 
wee_import we only included support for numeric fields; text fields were 
omitted, perhaps not intentionally, but more likely because no real 
consideration had been given to including them in the schema. That being 
said, it should be a fairly simple process to modify wee_import to support 
text fields, at least for CSV imports anyway. Having had a quick wee_import 
refresher this morning I am thinking we could support something like ANComment 
= ANComment, text in the field map. Let me look at this further and see 
what I can come up with.

As for supporting UPDATE, that will require further thought as I suspect 
that will introduce a number of wider issues. I'll probably raise an issue 
for that one. 

Gary
On Monday, 17 January 2022 at 23:14:00 UTC+10 Glenn McKechnie wrote:

> Working with TEXT records.
>
> I've gone through the wiki entry
> https://github.com/weewx/weewx/wiki/Storing-text-in-the-database
> and that all works well. I can add TEXT to the database and display it
> in the weewx skin. So far so good.
>
> Using a modified filepile.py, I can add what I want via the new_archive
> record hook. What I can't seem to do is add historical data that is in
> TEXT form, via weewx. Fair enough, it makes sense.
>
> I figured wee_import may be a solution so I crafted a csv file and used
> wee_import but it baulks on the text field. The csv files,
> /var/tmp/weewxaddnotes.csv has the contents...
>
> timestamp,extraTemp1,extraTemp2,ANComment
> 1641729300,23.0,22.0,"Test.\\nThen test again"
>
> It appears to be wanting a weewx_unit_name and I'm missing a clue stick.
> I can't find a name that it will accept without error. If the
> weewx_unit_name field is left blank (only the csv_field_name is given)
> it gives the following.
>
> Obtaining raw import data for period 1 ...
>  Unable to parse source-to-WeeWX field map.
>  No units specified for source field 'ANComment' in 
> /home/weewx/csv.conf.
>  Nothing done, exiting.
>
> Which makes sense as I had the following...
>
> [[FieldMap]]
> dateTime = timestamp, unix_epoch
> interval =
> barometer =
> pressure =
> altimeter =
> inTemp =
> outTemp =
> extraTemp1 = extraTemp1, degree_C
> extraTemp2 = extraTemp2, degree_C
> ANComment = ANComment
>
> If I tell wee_imports to ignore the ANComment entry, as follows...
> ANComment =
> then everything else imports as expected so it's falling over on the
> ANComment field
>
> ignore_invalid_data in the csv.conf file is tantalizing close (a numeric
> field containing non-numeric data) but I don't want it skipped or
> halted. I want it accepted.
>
> Can I write anything into that 2nd field that will allow a TEXT entry to
> skip the conversion process, and allow it to be written as-is to the
> database?
>
> On reflection, even if I can use wee_import to add the data I want. I
> need to get it correct and complete the first time as once a RECORD is
> written (and all it's fields filled) then I can't update it later
> without going the manual route as weewx appears to be missing an inbuilt
> sql UPDATE archive method. That or I can't find it.
>
> And, that's probably so we don't shoot ourselves in the foot.
>
> But it sure would be nice to write a historical record using weewx or
> preferably wee_import (with all their built in sanity checks) and then,
> if needed later, be able to update any missing fields, or correct errant
> values without going back to the command line.
>
> I understand the risk of blindly updating existing records, but in this
> case they are all known empty or new fields, and if they do have
> something in them then it needs changing anyway!
> Caveat Emptor or something along those lines! :-)
>
>
> As an aside. I'm doing this as I have a whole host of manual rain
> records that should be entered as they are sanity checks on the
> automatic gauges, weewx seems as good a place as any to store them.
> At the same time I'll be adding extraTemp values that I've recorded
> from the haystack.
> It'd be nice to plot them, and change them, as they use existing
> fields - extraTemp1 etc.
>
> Along with that, a TEXT comment as to why some readings appear as they
> do would be useful, or where the floods were after the recent epic
> rainfall, or why the rain values appear to be stuffed, or which area of
> the haystack the probe is at.
> The latest Tongan earthquake is probably another example given the
> recent barometric burps it caused.
>
> The possibilities expand as I write.
> So I better go.
>
> But... In summary.
>
> wee_import appears to baulk on the new add TEXT method. Is there a quick
> fix?
>
> The ability to sql UPDATE any historical weewx record would be useful. 1
> or many RECORD fields at a time.
>
> Individual confirmations not required. Other than accepting a one-time
> answer that; 'yes', I will bandage my own toes and blame no-one else if
> it backfires, because we always have our backups.
>
> Ha! Perhaps a

[weewx-user] Re: safety of wind instruments on metal pole on roof?

2022-01-17 Thread Karen K

There are people who lost their electronic equipment in the house including 
radio, tv set etc. because of a little bit of lightning near their house.

Trees are not exactly lightning rods.

I would strongly suggest to ground the pole using a round steel of about 
1/3" (about 10mm). There should be some grounding point in your house, 
where you can connect that round steel to. You must not use electric wire 
for that. And I strongly recommend to place that outside your house at the 
wall.

In case there is no such thing as a grounding point, you need a bar of 
stainless steel, again about 1/3" (about 10mm) and at least 18 feet in 
length. The whole thing you drive into the earth. The upper end that looks 
out of the earth you can connect to instrument pole. As 18 feet are very 
long, bars of about 3 feet are provided including a thread at the end to 
connect one to the other. And there are special devices to drive the bar 
into the earth by vibration.

morr...@gmail.com schrieb am Montag, 17. Januar 2022 um 21:03:47 UTC+1:

> Not strictly weewx related, but:
>
> Any safety concerns with mounting my wind speed and direction instruments 
> on a 1.25" galvanized steel pole, 6 feet above the roof line? 
>
> I currently have a prototype anemometer about 20 feet in the air. It's 
> well away from our house so solar powered, which is proving a challenge.
>
> We get a bit of lightning here, but there are tall trees near our house, 
> and I've never heard of a direct hit in the neighborhood.
>
> Thanks for any experience/anecdotes.
>

-- 
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/833d9e57-462c-4bbe-8509-f7ad947957e4n%40googlegroups.com.

[weewx-user] safety of wind instruments on metal pole on roof?

2022-01-17 Thread morr...@gmail.com

Not strictly weewx related, but:

Any safety concerns with mounting my wind speed and direction instruments 
on a 1.25" galvanized steel pole, 6 feet above the roof line? 

I currently have a prototype anemometer about 20 feet in the air. It's well 
away from our house so solar powered, which is proving a challenge.

We get a bit of lightning here, but there are tall trees near our house, 
and I've never heard of a direct hit in the neighborhood.

Thanks for any experience/anecdotes.

-- 
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/e7a23b4f-51af-4513-a31f-af9e64e4f527n%40googlegroups.com.

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

2022-01-17 Thread morr...@gmail.com

Not sure I am really seeing it here in maritime Canada. We're about 13000 
km from Tonga.

Attached is a gnuplot command file and its output is:
[image: barometer.png]
The pressure pulse should have arrived about 12:00 local time. There is a 
little pressure increase at about 12:10.

Use the command file to read from weewx database:

rm barometer.png; sqlite3 weewx.sdb "select datetime, barometer from 
archive where datetime > 164232 and datetime < 1642384200 order by 
dateTime;" | gnuplot barometer.gnup

and modify as needed for your own location.

-- 
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/74084e3d-13ed-4039-ae5c-a5498a95751en%40googlegroups.com.


barometer.gnup
Description: Binary data

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

2022-01-17 Thread Bob

For those who find this topic interesting you might want to look at 
Hamsci @ Googlegroups.


Bob - wd6dod

--
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/070d8479-00df-9673-db11-711805795ff7%40llorenzini.com.

Re: [weewx-user] How to extract graphs from a specific date?

2022-01-17 Thread Tom Keffer

You can give the utility wee_reports
 with a
timestamp. For example, graphs of 2022-01-01 UTC would be

*wee_reports /etc/weewx/weewx.conf 1640998800*

Because the timestamp is a positional argument normally found in the 2nd
position, you'll have to give the path to the configuration file in the
first position.

Use epochconverter.com to figure out what timestamp you need.


On Mon, Jan 17, 2022 at 6:26 AM weerman  wrote:

> Good afternoon,
>
> I would like to extract the mini graphs for a specific date e.g. for
> 2022-01-01,
> so that i can see e.g. the barometer curve for that day from 00:00 to
> 23:55 and the graph is named and saved with the corresponding time stamp
> e.g. barometer_2022-01-01.
>
> Is that possible with weewx?
>
> Many thanks in advance
>
> Georg
>
>
> --
> 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/97b1f212-719d-427d-9a5e-b3d504769a95n%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEDdJt%2BHq2Yk5jGCY_HPtELK98_4eOSemP%3DtNQqbJ9s84w%40mail.gmail.com.

[weewx-user] How to extract graphs from a specific date?

2022-01-17 Thread weerman

Good afternoon,

I would like to extract the mini graphs for a specific date e.g. for 
2022-01-01,
so that i can see e.g. the barometer curve for that day from 00:00 to 23:55 
and the graph is named and saved with the corresponding time stamp e.g. 
barometer_2022-01-01.

Is that possible with weewx?

Many thanks in advance

Georg


-- 
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/97b1f212-719d-427d-9a5e-b3d504769a95n%40googlegroups.com.

[weewx-user] Storing Text as a record, wee_import and mysql UPDATE

2022-01-17 Thread Glenn McKechnie

Working with TEXT records.

I've gone through the wiki entry
https://github.com/weewx/weewx/wiki/Storing-text-in-the-database
and that all works well. I can add TEXT to the database and display it
in the weewx skin. So far so good.

Using a modified filepile.py, I can add what I want via the new_archive
record hook. What I can't seem to do is add historical data that is in
TEXT form, via weewx. Fair enough, it makes sense.

I figured wee_import may be a solution so I crafted a csv file and used
wee_import but it baulks on the text field.  The csv files,
/var/tmp/weewxaddnotes.csv has the contents...

timestamp,extraTemp1,extraTemp2,ANComment
1641729300,23.0,22.0,"Test.\\nThen test again"

It appears to be wanting a weewx_unit_name and I'm missing a clue stick.
I can't find a name that it will accept without error. If  the
weewx_unit_name field is left blank (only the csv_field_name is given)
it gives the following.

Obtaining raw import data for period 1 ...
 Unable to parse source-to-WeeWX field map.
 No units specified for source field 'ANComment' in /home/weewx/csv.conf.
 Nothing done, exiting.

Which makes sense as I had the following...

[[FieldMap]]
dateTime= timestamp, unix_epoch
interval=
barometer   =
pressure=
altimeter   =
inTemp  =
outTemp =
extraTemp1  = extraTemp1, degree_C
extraTemp2  = extraTemp2, degree_C
ANComment   = ANComment

If I tell wee_imports to ignore the ANComment entry, as follows...
ANComment   =
then everything else imports as expected so it's falling over on the
ANComment field

ignore_invalid_data in the csv.conf file is tantalizing close (a numeric
field containing non-numeric data) but I don't want it skipped or
halted. I want it accepted.

Can I write anything into that 2nd field that will allow a TEXT entry to
skip the conversion process, and allow it to be written as-is to the
database?

On reflection, even if I can use wee_import to add the data I want. I
need to get it correct and complete the first time as once a RECORD is
written (and all it's fields filled) then I can't update it later
without going the manual route as weewx appears to be missing an inbuilt
sql UPDATE archive method. That or I can't find it.

And, that's probably so we don't shoot ourselves in the foot.

But it sure would be nice to write a historical record using weewx or
preferably wee_import (with all their built in sanity checks) and then,
if needed later, be able to update any missing fields, or correct errant
values without going back to the command line.

I understand the risk of blindly updating existing records, but in this
case they are all known empty or new fields, and if they do have
something in them then it needs changing anyway!
Caveat Emptor or something along those lines! :-)


As an aside. I'm doing this as I have a whole host of manual rain
records that should be entered as they are sanity checks on the
automatic gauges, weewx seems as good a place as any to store them.
At the same time I'll be adding extraTemp values that I've recorded
from the haystack.
It'd be nice to plot them, and change them, as they use existing
fields - extraTemp1 etc.

Along with that, a TEXT comment as to why some readings appear as they
do would be useful, or where the floods were after the recent epic
rainfall, or why the rain values appear to be stuffed, or which area of
the haystack the probe is at.
The latest Tongan earthquake is probably another example given the
recent barometric burps it caused.

The possibilities expand as I write.
So I better go.

But... In summary.

wee_import appears to baulk on the new add TEXT method. Is there a quick
fix?

The ability to sql UPDATE any historical weewx record would be useful. 1
or many RECORD fields at a time.

Individual confirmations not required. Other than accepting a one-time
answer that; 'yes', I will bandage my own toes and blame no-one else if
it backfires, because we always have our backups.

Ha! Perhaps a csv.conf entry named pieces_are_all_yours with a default
of no? Changing to 'yes' will 'turn on' the UPDATE method. ;-)


-- 

Cheers
  Glenn

 rorpi - read only raspberry pi & various weewx addons
 https://github.com/glennmckechnie

-- 
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/20220117131349.322f6yi3nbpn6bcq%40gmail.com.
# EXAMPLE CONFIGURATION FILE FOR IMPORTING FROM CSV FILES
#
# Copyright (c) 2009-2019 Tom Keffer  and Gary Roderick.
# See the file LICENSE.txt for your rights.

##

# Specify the source. Available options are:
#   CSV - import obs from a single CSV format file
#

Re: [weewx-user] safety of wind instruments on metal pole on roof?

Re: [weewx-user] safety of wind instruments on metal pole on roof?

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

[weewx-user] Re: When did the blast wave of the eruption "hit" your station?

[weewx-user] Re: When did the blast wave of the eruption "hit" your station?

Re: [weewx-user] Re: Storing Text as a record, wee_import and mysql UPDATE

[weewx-user] Re: Storing Text as a record, wee_import and mysql UPDATE

[weewx-user] Re: safety of wind instruments on metal pole on roof?

[weewx-user] safety of wind instruments on metal pole on roof?

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

Re: [weewx-user] When did the blast wave of the eruption "hit" your station?

Re: [weewx-user] How to extract graphs from a specific date?

[weewx-user] How to extract graphs from a specific date?

[weewx-user] Storing Text as a record, wee_import and mysql UPDATE

15 matches

Site Navigation

Mail list logo

Footer information