Add GeoJSON output option for vessel detection pipelines #97
+237
−260
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Use 32 workers when materializing vessel detection crops. - Just use Jupiter for Sentinel-2 job launcher. - Remove redundant code in Sentinel-2 vessel detection pipeline that could hide an error. - Ecosystem mapping: update to use latest dataset version - Minderoo: removed unneeded inference config and update training config to new config format
favyen2
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add GeoJSON output option.
I also changed the order in NearInfraFilter to (longitude, latitude) to be consistent with rest of codebase.
And makes crop directory for Sentinel-2 vessel detection pipeline to avoid directory not exist error.
This depends on PR #96.
Resolves #95.