In my opinion I would say no. Keep weewx doing it's main function - building the database, and use it's secondary function of uploading files to a website or external location such as WU.
I would handle the image retrieval/storage in an independent program set up for handling webcams and grabbing images. I would use an independent Python program to process the images - query the database for overlay information, create a new image, and if necessary put the image in a location where weewx can pick up the modified image file for uploading elsewhere. I personally do not feel that querying the database data for augmenting images should be handled within weewx. On Tuesday, 19 February 2019 04:40:56 UTC+2, rich T wrote: > > I'm able to transpose current data onto a captured image using PIL and > querying the database. It is still a work in progress. Was wondering if > creating a service would be the best way to go forward? > > On Friday, February 1, 2019 at 4:25:28 AM UTC-5, Andrew Elwell wrote: >> >> Hi Folks, >> >> I've just set up a basic webcam (r-pi camera module) and I'd like to >> overlay the wind speed and direction (ideally I'd like to simply >> overlay a wind barb, but suspect my imagemagick-fu isn't strong >> enough) >> >> I've got a couple of days worth of historic images just now (one frame >> every 5 mins with raspistill) and I'd like to pull out the weather >> info at the time of the exif image capture time. >> >> Is this possible (wee_reports or sqlite query?) for historic stuff, >> and whats the simplest way to get 'current conditions' as a machine >> readable file or API call at the time of future image generation? >> >> Many thanks >> >> Andrew >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
