-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forecast coordinates are ridiculously accurate #191
Comments
It seems that these are the exact coordinates provided to WeeWX in weewx.conf at I added a format of 4 decimal places in - for $wloc
+ #set $wloc_list = $wloc.split(',')
+ #set $format_string = "{0:.3f}"
+ for $format_string.format($float($wloc_list[0])), $format_string.format($float($wloc_list[1])) See ad9dcbe Feel free to test the change by editing the template file! Otherwise, it will be included in the next release. |
Thanks! I wasn't sure if the coords were from weewx.conf; I thought I had tested publishing after updating my weewx.conf, but I must have failed a step. In any case, I tried the code and it only prints three places which should look better under the Forecast table. |
Yes, sorry I meant to write "3 places" |
Hi @Daveiano, weewx[2270] ERROR weewx.cheetahgenerator: Evaluation of template /etc/weewx/skins/weewx-wdc/index.html.tmpl failed with exception '<class 'Val |
Hi @dave9997, the error was also noticed when the last version was released, see here: #218 (comment) Here is a quick fix that should help to solve the issue - these changes will be included in the next release: 884be1a Background: Every forecast provider provides the data in another format. |
Describe the bug
I am using the OWM forecast; when the forecast is generated the page incudes GPS coordinates with 10+ decimal places of precision. These coordinates are too accurate to be useful; all that's needed is a general area and that can be done with four places coordinate precision like the page footer.
Expected behavior
~3-4 decimal places of precision
Screenshots
The text was updated successfully, but these errors were encountered: