Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Assess Landsat metadata changes and how they affect LEDAPS processing #3

Closed
GoogleCodeExporter opened this issue Apr 20, 2015 · 2 comments
Closed

Assess Landsat metadata changes and how they affect LEDAPS processing #3

GoogleCodeExporter opened this issue Apr 20, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Other

Comments

@GoogleCodeExporter
Copy link 

The Landsat metadata values will be changing due to the LDCM project merges 
with Landsat.  These changes need to be assessed and determine if/how they 
affect the LEDAPS processing.

Original issue reported on code.google.com by schmidtg...@gmail.com on 25 Jul 2012 at 8:57
@GoogleCodeExporter
Copy link
Author 

lndpm has been modified to work with the new LPGS metadata as well as with the 
old LPGS metadata.

Original comment by schmidtg...@gmail.com on 17 Oct 2012 at 8:57

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by schmidtg...@gmail.com on 31 Oct 2014 at 10:41

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Other
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter