Closed cssprad1 closed 3 months ago
Currently we can run demCreator with 3 different types of input:
Giving the CLV a list of scenes.
evhr/view/demCreatorCLV.py -t -o /explore/nobackup/people/rlgill/SystemTesting/testDEM3/ --scenes '/css/nga/WV02/1B/2018/278/WV02_10300100889D0300_X1BS_502602073050_01/WV02_20181005212447_10300100889D0300_18OCT05212447-P1BS-502602073050_01_P002.ntf'
Giving the CLV an envelope to then query footprints for applicable scenes.
evhr/view/demCreatorCLV.py -t -o /explore/nobackup/people/rlgill/SystemTesting/testDEM3/ -e -148 65 -147.5 64.5 4326
Giving the CLV a list of catalog IDs which then gets the scenes based on a footprints query.
evhr/view/demCreatorCLV.py -t -o /explore/nobackup/people/rlgill/SystemTesting/testDEM3/ --catIds 10300100889D0300
At a high level, this task would get rid of 2 and 3? In addition, removing some portions of the pipeline that find missing pairs via footprints. Making dem creator self-contained with no database dependency.
Done with #22, closing.
cssprad1
commented
3 months ago
Currently we can run demCreator with 3 different types of input:
Giving the CLV a list of scenes.
Giving the CLV an envelope to then query footprints for applicable scenes.
Giving the CLV a list of catalog IDs which then gets the scenes based on a footprints query.
At a high level, this task would get rid of 2 and 3? In addition, removing some portions of the pipeline that find missing pairs via footprints. Making dem creator self-contained with no database dependency.