Date: Thu, 28 Mar 2024 14:05:07 -0400 (EDT) Message-ID: <2038041120.1368.1711649107938@gs-ed-prod-wiki1.earthdata.nasa.gov> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1367_814090353.1711649107938" ------=_Part_1367_814090353.1711649107938 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
We at the LP DAAC have be= en noticing some inconsistencies with regards to interacting with the CMR API lately.
https://cmr.earthdata.nasa.gov/search/granules= .json?pretty=3Dtrue&short_name=3DAST_L1T&version=3D003&temporal= []=3D2016-10-10T01:38:36.000Z,2016-10-10T01:39:03.000Z
G1334068323-LPDAAC_ECS at time 2016-10-10T01:38:36.000Z
G133431= 2987-LPDAAC_ECS at time 2016-10-10T01:38:45.000Z
G1334312859-LPDAAC_ECS = at time 2016-10-10T01:38:54.000Z
https://cmr.earthdata.nasa.gov/search/granules= .json?pretty=3Dtrue&short_name=3DAST_L1T&version=3D003&temporal= []=3D2016-10-10T01:38:36Z,2016-10-10T01:39:04Z
G1334068323-LPDAAC_ECS at time 2016-10-10T01:38:36.000Z
G133431= 2987-LPDAAC_ECS at time 2016-10-10T01:38:45.000Z
G1334312859-LPDAAC_ECS = at time 2016-10-10T01:38:54.000Z
G1334312951-LPDAAC_ECS at time 2016-10-= 10T01:39:03.000Z
Based on the docume= ntation, it says "For temporal range search, the default is inclusive o= n the range boundaries." which to me says that any granules matching the da= tes I provide should be included in my results. This seems to work fine for= the early/left side of the range, as the first granule returned matches my= earliest date, but it doesn't work on the later/right side of the range.= p>
Secondly, it doesn't seem like the option to flip the logic so that= it excludes the boundary makes a difference on the results. If I add
"options[temporal][exclude_boundary]=3Dtrue"
to the end for those queries, the results stay the same. I would expect = the first granule to disappear in both cases since my earliest date matches= the granules date exactly.