You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to weewx-user
gw1000 default field mapping: 24havpm251 from the interface makes sense - used as a string and meaning ’24 hours average PM2.5 id#1’ - but passing it through to weewx makes cheetah tags like '$current.24havpm21.raw' and that leading digit on a field is a bit iffy
i suggest aqiPm251 instead: ‘Air Quality Index for PM2.5 id#1’. naming is extendable to gas measures etc
gjr80
unread,
Aug 3, 2020, 10:22:40 AM8/3/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to weewx-user
No not too keen on fields starting with number myself. Will have another look at the default field names, I have two strong preferences though. First, fields that do not map to WeeWX schema fields should retain as much of their GW1000 description as possible. Second, consistent naming conventions are used.