@upscalevalley001 I think you are using too much of Chat GTP. All your answers are amazing. You answered to 4 post in the last 4 hours, you just created your account in the last 4 hours also!
Impressive ! Please confirm you wrote this with Chat GTP ?
Hello there,
The Webcam API professional states that we can enjoy full size images. Could you give more precision on the expected size of those images (resolution size)? Also, does the size change depending on the webcam or is it a universal size for every webcam ?
Thank you,
@Dale1771
We always lived in a climate changed world. Just some people being aware of it nowadays.
@tessellahedron
If I'm not wrong, windy ECMWF model is updated every 6 or 12 hours. And weather forecasts can change quite quickly depending on the location, especially those with a lot of mountains around.
Keep in mind that this is "forecasts", so it doesn't mean everything will be accurate. In the old times, most weather services gave a reliability % for accuracy: For example, 80% for sunny weather tomorrow, which means there is a 20% chances that it won't be sunny at all. Usually after 3-4 days, the reliability level drops below 50% of success. And because most weather forecast companies are businesses that needs to generate revenue, they tend to not show the reliability % anymore.
For WeatherKit, from my experience, since Apple bought Dark Sky, it just became less accurate, while Dark Sky use to be one of the most accurate. Sad.
Hi,
I would really appreciate an answer to the above question :)
Maybe the question wasn't clear so I rephrase it.
In V2, we could query webcams this way to retrieve the image url:
https://api.windy.com/api/webcams/v2/list/webcam=1438905018?show=webcams:image,url
This would return an empty array for the url webcams. In this post (https://community.windy.com/topic/23527/missing-webcams-in-the-api), you explained that some webcams are not provided in API since their providers don't want to have them there.
In V3, the same request (https://api.windy.com/webcams/api/v3/webcams/1438905018?include=images,urls) returns an url for this webcam.
Is this the intended behavior and now those providers are okay to share their webcams through your API?
I have no affiliation with any of those providers, I'm just working on a side project that may use your webcams API.
Thank you,
@kekert said in Webcams V3 token for images:
You don't have to save the token, it is already in the url. All you have to do is to call the API before each page load (in order to have urls of the images with fresh tokens)
OK cool. I thought the token was also designed to minimize API usage.
@kekert Thank you for your reply.
I'm far from being a security expert ;) but most API I used always relied on an API key or a signed certificated to protect their data.
If we assume the key could be stolen by reading the network communication, I don't see how the token would increase security. A hacker could always still the key, and make the urls requests to collect the token. Also, your other API (forecast, map) doesn't seem to have a token to protect the data, which is why I'm surprised with this token implementation for the image urls.
My main pain point with your current solution is that we have to save a token for every single image url, and then calculate when we have to collect it again.
Hi Windy,
With the new V3 API, we now need to retrieve a token to access the url of the webcam images. I understand the purpose of securing the urls, but why not simply use our API key to retrieve those urls instead of this token?
We now have to save a token somewhere, which means more ressources usage (write on disk every x hours), which is not very ESG compliant. The API key would be enough to secure those urls, in my opinion. Any reason on why to use a token instead ? There are many other way to secure access to data without the struggle to collect a token every time.
Thank you for any clarification on this technical choice.
Hi Windy,
Some webcams that were not available in API V2 are now available in V3 (https://community.windy.com/topic/23527/missing-webcams-in-the-api).
Is this the intended behaviour for V3 ?
Thank you,
It's been years I compare forecast model as a side hobby project. Most of them are often completely wrong. Those companies/public organisations are just selling data based on their madeOfNothing-reputation. They just measure the weather conditions from 1 spot, and then use algorithms to "guess" the weather in other regions, hoping people will trust them - and it work !
Also keep in mind that ECMWF model is mainly using weather sensor in Europe. There predictions are only update twice a day, which might be the reason of the wrong weather conditions in your region.
@Ondřej-Šutera I hope they are at least aware they are down
It seems they are down again, even their website. Any info ?