-
Notifications
You must be signed in to change notification settings - Fork 42
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
coregistration with ICESat-2 #282
Comments
Hi Marco, Great idea, and your timing is perfect! 😄 I implemented support for point data last winter in a It would be amazing to integrate this fully into xDEM, but there is still quite a bit of work on structuring, testing, plotting, and documenting! We should also coordinate with the developers of ICESat-2 aside, we had in mind to improve the structure, add plotting functionalities and write more tests for all |
Hi Romain, what you're doing sounds exciting, especially creating a workflow for downloading snow-off ICESat-2 tracks and co-registers DEMs might be beneficial for many people given the consistency and accuracy of ICESat-2 data! I am up for collaboration in general. Add me to the channel (my mail is mazzolini.marc@gmail.com). I participate in a summer school for some weeks, but I can join the effort from the second half of September! |
@mmazzolini, could we close this issue, as #346 is merged and we thus have (poorly refined but existing) functionality for Raster-point co-registration? |
We now have full point-raster support since #480, with the new documentation about to be published soon. Closing! |
Hi everyone,
I am a PhD student at UiO and in our project, we hope to measure snow depth with ICESat-2 data and snow-free DEMs. In this context, coregistration is a crucial step. I know in the repository iamdonovan/pybob there is a similar functionality, but wanted to know if someone here is working on it. If not, I wonder if someone with some experience on the structure of xdem would like to collaborate on implementing this feature.
Cheers,
Marco.
The text was updated successfully, but these errors were encountered: