This is just a quick overview of the major parameters and measurements provided by NOAA that get pulled into the model. There are a few different sources for these parameters, though in the end the sources all have pretty much the same data. Time Timestamp Data is generally provided in Track datasets, where each set of measurements has a corresponding timestamp. Includes Year, Month, Day, Hour, and often Minute, but hour is the primary resolution measurements are usually at 6 hour intervals, but sometimes interim measurements are made for large or notables storms Models tend to interpolate between time steps for more uniform coverage Position and Movement Position Provided as a Lat/Lng, to a 10th of a degree resolution Range: 90W-90E, 90S-90N Most NOAA products provide this in the format 1234E, 5678S.

This post will be about how I accessed the Go/Wasm memory buffer from the Javascript side. I wanted to get this one out, because it took me a very long time to work through it, and I had to piece together a ton of random internet resources. All the code is pulled from the site, but I’ve simplified it the best I can. Go/Wasm instantiation in JS When instantiating the Go/Wasm “application” in JS-land, its important to keep a reference to the WebAssembly object used in that process.

I played with WebAssembly, and now there’s a map! Well, I hit the “compile to WebAssembly” button on the Go compiler. Turns out it’s not that hard for the basics, which is pretty cool. Most of the work was put into remembering how the GeoJSON format works, so I could do the string formatting on the Go side. I’m also taking a bit sending back just a string and parsing the string on the JS side, but it works well enough.