Open BigShuiTai opened 1 year ago
I have no experience with this reader, but could you print the area_def
you have and paste the output here?
I have no experience with this reader, but could you print the
area_def
you have and paste the output here?
Area ID: REGX_2000m
Description: FY-4 REGX area
Projection ID: FY-4, 2000m
Projection: {'a': '6378137.20703125', 'h': '35785862.7929687', 'lon_0': '133', 'no_defs': 'None', 'proj': 'geos', 'rf': '298.2561192803', 'type': 'crs', 'units': 'm', 'x_0': '0', 'y_0': '0'}
Number of columns: 900
Number of rows: 1000
Area extent: (-3032011.4738, 2662009.9774, -1233004.5822, inf)
Ah ok, there's our problem. The upper-most extent is inf
. Not good.
The extent is calculated by converting:
c_lats = self.file_content['/attr/Corner-Point Latitudes']
c_lons = self.file_content['/attr/Corner-Point Longitudes']
To X/Y coordinates in the projection space and where Corner-Point Latitudes
and longitudes are global attributes in the input files. Could you find these attributes in your files and tell me the values?
Ah ok, there's our problem. The upper-most extent is
inf
. Not good.The extent is calculated by converting:
c_lats = self.file_content['/attr/Corner-Point Latitudes'] c_lons = self.file_content['/attr/Corner-Point Longitudes']
To X/Y coordinates in the projection space and where
Corner-Point Latitudes
and longitudes are global attributes in the input files. Could you find these attributes in your files and tell me the values?
The c_lats
returns [6.55340000e+04 5.26822548e+01 2.61917515e+01 2.54671078e+01]
, and the c_lons
returns [65534. 112.9593277 99.32941437 120.37347412]
I think 65534
is a wrong value for the GHI data.
Oh yeah, that doesn't look good. @simonrp84 have you seen anything like this before?
Yes, I have. The lats / lons produced by the reader are a fudge as the data from CMA didn't contain all the required information. It wouldn't surprise me if they've changed the contents of their data yet again and that's produced this problem.
Can take a look, but not for a couple of weeks.
Describe the bug Return wrong latitude & longitude while reading FY-4B GHI data.
To Reproduce
Expected behavior Return correct lat/lon data that do not include any np.nan or np.inf.
Actual results
Screenshots If applicable, add screenshots to help explain your problem.
Environment Info:
Additional context Add any other context about the problem here.