Isolines, raster layer and particle speed in a paid API


  • Paid API user

    1. I use isobars (pressure isolines) most of my weather maps but want to make some higher-level maps with geopotential lines instead of isobars (or maybe without any isolines). Now it seems that all the geopotential lines have calculated from ECMWF and usually after one- or two-days those are looking just funny and confusing. Is it not possible to create geopotential lines from the chosen model?
    2. If so, how can I exclude isobars from some maps. Now the API seem to make automatically isobars in all my maps if I don’t define any specific isolines.
    3. Is it somehow possible to use the same functionality for isolines that is used in Windy.com (the box , where you can activate or deactivate different isolines)?
    4. Is it possible to adjust particle speed and density in the paid API and do it only for one or two specific map?
    5. Is it possible to change the interval of the isobars in the paid API. I would be interested to change interval when zooming in and out (I’m dreaming 5 mb interval in zoom level 1-4 and 1 mb interval in zoom level > 5 ;)
    6. Is it somehow possible to adjust little less blurring for the isobars? The “kincks” of weather fronts is currently not detectable. It would be also possible to detect local wind effects from small “kincks” in the isobars… Of course, there must be some blurring, but in a meteorological sense it’s now little bit too much…
    7. There is raster layers in precipitation map and cloudiness map. In precipitation map there is flakes and in cloud map there is precipitation. Is it possible to take these raster layers away or maybe make those working on/off…


  • @saaneuvos Sorry about the delay.

    1. Isobars are generated server-side. If there are no isobars you are looking for, there is no any other option. Sorry.
    2. Take a look at https://api4.windy.com/examples/parameters/, you can run W.store.getAllowed('isolines') from, for example, debug console on the page you run Windy Map. And you will see off in the list :-)
    3. You have to create your own and change them on click.
    4. You can use undocummented settings for particles, for example: W.store.set('particles', {"multiplier":0.5,"velocity":1.4,"width":0.5,"blending":1.05,"opacity":1.5}) and rerender your map. Feel free to investigate what all these attributes do. You must handle specific particle settings for layers/maps on your own.
    5. No, it i not possible.
    6. Same as number 1., sorry.
    7. No, every layer is rendered as canvas objects.

  • Paid API user

    @marekd thanks for your time! I've never coded before and everything is very new for me... I know your job is not to teach coding, but could tell me what is wrong in my JS:
    W.store.set('isolines', 'off')

    I have made everything straight to my public folder knowing nothing about debug console ;)



  • I am affraid I am not able to help you with that. Go through all examples at https://api4.windy.com/, especially focus on https://api4.windy.com/examples/parameters/ and google, google and google :-) Hope you will make it work!


  • Paid API user

    @marekd I meant. Is this wrong way to avoid showing any isolines?

    W.store.set('isolines', 'off')


  • Paid API user

    @marekd I would say that there is bug in the API4 code! When using 'gh', 'pressure', 'temp', 'deg0' in W.store.set('isolines', 'x'), every isolines are changing and working nicely. But using W.store.set('isolines', 'off') after the above options, always getting some random isoline in the map!!! It's seem to be the most used isoline...

    In higher level maps it would be ok to use gh-isolines, but then isolines had to be from same model than other data. Now gh comes always from ecmwf and it seems very confusing after couple of days ( when models start to differ). That's why it so important to get rid of "wrong" gh. Without any gh is better than wrong gh...



  • @saaneuvos It works for me as expected, please, make your site with Windy Map public and send me URL as a private message into chat.


  • Paid API user

    @marekd & co: This seem to be bigger problem I first realized. Do you have any estimation when this (probably CORS) will be fixed? The bug is causing problems to my parent sites. Even when I'm making changes to my test folder, which is not published anywhere in my sites, might broke my parent sites !?! API seem to use latest changes made (at least in isolines, particles)in my test folders also for the already published API pages...



  • If it brokes your page, you are doing something wrong. You must handle on your own to keep js errors in its scopes.
    We will fix isolines, but now we are finishing some huge things with much higher priority. It will probably take us some time. If you need to publish your site, do not use isolines for now.


  • Paid API user

    Hi, I have already published my sites, but can't make any updates to my site. If I don't determine any isolines, API try to use the last one used.. And it seem that there is the same problem with particles? So, it's better that I don't make any update to my sites before you fix the problem... Do you have any estimation, when that fix possible will happen. I know it's not big deal for you, but it is important for me as a paid customer.



  • I am really sorry, but I cannot promise you any date. If you do not want to use paid API anymore, send email to simona.polackova@windy.com. Simona will refund you.


  • Paid API user

    @marekd weeks, months...?


Log in to reply
 

Windyty, S.E. - all rights reserved. Powered by excellent NodeBB
NodeBB & contributors, OSM & contributors, HERE maps