@musselfarm Once you click on Upgrade to professional and select the price option, you will be presented with a payment window, where you can select your country -
Screenshot 2022-07-05 at 9.37.29.png

@ShahramT Yes, there are many errors and they always be there. The problem is, you initialize API multiple times. That it worked is merely coincidence, not intention. In the new version, I had to do a workaround to preserve this compatibility.

@valda-sung Hello, I would recommend to check our Terms of Use.

Windy Premium is a completely different service than Windy API. If you want to use Windy in your project, you need to consider API only, more information at https://api.windy.com/.

Daily limit can be increased upon agreement, but for this, we would need to know details about your project and how exactly will be our data used.

@Thiago-Gabriel Unfortunately not :-( I reverted API to the old version until we will fix all the issues. Please, prepare me some playground without user data where I can replicate the bug, otherwise I am not able to help you. Leaflet extend method is too generic and used everywhere.

@korina Thanks for getting in touch! I just sent you the info through PM.

@안효진-2 Hello, try to insert the localhost address or your official project URL.

(sorry for the bracketed thing -- not escpated by this commenting system it seems)

It seems the only way to incorporate Windy is via explicit script tag, that is, not via an installable package from NPM, correct? The specific issue I note is that there wouldn't be a way to control the loading of the components as instructed in the documentation, that is, first Leaflet, then Windy.
For my Leaflet apps, I basically have:

import L from 'leaflet';

(and then us L as usual).

For also testing this setup with Windy, assuming an NPM-installable 'windy' package, I would then expect to be able to just do something like this:

import { windyInit } from 'windy';

and then use windyInit, etc.

Any comments or additional (technical) pointers that can clarify what's actually possible in term of integrations with frameworks like Vue would be very welcome. Thanks!

@wborsatti Hello, you can find more information at https://api.windy.com/.

Please also read our Terms of Use. API cannot be used in weather related projects or projects with no added value.

@frloo Hello, I would recommend to have a look at our API - https://api.windy.com/.

@asjustis Hello, Moisture anomaly is not available via API. All the available layers are stated on our API website.

@rob-burgess Hello, as the documentation says, the values are returned in local time:
"The sizes of all returned arrays are identical and the indexes mutually correspond. For example at the surface altitude the value of temp-surface[5] in the units defined as units["temp-surface"] contains the temperature for a timestamp ts[5] of the local time for given spatial coordinates."

@todesengel Hello, do you still have this issue? I do not see any error on those pages.

@careyshan Hello, the full API documentation can be found at https://api.windy.com/

@asjustis Additionally, I found that at least for labels, the issue is calculating the transform position for the label div. As in the screenshot, tile seems to perfectly positioned, and just the label position is somewhere far far away in the galaxy :))

Any chance for a fix or a workaround?

We were about to grab the pro license and launch our project, but bumped into this issue which is quite critical for us.

Thanks,
Justinas!

Screenshot 2022-06-07 at 09.48.51.png

@dwstallings Hello, API data are only available in 3hour intervals, no matter if you have a paid or test API key.

@rafaelrsss Hello, weather radar layer is not accessible via API, therefore you can't receive dBZ values.

@btrimm did you ever find a way to do this in leaflet?