-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Add imagery and timeframe selection #30
Conversation
@vgeorge when testing, I see two issues:
|
app/assets/scripts/components/explore/prime-panel/tabs/predict/mosaic-selector/index.js
Show resolved
Hide resolved
@vgeorge initial style handled for now. Can we truncate the bounds? |
@LanesGood thanks for the review. Here are some notes about the changes I made now:
I'm not planning on adding further changes until developmentseed/pearl-backend#43 is added to developmentseed/pearl-backend#38. I believe it would be better to have them ready before we finish hooking the logic to the UI. cc @geohacker |
@vgeorge yes, I think the preset mosiac timeframe selection should come from a dropdown list, if it is possible to format as [ Should we use the term "mosaic" in the UI? I think "Timeframe" is more approachable for users, but am not certain if this is 100% accurate.
To confirm, this sounds correct when no AOI/prediction run has yet been executed. When a prediction has already been run, we don't need to clear the imagery/mosaic/model |
Enable sample erase
Fix empty AOI list state
# Conflicts: # app/assets/scripts/fsm/project/machine.js
Disable AOI fill opacity
# Conflicts: # app/assets/scripts/fsm/project/machine.js
Upgrade Node.js to v18
…l, project and model mock commands.
…mand mockProjectEndpoints for readability
Move mock API routes payloads into separate files
As part of the branch reorganization described in #71, this is ready to be merged. |
Remaining tasks: