Hello everyone,
I'm trying to work with EMIT L2A data, when I select scenes according to the green marking on the EARTHDATA map. When I worked on the data in a smaller rectangle than the one shown in the green marking, the code still told me that there was no data in the entire area I was working in. When I checked the actual boundaries of the scene I downloaded - the boundaries are much smaller than the one shown in the green marking. Is this true? The green marking does not mark the area that has data in the file?
EARTHDATA:
"boundary": {
"points": [
{
"longitude": 17.379528045654297,
"latitude": -19.772571563720703
},
{
"longitude": 16.85712432861328,
"latitude": -20.392864227294922
},
{
"longitude": 17.451335906982422,
"latitude": -20.89330291748047
},
{
"longitude": 17.973739624023438,
"latitude": -20.27301025390625
},
{
"longitude": 17.379528045654297,
"latitude": -19.772571563720703
}
MY CODE:
Size (pixels): downtrack x crosstrack = 1280 x 1242 Latitude range: -20.511082 .. -19.817567 Longitude range: 16.856920 .. 17.529830 Corners (lat, lon):
UL: -19.817567, 16.856920
UR: -19.817567, 17.529830
LL: -20.511082, 16.856920
LR: -20.511082, 17.529830
TNX!
EMIT L2A scene boundaries
-
LP DAAC - dgolon
- User Services

- Posts: 181
- Joined: Tue Dec 03, 2024 2:37 pm America/New_York
- Endorsed: 2 times
Re: EMIT L2A scene boundaries
Hi @yananov Just noting, we are working with the Earthdata Search team on your question. I hope to have an answer for you soon. Thanks -- Danielle
Subscribe to the LP DAAC listserv by sending a blank email to lpdaac-join@lists.nasa.gov.
Sign up for the Landsat listserv to receive the most up to date information about Landsat data: https://public.govdelivery.com/accounts/USDOIGS/subscriber/new#tab1.
Sign up for the Landsat listserv to receive the most up to date information about Landsat data: https://public.govdelivery.com/accounts/USDOIGS/subscriber/new#tab1.
-
LP - erik.bolch
- Subject Matter Expert

- Posts: 4
- Joined: Mon Jun 13, 2022 10:26 am America/New_York
- Endorsed: 2 times
Re: EMIT L2A scene boundaries
Hi @yananov,
It is true that the polygon from the Earthdata map is slightly larger than the footprint of the actual data. That polygon is defined based on 4 points, so the boundary is extended to account for earth curvature and ensure it encompasses the full scene. Without doing this, some data would be cut off and excluded from searches.
This image should illustrate for your scene: Zoomed in: Hope this helps.
It is true that the polygon from the Earthdata map is slightly larger than the footprint of the actual data. That polygon is defined based on 4 points, so the boundary is extended to account for earth curvature and ensure it encompasses the full scene. Without doing this, some data would be cut off and excluded from searches.
This image should illustrate for your scene: Zoomed in: Hope this helps.