Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

We at the LP DAAC have been noticing some inconsistencies with regards to interacting with the CMR API lately.

Based on the documentation, it says "For temporal range search, the default is inclusive on the range boundaries." which to me says that any granules matching the dates 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.

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]=true"

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.