You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
The text was updated successfully, but these errors were encountered:
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:
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?
The text was updated successfully, but these errors were encountered: