Warnings: some suggestions #33

Closed
opened 1 year ago by arwagner · 7 comments
arwagner commented 1 year ago

I would like to suggest to consider the following additions wrt the warnings:

  • Notify a known warning for the current area in the wether report. An idea would be to bg-colour e.g. the date header in yellow or orange. Or, colour the value that got a warning, e.g. wind, temperature, rain.
  • It would be nice if I could select the warnings for the region easily. (Following the above, one might just tap the coloured date, or just a day/hour entry to jump to it?) Note: at least for me it is currently quite hard to hit my area in the map. Too clumsy finders and too small a map in destructive interference ;)
  • A note in the widget about known warnings might be nice as well. No need to be as bold as the Warnwetter-app. Probably just bg-colouring the region name (obeying the transparancy setting for the widget?
  • Add coastal area warnings might be helpful for all coastal activities (they cover the area as far as Helgoland ;)
  • Add sea area warnings: would cover most parts of the north sea ("behind Helgoland") and baltic.

BTW: I do like the data transfer economy of the app quite a bit. IOW I would not go for "get the warnings every so and so many minutes" or the like. One could think of including a warnings update in a data update, IOW ask for it explicitly. Probably, even an option: if you get data every n hours [ ] include warnings.

I would like to suggest to consider the following additions wrt the warnings: - Notify a known warning for the current area in the wether report. An idea would be to bg-colour e.g. the date header in yellow or orange. Or, colour the value that got a warning, e.g. wind, temperature, rain. - It would be nice if I could select the warnings for the region easily. (Following the above, one might just tap the coloured date, or just a day/hour entry to jump to it?) Note: at least for me it is currently quite hard to hit my area in the map. Too clumsy finders and too small a map in destructive interference ;) - A note in the widget about known warnings might be nice as well. No need to be as bold as the `Warnwetter`-app. Probably just bg-colouring the region name (obeying the transparancy setting for the widget? - Add coastal area warnings might be helpful for all coastal activities (they cover the area as far as Helgoland ;) - Add sea area warnings: would cover most parts of the north sea ("behind Helgoland") and baltic. BTW: I do like the data transfer economy of the app quite a bit. IOW I would not go for "get the warnings every so and so many minutes" or the like. One could think of including a warnings update in a data update, IOW _ask for it explicitly_. Probably, even an option: if you get data every _n_ hours `[ ] include warnings`.
Starfish added the
enhancement
label 11 months ago
Owner

Most of the features are already implemented and will be in the next version. Lets discuss this:

  1. date header changes color: this might be not prominent enough, currently a warning icon appears (in the color of the warning, meaning yellow=minor, orange=moderate, red=severe; I guess purple is extreme, but not spotted yet in the open data). Tapping on the warning symbol shows the heading of the warning (e.g. "Warnung vor Sturmböen").

  2. see 1; in the warnings activity, warnings that apply for the selected weather station have a colored background now, so that you easily see that they apply to you.

  3. on the map, a pin now indicates the position of the selected weather station.

  4. putting warnings in widgets might come later. The DWD sometimes changes warnings quite frequently, so you would need to poll them at least every 30 minutes or so. This would be a heavy penalty on battery, download amount etc., so I am not sure if this is worth it.

There is an other issue: as the popularity of my app obviously increased, I get quite a lot of reports about widgets not updating. I believe that my update-code is quite bullet-proof, and widgets really should update at least every 30 minutes. A lot of people use some wired battery savers, and some stock roms have them, too. They simply kill activities, leading to failed updates of data & widgets.

I am not sure if it would not be safer to keep warnings out of the widgets at all. Still thinking about it.

  1. Sea warnings: I can only draw polygons on the map when there is polygon data. Not all warnings have geo-polygons. Especially, the sea area warnings do not have them. It would not be too difficult to catch those few areas by manual polygons, but would need to be done seperately.

For a preview, see https://kaffeemitkoffein.de/nextcloud/index.php/s/4SXHaLxLSmFd8Ri

(edit: link corrected)

Most of the features are already implemented and will be in the next version. Lets discuss this: 1. date header changes color: this might be not prominent enough, currently a warning icon appears (in the color of the warning, meaning yellow=*minor*, orange=*moderate*, red=*severe*; I guess purple is *extreme*, but not spotted yet in the open data). Tapping on the warning symbol shows the heading of the warning (e.g. "Warnung vor Sturmböen"). 2. see 1; in the warnings activity, warnings that apply for the selected weather station have a colored background now, so that you easily see that they apply to you. 3. on the map, a pin now indicates the position of the selected weather station. 4. putting warnings in widgets might come later. The DWD sometimes changes warnings quite frequently, so you would need to poll them at least every 30 minutes or so. This would be a heavy penalty on battery, download amount etc., so I am not sure if this is worth it. There is an other issue: as the popularity of my app obviously increased, I get quite a lot of reports about widgets not updating. I believe that my update-code is quite bullet-proof, and widgets really should update *at least* every 30 minutes. A lot of people use some wired battery savers, and some stock roms have them, too. They simply kill activities, leading to failed updates of data & widgets. I am not sure if it would not be safer to keep warnings out of the widgets at all. Still thinking about it. 5. Sea warnings: I can only draw polygons on the map when there is polygon data. Not all warnings have geo-polygons. Especially, the sea area warnings do not have them. It would not be too difficult to catch those few areas by manual polygons, but would need to be done seperately. For a preview, see https://kaffeemitkoffein.de/nextcloud/index.php/s/4SXHaLxLSmFd8Ri (edit: link corrected)
Poster

1.-3. sound great. :) I'll stary tuned.

putting warnings in widgets might come later. The DWD sometimes changes warnings quite frequently, so you would need to poll them at least every 30 minutes or so. This would be a heavy penalty on battery, download amount etc., so I am not sure if this is worth it.

Get the point. Maybe it is too difficult to transport to the user: this warning was issued 6h ago, if it may be relevant for you now, you should refresh manually now. And be aware that we refresh this only every 6h at max. (This was my thinking: oh, there is something I should check now, refresh.)

I am not sure if it would not be safer to keep warnings out of the widgets at all.

So indeed, it was probably a bad idea to consider the widget. May give "false security".

A lot of people use some wired battery savers, and some stock roms have them, too. They simply kill activities, leading to failed updates of data & widgets.

I'm no programmer, but I there was something sounding quite similar for background activities in Trail-Sense which I use as a barograph. Don't know if this is of help but the author introduced quite some changes to work around a number of these. See. e.g. https://github.com/kylecorry31/Trail-Sense/issues/212 as a starting point.

Sea warnings: I can only draw polygons on the map when there is polygon data.

Ic. Don't know if I have them handy. I'll have a look.

1.-3. sound great. :) I'll stary tuned. > putting warnings in widgets might come later. The DWD sometimes changes warnings quite frequently, so you would need to poll them at least every 30 minutes or so. This would be a heavy penalty on battery, download amount etc., so I am not sure if this is worth it. Get the point. Maybe it is too difficult to transport to the user: this warning was issued 6h ago, if it may be relevant for you _now_, you should refresh manually _now_. And be aware that we refresh this only every 6h at max. (This was my thinking: oh, there is something I should check now, refresh.) > I am not sure if it would not be safer to keep warnings out of the widgets at all. So indeed, it was probably a bad idea to consider the widget. May give "false security". > A lot of people use some wired battery savers, and some stock roms have them, too. They simply kill activities, leading to failed updates of data & widgets. I'm no programmer, but I there was something sounding quite similar for background activities in [Trail-Sense](https://github.com/kylecorry31/Trail-Sense) which I use as a barograph. Don't know if this is of help but the author introduced quite some changes to work around a number of these. See. e.g. https://github.com/kylecorry31/Trail-Sense/issues/212 as a starting point. > Sea warnings: I can only draw polygons on the map when there is polygon data. Ic. Don't know if I have them handy. I'll have a look.
Poster

Adding some documentation to 1:

  • Minor: Yellow
  • Moderate: Orange
  • Severe: Red
  • Extreme: Violet

This is outlined in https://www.dwd.de/DE/wetter/warnungen_aktuell/objekt_einbindung/einbindung_karten_geowebservice.pdf?__blob=publicationFile&v=11 p.17.

Adding some documentation to 1: - Minor: Yellow - Moderate: Orange - Severe: Red - Extreme: Violet This is outlined in https://www.dwd.de/DE/wetter/warnungen_aktuell/objekt_einbindung/einbindung_karten_geowebservice.pdf?__blob=publicationFile&v=11 p.17.
Poster

As to 5: "Sea warnings". I wonder if the geoservice is of use for the polygon information. The following URLs return XML with some polygon information. I'm absolutely no expert here wrt the ploygon information. But the textual part sounds very familiar.

Maybe they are overly complex though as they really follow the coast and all the islands etc.

As to 5: "Sea warnings". I wonder if the geoservice is of use for the polygon information. The following URLs return XML with some polygon information. I'm absolutely no expert here wrt the ploygon information. But the textual part sounds very familiar. - [Coastal Areas](https://brz-maps.dwd.de/geoserver/dwd/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=dwd%3AWarngebiete_Kueste&maxFeatures=50) - [Sea Areas](https://brz-maps.dwd.de/geoserver/dwd/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=dwd%3AWarngebiete_See&maxFeatures=50) Maybe they are overly complex though as they really follow the coast and all the islands etc.
Owner

Thanks for this hint!

Copyright seems ok ( see https://brz-maps.dwd.de/geoserver/www/copyright.html). Transferring/importing the xml files would be some work.

I am not sure how to use this, the map of Germany in the app only shows a few sea areas, not all of them. Put them in to the mini-map (visible in landscape mode only)? Not sure how to display them best at the moment.

Thanks for this hint! Copyright seems ok ( see https://brz-maps.dwd.de/geoserver/www/copyright.html). Transferring/importing the xml files would be some work. I am not sure how to use this, the map of Germany in the app only shows a few sea areas, not all of them. Put them in to the mini-map (visible in landscape mode only)? Not sure how to display them best at the moment.
Poster

Thanks for this hint!

You're welcome.

Transferring/importing the xml files would be some work.

I'd guess that. It might be worthwhile as the same service offers quite a few area polygons on various levels, e.g. "Gemeinden" etc. Don't know of your plans here. I just remember that in #24 we came across the missing boundaries already.

I am not sure how to use this, the map of Germany in the app only shows a few sea areas, not all of them

It may depend on your plans for the map (should it eventually allow to zoom in/out eg.). As long as it is a static bitmap like now, I guess that on the current warning map you'll mainly need the one for German Bight, probably Belte und Sund, W and S Baltic. Indeed, most should be covered by the coastal areas. However, sometimes you have a warning for say German Bight, but none for the coastal areas. And a stiff wind out there might build up some sea. (Better safe than sorry?)

Still, even if they are not on the map for my funny area of interest it would be nice if I could call up current sea area and coastal warnings in text, even if they are not on the map. Usually, you'd know where e.g. Viking is located (e.g. via Bordwetterkarte Nr.9 or similar publications.)

> Thanks for this hint! You're welcome. > Transferring/importing the xml files would be some work. I'd guess that. It might be worthwhile as the same service offers quite a few area polygons on various levels, e.g. "Gemeinden" etc. Don't know of your plans here. I just remember that in #24 we came across the missing boundaries already. > I am not sure how to use this, the map of Germany in the app only shows a few sea areas, not all of them It may depend on your plans for the map (should it eventually allow to zoom in/out eg.). As long as it is a static bitmap like now, I guess that on the current warning map you'll mainly need the one for _German Bight_, probably _Belte und Sund_, _W and S Baltic_. Indeed, most should be covered by the coastal areas. However, sometimes you have a warning for say German Bight, but none for the coastal areas. And a stiff wind out there might build up some sea. (Better safe than sorry?) Still, even if they are not on the map for my funny area of interest it would be nice if I could call up current sea area and coastal warnings in text, even if they are not on the map. Usually, you'd know where e.g. Viking is located (e.g. via [Bordwetterkarte Nr.9](https://www.dwd.de/DE/leistungen/lehrmittel/bordwetterkarte_nr9.html) or similar publications.)
Owner

Closed, related to #53 and solved by 9f5a4f9420, warning in sea areas and costal areas now display correctly

Closed, related to https://codeberg.org/Starfish/TinyWeatherForecastGermany/issues/53#issuecomment-201346 and solved by https://codeberg.org/Starfish/TinyWeatherForecastGermany/commit/9f5a4f9420036f8351f63019be16c5b34f7c765f, warning in sea areas and costal areas now display correctly
Starfish closed this issue 8 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.