We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a somewhat rare edge case that comes up with complicated landmasses & AOIs. It's hard enough to contrive an example that we don't test for it, apparently. Our code to handle MultLineString iteration simply is not compatible with Shapely 2.0. https://shapely.readthedocs.io/en/stable/migration.html#multi-part-geometries-will-no-longer-be-sequences-length-iterable-indexable
MultLineString
I have some user's data so I can reproduce and fix it.
Traceback (most recent call last): File "taskgraph\Task.py", line 674, in add_task File "taskgraph\Task.py", line 1093, in _call File "natcap\invest\coastal_vulnerability.py", line 1176, in prepare_landmass_line_index_and_interpolate_shore_points TypeError: 'MultiLineString' object is not iterable 10/21/2024 17:29:44 natcap.invest.utils ERROR Exception while executing natcap.invest.coastal_vulnerability Traceback (most recent call last): File "natcap\invest\utils.py", line 165, in prepare_workspace File "invest\cli.py", line 470, in main File "natcap\invest\coastal_vulnerability.py", line 856, in execute File "taskgraph\Task.py", line 674, in add_task File "taskgraph\Task.py", line 1093, in _call File "natcap\invest\coastal_vulnerability.py", line 1176, in prepare_landmass_line_index_and_interpolate_shore_points TypeError: 'MultiLineString' object is not iterable
The text was updated successfully, but these errors were encountered:
move a test to be near other related tests. natcap#1657
e1698ab
fixed a shapely 2.0 incompatibility; modified a test to cover it. nat…
2b956f9
…cap#1657
reverting a change for debugging. natcap#1657
b5a681b
davemfish
Successfully merging a pull request may close this issue.
This is a somewhat rare edge case that comes up with complicated landmasses & AOIs. It's hard enough to contrive an example that we don't test for it, apparently. Our code to handle
MultLineString
iteration simply is not compatible with Shapely 2.0. https://shapely.readthedocs.io/en/stable/migration.html#multi-part-geometries-will-no-longer-be-sequences-length-iterable-indexableI have some user's data so I can reproduce and fix it.
The text was updated successfully, but these errors were encountered: