Comments (7)
I talked to Scott Rudlosky from NESDIS and he pretty much reiterated what Tim said, adding that Tim really knows his stuff. I agree that the metadata must be correct, but I'm still puzzled as to why the ABI imagery seems to contain more error than can be attributed to just parallax. I'll dig around and play around with reprojection functions some more and let you know if I come up with anything
from pybkb_v3.
I haven't run into issues like this yet, but this is good to know. Thanks.
from pybkb_v3.
@mnichol3, I can confirmed the issue with the satellite longitude location. The left is GOES16 at -75.0 degrees, the right is GOES16 at -75.2 degrees. It is obvious that the drawn coastlines are wrong for the -75 degree location. The location metadata in the file is wrong!
This document shows that GOES-16 location is -75.2. (It looks like GOES-13 used to be at -75.0, which might be the source of the error). https://www.goes-r.gov/users/transitionToOperations16.html
The question is, how do we get the metadata fixed in the NetCDF files available on Amazon???
from pybkb_v3.
I downloaded another GOES-16 netCDF from NCDC to see if the longitude metadata error was unique to the Amazon files; the NCDC file had it too.
Not exactly sure how to go about addressing this issue, but I know some folks at NESDIS so I'll talk to them and see if they've heard anything about it!
from pybkb_v3.
That makes sense, since Amazon receives the files directly from them.
I contacted the people I know, too. Maybe with several people hearing the issue it will be fixed soon.
I wonder if GOES-17 has a similar issue?
from pybkb_v3.
The answer I got from Tim Schmit (Twitter @GOESguy) is this:
There are 2 longitudes, one is the location of the satellite, which is approximately 75.2W, the other, as you have noted above, that is the longitude of the remapped ABI data and that is in fact to 75.0W. Since you have remapped data, I think the 75.0W is the right value.
From that statement, I suspect the file's metadata should be trusted because the ABI data has been remapped to a common grid. However, that still doesn't explain why the coastlines I'm plotting appear misplaced. Perhaps there are issues when reprojection the image.
from pybkb_v3.
It appears the issue depends on which map plotting tool you use. With Basemap, the coastlines are off, but with Cartopy, the coastlines are correct.
from pybkb_v3.
Related Issues (2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pybkb_v3.