David Schulz <[email protected]> writes: > Battery : *1* Temperature: *22.4 C* Humidity : *59 %* > Wind direction: *205* Wind speed: *0.0 m/s* Gust speed: > *0.0 > m/s* Rainfall : *13.2 mm* UV : *83* UVI > : *0* Light : *10922.0 lux* Integrity : *CRC* > In my SDR device sensor map I am mapping the UV value to radiation, the UVI > value to UV. Those values seem to be landing in the 'intended' columns and > display nicely in repots with correct values assigned. > > radiation = uv.133.FOWH65BAltPacket > > UV = uv_index.133.FOWH65BAltPacket > > luminosity = light.133.FOWH65BAltPacket > It is the value being reported as 'light' from the sensor that I'm > struggling with. It's currently I'm mapping that value to field I can > physically see in the database called luminosity. That stores data in the > database but the display shows no units and presents with 6 decimal > places.
As I understand it, Radiation is supposed to be the physical quantity "irradiance" in W/m^2, 1000ish at noon under blue sky. UV seems to be some radiometric measurement of just UV, and while that's useful, it is not irradiance. UVI I think you have correct. As I said before, luminosity is not a sensible word in this context. So stop mapping UV to radiation, figure out what UV really is, and add a column, perhaps uv_irradiance if it's in mW/m^2 which I think it might be, but I don't have that kind of hardware. > After some searching through this group, I found the post referenced where > it sounded like there 'should' be a column called 'illuminance' which is > mapped to a group with the same name which uses lux as units. When I make > that mapping, weewx refuses to start - not surprisingly. There are multiple schemas, as I understand it (and I am far from an expert). Original wview, and extended, and then you can add whatever. Read this carefully: https://www.weewx.com/docs/customizing.htm#archive_database Look in bin/schemas in the source. The wview regular schema has UV and radiation. Schema entries do not give units. units are mapped in another file. wview extended adds luminosity. My best guess is that luminosity is a word to mean illuminance, and that it came from a decision in a scheme not in weewx long ago The processing part of the code seems to use illuminance in lux. This is correct. The fineoffset driver converts (bogus but the best you can do) illuminance to radiation and puts that in the radiation column. > So that leaves me with 2 options - assume my database is 'incorrect' and > add a column (wee_database --add-column) called illuminance and remap the > light values to that column. The alternative is to add the existing column > to the illuminance group so it uses the correct unit and I can apply some > formatting. I guess I'm wondering if there are other options, and if not, > which of the methods is the "safest" in terms of playing nice with future > upgrades. My read -- and don't trust me -- is that having luminosity in the schema is a bug, perhaps inherited from wview, and that you want an illuminance column. > I'm just now looking up the command syntax to add a column and I notice > this example from the section on renaming columns - 'wee_database > --rename-column=luminosity --to-name=illuminance'. Maybe not a coincidence > that example is used? That's starting to lok like my third (and best?) > option. That's what I would do, after making 3 backups, one of which is off site :-) > Appreciate any guidance on what the intended design is here. Note that I am really just guessing in places. -- 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/rmi4jtwbxy9.fsf%40s1.lexort.com.
signature.asc
Description: PGP signature
