Please check if your PR fulfills the following requirements:
[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[x] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[ ] Check your code additions will fail neither code linting checks nor unit test.
Pull request type
Please check the type of change your PR introduces:
- [x] Bugfix
- [x] Feature
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [ ] Other (please describe):
## What is the current behavior?
We have encountered bad inputs in GFW Pro Dashboard (see GP-96) which lead to topology exceptions during the intersections required for feature splitting. These are fatal exceptions.
Issue Number: N/A
What is the new behavior?
The solution should be to use the same strategy as in #122 to capture intersection problems in the input geometries by threading the use of Validated from cats into the Dashboard module.
Does this introduce a breaking change?
[ ] Yes
[x] No
Other information
Note that this PR was built on top of #127 to aid in debugging.
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces: - [x] Bugfix - [x] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior?We have encountered bad inputs in GFW Pro Dashboard (see GP-96) which lead to topology exceptions during the intersections required for feature splitting. These are fatal exceptions.
Issue Number: N/A
What is the new behavior?
The solution should be to use the same strategy as in #122 to capture intersection problems in the input geometries by threading the use of
Validatedfrom cats into the Dashboard module.Does this introduce a breaking change?
Other information
Note that this PR was built on top of #127 to aid in debugging.