-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEADAS: seadas reader fixes (master) #119
base: master
Are you sure you want to change the base?
Conversation
knowles
commented
Jan 13, 2023
- Fixed product naming in L1AHawkeyeFileReader.
- Recognizes level3 mapped files output by l3mapgen and adds band autogrouping.
- L1CPACEFileReader can now read SPEXOne and HARP2 files.
- Added support for PACE L1C.
- Added support for PACE L1B version 8.
…nd adds band autogrouping. 2. L1CPACEFileReader can read SPEXOne and HARP2 files. 3. Added support for PACE L1C. 4. Added support for PACE L1B version 8.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again, Danny.
There is only a minor comment. Maybe you want to do the change regarding the GeoCoding.
If not, the PR is okay for now. Let me know what you would like to do.
But in general, some unit level tests would be great.
@@ -108,7 +101,7 @@ public void addGeocoding(final Product product) throws ProductIOException { | |||
lats = geoNcFile.findVariable("geolocation_data/latitude"); | |||
lons = geoNcFile.findVariable("geolocation_data/longitude"); | |||
|
|||
//Use lat/lon with PixelGeoCoding | |||
//Use lat/lon with TiePointGeoCoding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this change in the comment is not correct. In the end still a PixelGeoCoding is created.
By the way, the GeoCodingFactory should not be used anymore. It is better to use the ComponentGeoCoding. Probably we will soon change the implementation of GeoCodingFactory or maybe remove it at all. The new one is faster and more accurate.
|