OK, should have the first cut of the WeatherCat section of wee_import 
portion of the Utilities Guides done today. Will post a link once done, 
check back before you do the import as the Utilities Guide will be an 
easier read than comments in a file.

Gary

On Friday, 15 May 2020 03:04:37 UTC+10, Ville Helander wrote:
>
> Good to hear that email was send succesfully.
>
> I try to get time on weekend to test it, I can make whole new virtual 
> machine to try that import. 
>
> Since yesterday I had to take my laptop (Macbook pro from 2016 with very 
> shitty keyboard) to repair shop and have to work with space computer so it 
> is not so easy, but I think I can locally attach keyboard and monitor to my 
> server and try it locally.
>
> I answer how thinks go.
>
> -Ville-
>  
>
> gjr80 <[email protected] <javascript:>> kirjoitti 13.5.2020 kello 17.36:
>
> 
> Ville,
>
> I received all of your post in the email summary, think the embedded image 
> may have caused some hiccups for google groups.
>
> I have yet to write the weathercat instructions for the Utilities Guide 
> <http://weewx.com/docs/utilities.htm> but they will be very similar to 
> the Cumulus <http://weewx.com/docs/utilities.htm#Importing_from_Cumulus> 
> and Weather Display 
> <http://weewx.com/docs/utilities.htm#Importing_from_Weather_Display> 
> sections, the process will be very similar so you may get some good 
> background by reading those sections.
>
> The easiest was to use the weathercat import and not interfere with your 
> current install is to clone the WeeWX Github development branch and run 
> wee_import from there. Instructions as follows:
>
> 1. install git if not already installed:
>
> $ sudo apt-get install git
>
> 2. create a directory in which the WeeWX repo will be cloned and change to 
> that directory:
>
> $ mkdir /var/tmp/src
> $ cd /var/tmp/src
>
> 3. clone the development branch of the WeeWX GitHub repo:
>
> $ git clone -b development https://github.com/weewx/weewx
>
> 4. check wee_import works:
>
> $ sudo PYTHONPATH=/var/tmp/src/weewx/bin /var/tmp/src/weewx/bin/wee_import 
> --help
> $ sudo PYTHONPATH=/var/tmp/src/weewx/bin /var/tmp/src/weewx/bin/wee_import 
> --version
>
> you should see the wee_import help and the version should be 0.5
>
> 5. copy the example weathercat import config file to /var/tmp:
>
> $ cp /var/tmp/src/weewx/util/import/weathercat-example.conf /var/tmp/wcat.
> conf
>
> 6. edit /var/tmp/wcat.conf and have a read through the settings and the 
> comments. Change settings as required. Likely you will only need to change 
> the directory setting, the interval setting and perhaps the [[Units]] 
> settings. The directory setting should be the path to the directory 
> containing the year directories containing your .cat files. The interval 
> setting should be set to the interval used in the .cat files, in the .cat 
> files I have seen this has been 1 minute so I have used interval = 1. 
> Change the [[Units]] settings to suit the data in your .cat files, 
> remember the setting must use WeeWX unit codes, the comments should help 
> you.
>
> 7. stop WeeWX and backup your database
>
> 8. first try a dry run, the import command will look something like:
>
> $ sudo PYTHONPATH=/var/tmp/src/weewx/bin /var/tmp/src/weewx/bin/wee_import 
> --config=/home/weewx/weewx.conf --import-config=/var/tmp/wcat.conf --dry-
> run
>
> You need to use your existing weewx.conf, I have assumed it is in 
> /home/weewx, depending on your install it might be in /etc/weewx, change 
> as required. You will likely see a lot of warnings indicating a field was 
> mapped but no data was found, this is due to the fields that are in the 
> wee_import .cat field map but for which there is no data in your .cat 
> files, mostly it is the less common fields such as soil moisture, leaf 
> temperature etc. Unless there are obvious discrepancies you can ignore 
> these. You can suppress the warnings using the optional 
> --suppress-warnings command line option. 
>
> I suggest that for your first dry run import just have a few months of 
> .cat files in your import directory, or limit your import with --from and 
> --to command line options, otherwise you might be waiting for some time.
>
> 9. if the dry run goes OK do a live import by removing the --dry-run 
> command line option.
>
> 10. finally, you can remove the trial code code using:
>
> $ rm -R /var/tmp/src
>
> Any problems/issues/feedback please let me know.
>
> Gary
>
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/zc4atfmQIco/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/814c912a-06db-452f-ae7c-fe2ce7907aaa%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/814c912a-06db-452f-ae7c-fe2ce7907aaa%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/ca34961a-44af-4d36-891a-39ab8d61071e%40googlegroups.com.

Reply via email to