@marekd said in API beta test:

https://api.windy.com/assets/map-forecast/libBoot.js?beta=36

Hei, thanks for the effort in fixing the issues we are facing. I tried the beta version of the API and I still face the same two issues from before.

• The particles plugin is not init due to some error when trying to extend a Leaflet component (the component is undefined).
• When returning to the page where the windyMap is init, the init process fails.

I dont have time to try to prepare a playground that reproduces the error for you right now. I will try to do it when I finish some other tasks.

I noticed that after the release of the new version of the Windy API, the particle system is not working at all. When the page first loads, there is no particles displayed. When the map is reloaded during navigation, the whole map crashes.

Here is an screenshot of the error I get:

This is a similar issue reported today by another user today (see post). In my case, even with a professional key, the issue with the API happens.

Could you please take a look into this issue?

Thank you,
Thiago Gabriel

Suddenly a CORS error appeared in my application.
I can see it is also visible in the windy api page.

Could you guys check what the issue is?

Regards,
Thiago Gabriel

@nesro It is! Thanks!

@nesro It is! Thanks!

Suddenly a CORS error appeared in my application.
I can see it is also visible in the windy api page.

Could you guys check what the issue is?

Regards,
Thiago Gabriel

When i click the playback button, the particle animation only work in a constrained section of the whole map. In the SS below, it is possible to see that the tile to the left has no particles and the tile to the right is where the animation starts.

This only happens during the playback. If i just click at some timestamp in the forecast timeline, the particles are displayed over the entire map.

The windy map is implemented in my react application and I have tested in both chrome and firefox. There are no errors displayed at the console.

Any ideas about how to fix this issue?

Regards,
Thiago Gabriel

@nedait

Hey!

I'm little late to the party, but I have experienced a similar issue when the windy api was update the new version recently. In my case, the problem loading the particles puglin happened because of a conflict between loading the leaflet library in the html file of my react application and a module import of the leaflet library in one of my react components. Not sure if it is the same problem you are facing, but I think it is worth checking for this kind of conflict.

regards,
Thiago

Hi again! I'm facing some issues with the WIND overlay in my ReactApp (not sure if the problem is related to React or not, though).

When the windyApi loads, the legend that shows the color scale is not generated. If I change the overlay manually, to any other overlay, the legend for that overlay is generated correctly. If then I change back to the WIND overlay, the legend is now generated.

I also noticed that I cannot change to the WIND overlay programatically. Using store.set("overlay","wind") yields to no results. Once again, this works if I use any other overlay as argument.

Here is a minimal reproduction of the issue: https://codesandbox.io/s/romantic-cloud-tio6qd?file=/src/App.jsx

Could you guys please take a look at this issues?
Thiago

@marekd Hi marekd. I face the same issue regarding the reinitialization of the map in my React web app. If i do not explicity reinit the map when I come back to the page that contains the windy div after navigating to another url, the map is not rendered again (I just get a gray screen). Am I missing something? Why the class that I use to define the windy map doesnt seem to target the windy map div after the first initialization of the API?

@marekd said in API beta test:

https://api.windy.com/assets/map-forecast/libBoot.js?beta=36

Hei, thanks for the effort in fixing the issues we are facing. I tried the beta version of the API and I still face the same two issues from before.

• The particles plugin is not init due to some error when trying to extend a Leaflet component (the component is undefined).
• When returning to the page where the windyMap is init, the init process fails.

I dont have time to try to prepare a playground that reproduces the error for you right now. I will try to do it when I finish some other tasks.

@marekd Hei, thanks for the reply. It is tricky for us to share the running API, since we have authentication+sensitive data from clients in the app. I tracked down the error to a Leaflet.CanvasLayer "extend" call inside the gl-particles module. Is this info of any help for you?

I noticed that after the release of the new version of the Windy API, the particle system is not working at all. When the page first loads, there is no particles displayed. When the map is reloaded during navigation, the whole map crashes.

Here is an screenshot of the error I get:

This is a similar issue reported today by another user today (see post). In my case, even with a professional key, the issue with the API happens.

Could you please take a look into this issue?

Thank you,
Thiago Gabriel