Visualize wind field on Cesium
Visualize the wind on earth, powered by Cesium JS.
More detail is in this blog post: GPU Powered Wind Visualization With Cesium
Just create a HTTP server for the "index.html" file in the "Cesium-3D-Wind" folder.
If you have VSCode installed, I recommend to intall the "liveserver" extension.
The NetCDF file is in the "data" folder, it should contains below variables: - U (lev, lat, lon) @min @max - V (lev, lat, lon) @min @max
Note: - Don't forget to change the filename in the source code ("gui.js") - "lev", "lat", "lon" are names of dimensions, and "min", "max" are the attributes of the variable. - The order of dimensions matter - Use small (less than 100MB) NetCDF file if possible, or your browser may crash.
The layout of the NetCDF data:
Note: - The range of longitude is
[-180, 180]- netcdfjs will read the data row by row, so array(0) is (lon 0, lat -90) - You must use NetCDF version 3 (NOT 4, NOT other file types like HDF or GRIB) file
For more detail, use Panoply to read the "data/demo.nc" file
You can add a function for loading JSON data in the dataProcess.js, and call your JSON loading function in the exposed function loadData.
However, you should ensure that the data return from your JSON loading function should have the same structure as that of function loadNetCDF.
After the conversion I used NetCDF Operator for further process of the NetCDF data. I wrote a PowerShell script(in the 'Util' folder) to extract and transform the data by making use of NetCDF Operator. You can also use this script once you setup the 'NCOPath' and 'fileToProcess' variables in the script.
"particleHeight" is the distance from the surface of earth. Particles lower than the terrain will be overlapped.
Because sometimes the depth test for particles is not accurate enough. This problem is similar with Z-fighting, the cause is depth buffer does not have enough precision.
The panel is made with dat.gui library, you can read its document and modify the gui.js as you need.
If possible, you should run this demo in Chrome on PC, because I did not test it in other browser or mobile device.
If you got into trouble on other device(for example, mobile phone), you can check your WebGL implementation in WebGL report. Check the "Supported Extensions" section, below extensions are at least required: - OEStexturefloat - WEBGLdepthtexture extension - EXTfragdepth
Please check the speed of your network connection. Open the development tools in your browser and refresh the website, then check if your browser is downloading the data in a very slow speed.
Unfortunately, there is no easy way to debug WebGL code, and I can't find any debugging tool for setting breakpoints in WebGL. For the moment, I suggest to use Spector.js to figure out what is happening with your WebGL code. It can tell you the input and output of your code.
Probably the WMS URL changed, you may check the latest WMS URL by accessing NOAA's TDS server of GFS Analysis. Click the data file of the date you want (mine is 201909160000000), then the WMS URL for this file will be showed in the web page. After getting the latest URL, you can update the variable "WMS_URL" in gui.js to make WMS layer display work again.
This demo makes use of TDS server of NOAA GFS for WMS layer display