-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
Maintence Request: Don't read settings from shoreline and transect settings files #208
Comments
|
After some investigation I've found that the I suppose its possible to get rid of this file because these details can be created on the fly when the extracted shorelines are loaded onto the map. I'll need to think about this a bit more. |
I'm going to pause on this idea for now given that with the current design reading from |
Coastseg should not read settings from the files shoreline_settings.json & transect_settings.json . After testing coastseg with users our team has determined that the best approach is to store all relevant settings in a single file
config.json
. Saving these settings to different files is an artifact from a time where we wanted to store different settings in different files, however, this makes to more complicated for both developers and users to track settings, so we have decided to abandon this approach.Tasks
modify the
load_session_files
to not read the shoreline and transect settings from shoreline_settings.json & transect_settings.jsondon't save the shoreline and transect settings in a separate file
remove all code that generates the shoreline and transect settings files
The text was updated successfully, but these errors were encountered: