-
Notifications
You must be signed in to change notification settings - Fork 24
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
DELETE ME #2433
DELETE ME #2433
Conversation
@JohnHalleyGotway does the most recent comment from GwenChen in the issue here #2426 |
@davidalbo, I suppose it does. I'd recommend that we stick with the smaller set of changes in #2432 for the bugfix in main_v11.0. But ideally we'd update the develop branch with the more thorough set of the buoy locations. Options are...
I don't have time now to work on the updated buoy locations file, but perhaps you do? If you do, let's add you as an assignee to this issue and do option (1). If not, let's do option (2). What do you think? |
Here's the plan:
|
…e web and update local data
@davidalbo wondering if I should just close this PR? Or are you planning on using it for your set of changes for develop for this issue? |
@JohnHalleyGotway I have python already implemented and uploaded to this branch: bugfix_2426_develop_buoy. All that is needed is testing, which would be to run the python script, then run ascii2nc on the newer ndbc locations file that gets generated.And... replace the actual table file with the newer one if the test works. I can do this as part of issue 2426 I guess, whatever makes sense. I'm actually confused by what seems to be 3 issues for this. 2426 2433 2432 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm understanding, this pull request puts a few things into develop:
- adds changes made by JohnHG for logging formatting.
- Adds additional stations by hand to the ndbc_stations.xml file.
- Adds a python script that combines station information from the two sources, but that is not yet used for anything.
We can continue working on #2426 to actually use the python or make a new issue to continue work on that.
I approve this pull request.
Same fix as PR #2432 but for the develop branch instead. Please review them together.