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
should each step have a sensible default for the output_file (name and path)?
what about keeping the previous filename but appending something like _points or _segmentation or _pixelcount depending on the process that was run (and removing any previous appended defaults if found?)
alternatively, when the user is forced to provide the path, they know where to look for the file and what it'll be called? although this potential issue could also be mitigated by making sure every process logs a completed message that includes the path (which might already be the case), for example:
2024-07-19 11:04:16.000 | SUCCESS | __main__:main:99 -
Saved points, images and scores to /Users/danbjoseph/
GitHub/americanredcross/street-view-green-view/data/
interim/ParkView_segmentation.gpkg
The text was updated successfully, but these errors were encountered:
should each step have a sensible default for the
output_file
(name and path)?what about keeping the previous filename but appending something like
_points
or_segmentation
or_pixelcount
depending on the process that was run (and removing any previous appended defaults if found?)alternatively, when the user is forced to provide the path, they know where to look for the file and what it'll be called? although this potential issue could also be mitigated by making sure every process logs a completed message that includes the path (which might already be the case), for example:
The text was updated successfully, but these errors were encountered: