Skip to content
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

improve cropping method #22

Open
caver456 opened this issue Jul 7, 2022 · 0 comments
Open

improve cropping method #22

caver456 opened this issue Jul 7, 2022 · 0 comments

Comments

@caver456
Copy link
Contributor

caver456 commented Jul 7, 2022

Sometimes searchers are intentionally searching siginifcantly outside the drawn assignment boundary. This can result in a) a lot of cropped fractured segments even though the crop function is working correctly, and b) missed data outside the crop boundary.

Shoreline searches are a good example - in this case the shoreline drawn based on MBT is significantly different from the actual shoreline:

image

image

While one could say that planners should get in the habit of using MBH or some other imagery layer, that's probably not a realistic or reasonable request. We know the planners' intent was to have the team search the shoreline (and some swath inland from the shoreline), wherever that might be.

What's the best way to deal with this?

  • Expand the crop boundary / increase the overlap for all assignments?
  • Increase the overlap more for linear/buffer assignments than for area assignments?
  • keep/reattach cropped discarded segments that touch the crop boundary twice i.e. track-goes-out-then-comes-back-in?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant