Longitude / Latitude banding in L2 MODIST data
Posted: Mon Feb 12, 2018 11:03 am America/New_York
Hi All
I have been accessing L2 granules obtained using fd_matchup.py and MODIST. The internals of fd_matchup uses the CMR search of OB_DAAC L2 granules (e.g. url: https://cmr.earthdata.nasa.gov/search/granules.json).
The metadata suggests this was created using L2gen.
The thing is that the Longitude and Latitude arrays have some serious banding issues. Each 10 pixels or so there is a discontinuity creating a "sawtooth" type of response.

This corresponds to very visible "banding" in the products (e.g. chor_a etc.) where strips are repeated due to the positional sawtooth function described above.

Is this a common / fixable phenomenon? I'm using this data for machine learning and so the banded redundancy is not ideal. If I reproject using the lat, lon arrays this creates missing stripes of data....which is also not ideal.
Anyone got any ideas? Is this a specific sensor (MODIST) problem or something that is common across all sensors....or possibly a reprocessing error?
Thanks
Paul
I have been accessing L2 granules obtained using fd_matchup.py and MODIST. The internals of fd_matchup uses the CMR search of OB_DAAC L2 granules (e.g. url: https://cmr.earthdata.nasa.gov/search/granules.json).
The metadata suggests this was created using L2gen.
The thing is that the Longitude and Latitude arrays have some serious banding issues. Each 10 pixels or so there is a discontinuity creating a "sawtooth" type of response.

This corresponds to very visible "banding" in the products (e.g. chor_a etc.) where strips are repeated due to the positional sawtooth function described above.

Is this a common / fixable phenomenon? I'm using this data for machine learning and so the banded redundancy is not ideal. If I reproject using the lat, lon arrays this creates missing stripes of data....which is also not ideal.
Anyone got any ideas? Is this a specific sensor (MODIST) problem or something that is common across all sensors....or possibly a reprocessing error?
Thanks
Paul