BUG: Zoo workflow saves config.json in a different format than CoastSat workflow #205
Closed
1 task done
Labels
bug
Something isn't working
Currently the zoo workflow and coastsat workflow operate quitely differently. I believe the goal is to have these workflow be interchangable at some point. However this cannot happen if each workflow generates different formatted files. The zoo workflow currently works on only a single ROI at a time while the coastsat workflow can process multiple ROIs within a single session.
Sample Config.json from Zoo Workflow
Sample Config.json from CoastSat Workflow
The text was updated successfully, but these errors were encountered: