Initial commit

AIR_QUALITY_MODULES.md

@@ -0,0 +1,11 @@
+The new air qualiy modules require a database source of particle concentration data. The new WeeWX 4.x.x extended database schema includes fields for PM1.0, PM2.5 and PM10.0. Due to the variety of air quality measuring devices that are now available, it is beyond the remit of these instructions to describe in detail the process for each type of sensor. It is assumed for the purposes of these instructions that you are using the extended database and the particle concentration fields are being populated. The new modules are as follows: -
+
+Module 1. Top Line Module WORLD (US EPA) AQI PM2.5 and requires the database field pm2_5 to be populated. This modules gives a read out for the Global AQI and NOW which is based on the United States Environmental Protection Agency method of calculation.
+
+Module 2. Top Line Module UK DAQI PM2.5 and PM10 which requires both the pm2_5 and pm10_0 database fields to be populated. The United Kingdom Daily Air Quality Index for both 2.5 and 10.0 particle extensions are displayed.
+
+Both these modules have information pop-up windows when the centre of a module is clicked. Selection of these modules is facilitated from the Weather34 settings page.
+
+Module 3. This is a regular sized model and again selected from the Weather34 settings page. It displays the World (US EPA) AQI PM2.5 figure. Links to charts for PM2.5 and PM10.0 particle concentrations can be found at the base of this module. 
+
+

CHANGE_LOG-closed-08-08-20.md

@@ -0,0 +1,92 @@
+# Change Log
+
+**Version W34-HC-IMJD-2.0.0**
+
+1. Changes for WeeWX 4.0 new extended database schema
+2. Protection code for empty strings
+3. Added energy to lightning module display
+4. CSS additions in preparation for future planned air quality module options
+5. Updated settings.php to next version code **W34-HC-IMJD-2.0.0**
+6. Added lightning chart links to index.php
+7. Code cleanup lightning variables & css tweaks for lightning
+8. Added lightning monthly chart
+9. Add missing y axis label for lightning
+10. Additional lightning label changes
+11. Readme up issue
+12. Removed duplicated documents in www folder
+13. Adjust location of miles widget
+14. Reduce race condition on update section
+15. wind_gust_60min missing and wind conversions in the wrong file
+16. Cloud height display reversed
+17. CSS adjustment for airqualitymodule.php
+18. Corrected issues with RT windrose chart
+19. Further air quality module CSS adjustments
+20. Air Quality Module updated
+21. AQI info pop up added (aqipopup.php, aqi_info.php)
+22. World AQI Top Row Module added (worldaqitop.php)
+23. UK AQI Top Row added (daqitop.php)
+24. Added cloudbase data to archivedata.php.tmpl
+25. w34CombineData.php now uses WeeWX cloud base data 26 Fixed cloud base unit conversion in currentconditions.w34.php
+26. Use lasttime for lightning strike
+27. Created airqualitydata.php.tmpl
+28. Added [[[AIRQUALITYDATA]]] to Weather34 skin.conf
+29. Dual windrose plots on one iframe
+30. Day plots for multiple plots per page
+31. Cloudbase calculation works on US units database also
+32. Month/Year Windrose Gust use GustSpeed from db
+33. Windrose Gust tweaks and using 10min gust for display
+34. Fix chk_lightning_count option
+35. Remove unused config entry
+36. Weewx IP in realtime.txt for day plots
+37. Remove weewxbinpath from plots_config.js
+38. Change to make lightning time ago correct
+39. Round 2 Day Plots communication
+40. Use 10min dir avg and 10min gust avg for rose
+41. Config option to disable day plots
+42. New Cloud Cover percent display
+43. New Cloud Cover Chart
+44. Misc changes for Cloud Cover and chmod for sat images
+45. Added cloud cover unit to settings.php
+46. Renamed RemoteWebServer and realtime.txt
+47. Added text to cloud cover chart
+48. Added additional hidden fields for new hidden variables to ensure they are not removed from settings1.php when settings page is saved.
+49. Remove scroll bar from temp almanac
+50. Corrected path in Weather34CloudCover stanza in the install config files
+51. Added % cloud cover chart link to current conditions module
+52. Rsync w34realtime.txt to remote web servers
+53. Rsync of json directory is now possible
+54. Remove duplicate filename config entries in W34 sections
+55. Added green, yellow, orange and red advisory alert triangles to shared.php
+56. Inserted space in cloud cover link index.php
+57. Fixed white plot background for cloud cover chart
+58. Buttons styles
+59. W34 WebServer always enabled remove config section from weewx conf
+60. Send webserver ip address on index.php page load
+61. currentconditionsw34.php adjusted layout
+62. Support multiple remote web servers for one weewx machine
+63. Auto theme for dark and light theme based on sunrise & sunset
+64. Added delete of config entries to w34 installer
+65. Added advisory_extended.php
+66. Added alert fields to easyW34skinSetup.php
+67. $lat and $lon added to auto theme index.php
+68. settings1.default.php additional variables for Meteoalarm added
+69. Additional updates to easyW34skinSetup.php for Meteoalarm filelds
+70. Hayes wind speed chart and range selector for radial charts
+71. index.php edited module links
+72. Protection code around lightningSum_json
+73. Protection code for degrees to compass value
+74. Cloud Cover Radial chart added
+75. readme.md Updated screen shots
+76. Updated radial chart screen shot
+77. Added polar chart for tempallplot
+78. Use either weewx 3.x or 4.x logging
+79. Allow polar charts to use different dates using input selector
+80. User is now prompted with the Python Version the install will be run
+81. Re-worked cloud cover
+82. Added night and day icon selection to cloud conditions
+83. easyW34skinSetup.php MB platform not required
+84. Added $theme1 and $al_ip to settings1.default.php
+85. Added missing cloud cover variable to w34CombinedData.php
+86. Current conditions module Icons and descriptions now match
+87. Addition of oktas to cloud coverage in current conditions module
+88. Readme and installation instructions updated

CHANGE_LOG.md

@@ -0,0 +1,8 @@
+# Change Log
+
+**Version W34-HC-IMJD-3.0.0**
+
+1. weather34.py. Change for time out in P3
+2. weather34.py corrected hard coded path
+3. w34CombinedData.php try catch around loading archivedata.php
+4. Corrected font weight WU large forecast in light theme

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,15 @@
+When contributing ideas and improvements it is important to crosscheck the suggested ideas in all metrics , many times I see ideas
+not working across all possibilities. many issues can arise due to various hardware used, interval updates, cross metric useage where
+perhaps celsius is used with non metric variables. Its not easy to capture them all and often what may work perfectly well for you
+does NOT always work well for others.
+
+So I ask kindly you to think outside your own enviroment and what would the outcome be if you
+were positioned in a different climate region. examples you may reside in a climate that gets little rainfall or totally the opposite like a monsoon region or extreme high temperatures and low humidity or vice versa low temperature high humidity.
+
+All constructive ideas are always considered and you may see an issue or forward an idea but it may take time to implement as it needs to be crossed checked. weather templates due to the nature of various hardware,metrics are not like your simple website , blogging templates they require a lot of focus on finer detail that may not always be available as the nature of our weather changes from day to day , month to month , for example you have an idea that is put together in your winter season but it is easy to overlook what the output may be in the warmer seasons ..
+
+Ideas based on iframe scraping data from other websites will never be implemented ,these type of scripts if not structured right can have a large impact of the performance(loading) .Weather34 has avoided these since the beginning way back in 2015 .I know it is a personal thing and some may want to display animated charts scrapped from commercial or third party sites but if that third party site has downtime or performance issues that is carried over to your website performance .Any third party data used in the template is generated in the background via official API useage where it is permitted on agreement to use the
+data .Third party scraping of graphics,maps,radars etc are not used based on above..Any API useage even official API methods always has the risk of downtime however the benefit of using the official API methods is normally downtime is minimal ..So in short no ideas based on scraping will be implemented ..However if you want to do this for your pesonal use there is no reason why you cant its your website,your domain and so on.
+
+
+

EUROPEAN_WEATHER_ALERTS.md

@@ -0,0 +1,59 @@
+This new function is only available for Geographical European users and is based on warning data published by Meteoalarm.
+
+Settings can be found in the web services section of the Weather34 settings page. To ascertain your own alerts location go to https://www.meteoalarm.eu and select your country and region from the map and make a note of the the URL that you arrive at. From this URL you will see your country and region codes.
+
+      For example, the URL for the UK London and South East region is https://www.meteoalarm.eu/en_UK/0/0/UK013-London%20&%20South%20East.html
+      From this URL the key piece of information is UK013. Splitting this into UK and 013, produces the country code and region code. The other two pieces of information required by the Weather34 settings page are Update Frequency and local network IP address of the device that is running the software. Include the port address if it is not the default 80. You will also need to select a webservice code string which includes which includes 'al'
+      
+After clicking on save, restart WeeWX to prime the new service.
+
+When an alert is force, a brief description and either a yellow, orange or red warning triangle will appear in the top row advisory module. Clicking on the alert will activate a pop-up window with more details of the alert(s) either in force or about to be in force.
+
+I would welcome Weather34 users' input to code interfaces for othe weather alert systems in othe parts of the Globe to make this a complete service.
+
+Below is a copy of an e-mail to Ken True of saratoga-weather.com outlining the conditions that are required by EUMETNET - MeteoAlarm for public use of the data.
+
+Date: Thu, 11 Sep 2008 11:39:52 +0200
+From: karin buchauer <[email protected]>
+Organization: zamg
+
+Dear Mr True,
+
+you are quite right:
+you can use the material featured on the website, without modifying it, providing the source (link) as well as time and date of issue of the data, as stipulated in the Terms & Conditions.
+
+With best regards,
+Karin Buchauer
+
+
+
+Ken True schrieb:
+> Dear Sirs,
+>
+> I am an amateur weather enthusiast who also writes scripting for other weather enthusiasts to incorporate weather data into their personal, non-commercial weather websites.  Many of my scripts (which I write as a hobby, and are distributed gratis) are in use on personal weather websites worldwide.
+>
+> I've had requests to package the excellent data from www.meteoalarm.eu for weather advisories in EU countries, and before I generate a script for that purpose, I'd like to have your permission to proceed.
+>
+> Your Terms and Conditions page (http://www.meteoalarm.eu/terms.asp?lang=EN ) says:
+>
+> "The material featured on this site is the common property of the Meteoalarm partners, and is subject to copyright protection.
+> The ownership and intellectual rights on all operational and updated awareness and warning information delivered to the Meteoalarm system remain with the Meteoalarm partners who originally delivered this information. The information on this web site may be used freely by the public.
+> Before using information obtained from this server special attention should be given to the date & time of the data and products being displayed.
+> In case this information is re-used: This information shall not be modified in content and the source of the information has always to be displayed as EUMETNET - MeteoAlarm, or if a single country, the providing national Institute (for internet application in all cases in the form of a link to: www.meteoalarm.eu). The time of issue at www.meteoalarm.eu must be count.
+>
+> Third parties producing copyrighted works consisting predominantly of the material of this website must provide notice with such work(s) identifying the source of material incorporated and stating that such material is not subject to copyright protection. Further information can be obtained from this following address: [email protected]"
+>
+> My reading of this implies that you do permit re-use/publishing of the information with attribution and an active link to the source page for the data on your site, and a note that the data is copyrighted by the data providing organization (and not subject to copyright by the 3rd-party website including/displaying the data).  Is that correct?
+>
+> Is it ok with you for me to generate a script for displaying national/regional weather alerts using your data from www.meteoalarm.eu with the appropriate attribution.
+>
+> Please feel free to examine other scripts I've written which use NOAA, Environment Canada, US Geological Services, and temis.nl as data sources (http://saratoga-weather.org/scripts.php ).
+>
+> Thank you in advance for your response,
+>
+> Best regards,
+> Ken True
+> [email protected]
+> Saratoga, California, USA
+
+