question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

acquisition_date seems to not exist in metadata

See original GitHub issue

While updating the GRASS GIS addon i.landsat.download to support the recent changes in landsatxplore (Thanks much!!!), I found out that metadata regarding date has changed in both collection 1 and 2 Landsat data. There’s not such thing as acquisitionDate anymore nor acquisition_date, but now there is a dictionary temporalCoverage with keys start and end date or a different key called publishDate. See https://github.com/OSGeo/grass-addons/pull/450.

Where did you find acquisition_date variable when updating the README https://github.com/yannforget/landsatxplore/commit/f44f12232360b8cea5d4057c331b30245cb4db06 ? If I perform the search and print scenes, I do not see it.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:12 (6 by maintainers)

github_iconTop GitHub Comments

3reactions
yannforgetcommented, Feb 26, 2021

Hi all and thanks for the inputs,

Yes, metadata field names and date formats are all over the place for now. I’m currently working on an update that harmonizes metadata field names and data types across the datasets, with automatic conversion to shapely Polygons for spatial objects and python datetimes for temporal values.

So in the next release (shoud be today) acquisition_date will always return a valid python datetime.

2reactions
yannforgetcommented, Mar 1, 2021

Yes, the NADIR bug is fixed now

Regarding i.landsat.download, you would have to update:

  1. The metadata dictionary keys: entityId -> entity_id, display_id -> display_id, acquisitionDate -> acquisition_date, cloudCover -> cloud_cover, etc.
  2. The calls to ee.download as the scene_id= argument has been replaced by identifier=
  3. The post-processing of the metadata values. Cloud cover is now returned as a float and acquisition date as a python datetime
Read more comments on GitHub >

github_iconTop Results From Across the Web

OMERO does not import Acquisition Date from .czi file metadata
Hi, there is one file uploaded . It is from a Zeiss LSM880. The data where copied to another computer via network.The image...
Read more >
Copy metadata "Date Modified" to "Date Acquired"
I wish to batch copy each file type JPG and video clip MTS their modified date to overwrite EXIF Date Acquired. I am...
Read more >
Retrieve the target lifecycle state through instance metadata
If your instance transitions to one of the target lifecycle states after that date, the target lifecycle state item is present in your...
Read more >
What is metadata and how does it work? - TechTarget
Metadata is data that describes other data, providing a structured reference that helps to sort and identify attributes of the information it describes....
Read more >
How to resolve warning messages (metadata object not found
The MyClass2 2nd generation subclass seems to be significant (without it the warnings go away). I do not understand why. I have run...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found