Thank you very much for fixing this issue - v28.0.3 looks great on the iPhone 12 Pro!!!!
Also, thank you for the new iOS 14 widget!
Keep up the great work... 👍
Thanks for continuing to look into this issue.
If this is in fact the correct behaviour, why is it that the data from both overlapping sources is in fact displayed correctly in the overlapping region in the first frame? It is only in the second frame, when the Environment Canada data in the non-overlapping regions becomes hatched, that the EC data in the overlapping region disappears.
It is this inconsistency in the behaviour of the overlapping data that was leading me to believe that this issue is bug and not the intended behaviour.
@korina this is exactly the problem - in my example it is not behaving the way you describe it should be. In the regions I highlighted, the Environment Canada data disappears in the latest time stamp (when the rest of the visible Environment Canada data become hatched). If it were in fact showing the maximum value of precipitation, this data would remain.
The issue is clear when you see the difference between the two images, or between the two time stamps in the video. A large portion of the Environment Canada data in the highlighted region simply disappears when the rest of the data becomes hatched. This clearly seems to be a bug related to when one part of the overlap area becomes hatched/striped. Before this data becomes hatched/striped, everything is behaving as it should.
I have emailed you an additional example. Thanks for continuing to look into this issue.
@korina I know what the stripped/hatched area means. Please read my post in detail. It explains the issue I am referring to.
@korina my apologies, I linked the wrong file. It should be working now.
There seems to be an issue in areas of weather radar overlap between adjacent weather data providers (let's say providers A and B) that causes the part of A's radar image that overlaps with B to disappear when A's data expires and becomes hatched elsewhere.
Please see this video for an example. Running horizontally across the middle of this video is the 49th parallel, the border between Canada and the US. Data north of the border is provided by Environment Canada, and south of the border by NOAA. Here in Vancouver, we are close enough to the border that we are covered by both weather radar feeds. Watch the time slider along the bottom of the screen. You'll notice that in the most current image (end of slider), the Environment Canada data becomes hatched (expired, in relation to the NOAA data, I presume), and at the same time a large portion of the radar image around Vancouver disappears. This is the Environment Canada data that's disappeared, even though it remains hatched in the rest of the visible area. It should, therefore, appear hatched here too.
I believe that there is some kind of graphical issue that prevents the hatched weather data from displaying correctly in areas where there is an overlap with an adjacent provider.
Please let me know if you require any further info!
@Korina did you receive my latest comments?
@korina as I mentioned previously, the blue dot which represents my current location is correct, which means that iOS is in fact providing my correct location. The issue is that Windy is launching at a location that is not centred on the blue dot.
This seems to be a Windy issue, not iOS. I have emailed you an updated screen recording to demonstrate the location of the blue dot.
@korina thanks, Korina. I’ve replied to your email, but will give the info here as well...
I am running Windy 27.3.2 on an iPhone 12 Pro with iOS 14.3.
I’ll also mention that I have the radar set as the start-up layer.
I never saw this issue prior to Windy version 27.3.1.
@korina just an update to let you know that this issue has been happening not just after a force quit, but also when launching the app after not using it for a while.
Did you receive my email with the screen recording?
@korina email sent with subject “ATTN: Korina”.
@ivo sorry, I guess I misunderstood your previous reply that it had already been fixed and submitted to Apple, and we were just waiting for Apple to approve it.
Can we expect the fix in the next update? I don’t mean to be impatient, but this particular UI issue really affects the usability of the app...