API beta test
-
@marekd We will need to discuss this internally. Initial feeling is that we would rather stay as close to a standard leaflet implementation as possible. Windy is a small part of our application.
@marekd can you reproduce the above CSS issue? I could create a simple page and set this up if you would like.
Euan
-
@compassdsnm CSS pseudo class
:read-only
is applied correctly, checkboxes and radio buttons are considered as readonly inputs in browsers by default. There is nothing wierd about that. If you need to change this behaviour, feel free to override styles like you did. -
@marekd said in API beta test:
checkboxes and radio buttons are considered as readonly inputs in browsers by default.
@marekd I have never seen a checkbox or radio button having a default readonly value in all my life. Please can you share any documentation you have on this?
Mozilla's documentation says it is not default.
https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/readonlyPrior to your release on Monday morning, this was working as expected.
-
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 -
@thiago-gabriel Thanks for the report! You are right, it looks like a bug. To hofix this issue, please use:
store.set('overlay', 'wind', { forceChange: true })
We try to fix it and release update today.
-
@thiago-gabriel It is fixed now, thanks again!
-
@marekd Thanks for the new updates and sorry haven’t seen the thread. I recently noticed that a couple of features have changed during the update.
1 Now data of ICON (Eu and Global) is only displayed every 3 hours by default, even though the time step is shown every 1 hour. GFS defaults to data every 1 hour as before
2 The satellite data is no longer automatically included as before. If ‘satellite’ set as the default layer of the API, it is visible. If the default is something else and the satellite is only in the favorite layer, it will not be visible at all.
Or have I previously used the wrong name for the satellite data (‘satellite’) and the layer has only been shown because it was the only data I had in that API -
Sorry confusing, I have two account Saaneuvos and DaFish. Recently use the rare one
-
@marekd Thanks for the new updates and sorry haven’t seen the thread. I recently noticed that a couple of features have changed during the update.
1 Now data of ICON (Eu and Global) is only displayed every 3 hours by default, even though the time step is shown every 1 hour. GFS defaults to data every 1 hour as before
2 The satellite data is no longer automatically included as before. If ‘satellite’ set as the default layer of the API, it is visible. If the default is something else and the satellite is only in the favorite layer, it will not be visible at all.
Or have I previously used the wrong name for the satellite data (‘satellite’) and the layer has only been shown because it was the only data I had in that API -
@saaneuvos Thanks for the report! We will look into it and let you know.
-
Hi @saaneuvos ,
-
1 hour animation step for ICON models is a feature available only for premium users logged in on Windy.com and it's not available in our Map Forecast API.
-
I checked your site and you are missing
satellite
in thefavOverlays
array. If you put it there, you should see the satellite option in the menu.
-
-
@nesro and @marekd Thanks. Before the update, there was 1 hour animation step in IconEU in premium API! And in GFS there is 1 hour a.s. I think there should be 1 hour a.s. for premium customers for paid version at least for the IconEu ( because no Ecmwf). In my opinion GFS and IconGloal could be 3 hour a.s.
-
-
@saaneuvos It is the image data of premium models with 1 hour granularity that are not available for Map Forecast API. They are only available on www.windy.com for premium users.
There is no way how the API client can access the 1 hour image data right now.
-
@nesro Will the 1 hour data be back for paid Map forecast API some day. Now you can get 1 hour GFS in free version of Map forecast API, but not Icon even in paid pro version?
-
@saaneuvos GFS is at this moment free for all users. ICON do not. We are sorry, it was bug that 1h forecast was available. It is a premium feature for windy.com users. It is not available for API, unfortunately. Sorry for all troubles, but we have basically just fixed a bug.
-
@marekd OK. I'm trying to settle for this ;)
-
-
-
@Thiago-Gabriel Hi! I got the same error as you and I fixed it by removing the global window.W when unmounting my component. So I still run init on mount but now I don't get the warning. Feels like a hack but I don't know any other way to fix this in a SPA. Hope this is some kind of help
-
@KimDotSe I got some more errors from windys lib-somthing file after removing global.W. Moved the delete to right before i run init again instead.
-
WOW!! Thank You!!!