-
Notifications
You must be signed in to change notification settings - Fork 9
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
RGI09 (Russian Arctic): wrong ice divide on one tidewater glacier #4
Comments
Thanks! In terms of workflow (what needs to be done), the easiest would be to select the two or three entities in GLIMS that need change and change only these. These could then be submitted to GLIMS as a new contribution, and in the script we could unambiguously replace the three faulty ones with the new contribution. |
Excellent, I will do this and resubmit to GLIMS next week. |
|
Actually, did you submit anything related to this issue @willkochtitzky ? |
I actually never did. I wasnt sure if it was really helpful or just extra work. If it is helpful, I could do that this afternoon. |
See attached for the corrected outlines (also emailed to @fmaussion and Bruce). No other glaciers will be impacted, I left the other borders the same as they are pretty close. |
Trello card: https://trello.com/c/LXovmAfk |
Just to keep track of this: I will incorporate them in RGI7 with a temporary workaround but there is some issues to be fixed in GLIMS before I can close this. cc @bruceraup |
![Screen Shot 2021-07-22 at 2 48 24 PM](https://user-images.githubusercontent.com/30648918/126692990-9fe61ecb-90ab-4c8b-bc47-d89bd045a622.png)
I am not sure if this is a big enough issue to merit our time in fixing. I came across this because the mass balance budgets are way off, I think due to the size of the glacier in RGI. In RGI7 it is: G059108E75722N In RGI6 it is: RGI60-09.00088I drew the red arrow where I think you have flow coming into this basin. I am not sure how to redo the basin boundaries, just that this one looks way too small based on the size of the calving front and crevasses/velocity. If there is a suggestion for how to fix it, I am very happy to do the work to make it happen.
This is the ID for the Landsat image used here: LE07_L1TP_179006_20000812_20170210_01_T1
From August 12, 2000
The text was updated successfully, but these errors were encountered: