Alexander Rey

Good news and bad news. The good news is that I fixed the bug preventing this, which was a pretty easy fix (type error). The bad news is it led...

Yup! Fixes are in 2.1, so good to close!

Hey, thanks for opening this issue, and also cluing me into Briefsky, which I hadn't seen before! To answer your initial question- I suspect the reason they're different is because...

This one is sort of an interesting question- my overall mental model for this API is that "point requested = point returned" from a data standpoint, but obviously that's not...

Just wanted to say I haven't forgotten about this! V2 is up for testing on the dev endpoint, but I missed this particular issue for it- you should see the...

Quick update- this is live in version 2.0l, which should go to production API tomorrow! It's still relying on ETOPO, so may have some inaccuracies from there; however, at least...

I would love to include it, but despite a fair bit of sleuthing, I can't seem to find the GFS elevation data anywhere! I know exactly what you're asking for...

What's currently being returned is the elevation from ETOPO, which is a separate elevation data set maintained by NOAA. GFS (the model) would have its own internal elevation database, but...

Thanks for opening an issue- you're definitely in the right place. UV index is kind of a tricky parameter. It's the only one that comes from a different model, so...

I've been watching this over the last few days and this is definitely an issue! I'm working om revamping some of the processing flows now, so I'm going to take...