@docbee said in Very poor communication to developers of upload software:

Hi,
as the developer of the Meteobridge SW which quite a few user use to upload data of their PWS to windy, I am largely disappointed that you do not inform me before doing changes in the upload format. The current issue I was pointed to by my customers is that station IDs are now given as alphanumerics, while it was only numerics before. Looks like a small change, but Meteobridge allowed to use numerics only according to previous specs. As a result I got bug reports and frustrated customers.

Is it too much to ask to be informed on changes that impact data upload before you implement those? I see this as rather unprofessional and I am not interested to support unreliable services that impact quality and user experience of my product.

I can totally relate to this, and I’m actually dealing with something similar on my end. I also have the same question about why changes like this aren’t communicated in advance, especially when they directly impact integrations. Even a small shift like moving from numeric to alphanumeric IDs can break assumptions in existing systems, and it ends up causing unnecessary issues for both developers and users.

It’s particularly frustrating when you’re the one fielding bug reports from customers without having any prior notice of the change. I’m also wondering if there’s any official channel or update feed where these kinds of changes are announced ahead of time, because relying on users to discover breaking changes isn’t really sustainable. Would definitely appreciate more transparency and coordination here.

@docbee said in Very poor communication to developers of upload software:

Hi,
as the developer of the Meteobridge SW which quite a few user use to upload data of their PWS to windy, I am largely disappointed that you do not inform me before doing changes in the upload format. The current issue I was pointed to by my customers is that station IDs are now given as alphanumerics, while it was only numerics before. Looks like a small change, but Meteobridge allowed to use numerics only according to previous specs. As a result I got bug reports and frustrated customers.

Is it too much to ask to be informed on changes that impact data upload before you implement those? I see this as rather unprofessional and I am not interested to support unreliable services that impact quality and user experience of my product.

I can totally relate to this, and I’m actually dealing with something similar on my end. I also have the same question about why changes like this aren’t communicated in advance, especially when they directly impact integrations. Even a small shift like moving from numeric to alphanumeric IDs can break assumptions in existing systems, and it ends up causing unnecessary issues for both developers and users.

It’s particularly frustrating when you’re the one fielding bug reports from customers without having any prior notice of the change. I’m also wondering if there’s any official channel or update feed where these kinds of changes are announced ahead of time, because relying on users to discover breaking changes isn’t really sustainable. Would definitely appreciate more transparency and coordination here.

@Coughts1947 said in can I use my iOS subscription on your website?:

Hi,

(how) can I use my iOS subscription on your website?

Thank you very much

I have the same question I’m also wondering if it’s possible to use an existing iOS subscription directly on the website. It would be great to have the flexibility to access the same features across both platforms without having to purchase a separate web subscription.

If anyone knows how to link or verify the iOS subscription for web use, or if this feature is planned for the future, I’d really appreciate some guidance on that.

@benclarkee

Thanks for the clarification! I appreciate the quick response. I must’ve just noticed the difference more prominently today it looked a lot darker than usual, so I wondered if something had changed recently. I’ll check out the 2021 post you mentioned for reference. Thanks again for pointing me in the right direction!

@J42ds said in Colour shading of SO2:

Thanks. I am in Australia (Melbourne). I have never seen so much red on the map. A couple of days ago, the reading at my location was around 1 and the forecast was for a wind change to an Easterly, which would blow the SO2 towards me.

At the moment it’s showing a level of 18 mg/m2, which is way above the forecasted level. (I do understand that this is per m2 and not per m3, so a value for the whole column).

I’m trying to understand where all the extra SO2 has come from. Volcanic activity??

I have the same question — I’ve noticed lately that SO₂ shading on maps looks much darker/more intense than I remember. Some users have pointed out the same visual shift.

@Valencia_WX said in Video ONE TIME ANIMATION BUG:

I found a bug that makes the first frame of ONE TIME ANIMATION look like this. This occurs 100% of the time i make an animation.

I think its posible to fix this by delying the start recording by 1000ms after the user allows the share screen option on his browser.

Hi,

I’m also encountering this issue right now. The first frame of a one-time animation always looks distorted, exactly as you described. It happens consistently whenever I create an animation.

I agree that delaying the start of the recording by 1000ms after the user allows the screen share in the browser might be a good solution. Hopefully, someone can confirm if this is a viable fix or if there’s another workaround.

Looking forward to any insights!