Closed bnordgren closed 8 years ago
Yep, crap, this is a huge oversite. When I put things together my testing data set was in chronological order and then I forgot about it. That proabably explains the trouble I was having with large fires.. I’ll put together a bit to sort the list.
[Forest Service Shield]
Carl Albury Remote Sensing Specialist
Forest Service Contractor Remote Sensing Applications Center
p: 801-975-3351 calbury@fs.fed.usmailto:calbury@fs.fed.us
2222 West 2300 South Salt Lake City, UT 84119 www.fs.fed.ushttp://www.fs.fed.us/ [USDA Logo]http://usda.gov/[Forest Service Twitter]https://twitter.com/forestservice[USDA Facebook]https://www.facebook.com/pages/US-Forest-Service/1431984283714112
Caring for the land and serving people
From: bnordgren [mailto:notifications@github.com] Sent: Tuesday, March 08, 2016 8:30 AM To: firelab/viirs_ba viirs_ba@noreply.github.com Subject: [viirs_ba] must process scenes in chronological order (#13)
The way the code is written, scenes must be provided to the ImageDates option in the configuration file in chronological order. At the moment, I have them sorted manually.
It's probably better just to have the viirs_config object sort them. Or the get_dates utility emit them in sorted order.
— Reply to this email directly or view it on GitHubhttps://github.com/firelab/viirs_ba/issues/13.
This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.
You thinking to add to my viirs_config class, or to the processing code? I think there's probably just a .sort() method on the list or something like that.
On Tue, Mar 8, 2016 at 10:41 AM, calbury notifications@github.com wrote:
Yep, crap, this is a huge oversite. When I put things together my testing data set was in chronological order and then I forgot about it. That proabably explains the trouble I was having with large fires.. I’ll put together a bit to sort the list.
[Forest Service Shield]
Carl Albury Remote Sensing Specialist
Forest Service Contractor Remote Sensing Applications Center
p: 801-975-3351 calbury@fs.fed.usmailto:calbury@fs.fed.us
2222 West 2300 South Salt Lake City, UT 84119 www.fs.fed.ushttp://www.fs.fed.us/ [USDA Logo]http://usda.gov/[Forest Service Twitter]< https://twitter.com/forestservice>[USDA Facebook]< https://www.facebook.com/pages/US-Forest-Service/1431984283714112>
Caring for the land and serving people
From: bnordgren [mailto:notifications@github.com] Sent: Tuesday, March 08, 2016 8:30 AM To: firelab/viirs_ba viirs_ba@noreply.github.com Subject: [viirs_ba] must process scenes in chronological order (#13)
The way the code is written, scenes must be provided to the ImageDates option in the configuration file in chronological order. At the moment, I have them sorted manually.
It's probably better just to have the viirs_config object sort them. Or the get_dates utility emit them in sorted order.
— Reply to this email directly or view it on GitHub< https://github.com/firelab/viirs_ba/issues/13>.
This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.
— Reply to this email directly or view it on GitHub https://github.com/firelab/viirs_ba/issues/13#issuecomment-193884346.
Fixed in fom branch via 3dc08fab16d12da3bbd61703976b0541b59f0fe0
The way the code is written, scenes must be provided to the ImageDates option in the configuration file in chronological order. At the moment, I have them sorted manually.
It's probably better just to have the viirs_config object sort them. Or the get_dates utility emit them in sorted order.