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
It raises: "ValueError: Invalid formatted plifile, Settings of block might be incorrect, expected a valid name or description at line 0. Invalid block 0:4"
FM does support spaces in the names, it also includes all parts of the name in the history output, so not only the first part before the space like in obsfiles. However, when this polyfile is used for generating bc files, we would end up with names with spaces like this, which I think will cause issues for FM (not tested):
[Forcing]
name = DEEP BAY_0001
I wonder if it is desireable to support spaces in polyline names, or not. If not, maybe FM should also not support them?
Edit: After a quick test I can conclude that FM does support spaces in bc forcing names, so I would suggest to add support for polyline names in hydrolib-core also if it does not ruin other processes.
The text was updated successfully, but these errors were encountered:
When reading a polyfile (.pli) with these contents, I get an error since there are spaces in the names of the polylines:
It raises:
"ValueError: Invalid formatted plifile, Settings of block might be incorrect, expected a valid name or description at line 0. Invalid block 0:4"
FM does support spaces in the names, it also includes all parts of the name in the history output, so not only the first part before the space like in obsfiles. However, when this polyfile is used for generating bc files, we would end up with names with spaces like this, which I think will cause issues for FM (not tested):
I wonder if it is desireable to support spaces in polyline names, or not. If not, maybe FM should also not support them?
Edit: After a quick test I can conclude that FM does support spaces in bc forcing names, so I would suggest to add support for polyline names in hydrolib-core also if it does not ruin other processes.
The text was updated successfully, but these errors were encountered: