Skip to content
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

Add CReSIS Radar Depth Sounder (RDS) L2 data 2009-2017 #21

Closed
3 tasks done
weiji14 opened this issue Sep 30, 2018 · 0 comments
Closed
3 tasks done

Add CReSIS Radar Depth Sounder (RDS) L2 data 2009-2017 #21

weiji14 opened this issue Sep 30, 2018 · 0 comments
Assignees
Labels
data 🗃️ Pull requests that update input datasets enhancement ✨ New feature or request

Comments

@weiji14
Copy link
Owner

weiji14 commented Sep 30, 2018

Add in Radar Depth Sounder (RDS) data from the Center for
the Remote Sensing of Ice Sheets (CReSIS)
team based at the University of Kansas and other places (see here).

Antarctica Coverage Map for most of the past seasons

Acknowledgements:

We acknowledge the use of data and/or data products from CReSIS generated with support from the University of Kansas, NASA Operation IceBridge grant NNX16AH54G, and NSF grant ACI-1443054.

See also:

TODO:

  • Get 2009-2017 Antarctic RDS data from https://data.cresis.ku.edu/data/rds/ (061242a)
  • Process RDS data from csv to a gridded bed DEM (061242a, ebcb85a)
    • Note that only three (Basler, DC8, TO) were processed into DEM tiles
    • One of the datasets (P3) was only downloaded but not processed into a DEM
  • Retrain Super Resolution model with this extra CReSIS RDS data (607557d)
@weiji14 weiji14 self-assigned this Sep 30, 2018
@weiji14 weiji14 added the enhancement ✨ New feature or request label Sep 30, 2018
weiji14 added a commit that referenced this issue Oct 4, 2018
Finally got to adding the bulky CReSIS Radar Depth Sounder (RDS) data from the University of Kansas for #21, bumping up training tile count to 2111! The csv point data is not exactly 'high' resolution, and I had to resort to using an IDW interpolation window_size of 2 in the pdal pipeline instead of 0 as in be0b77c. Three separate geotiffs groupings (Basler, DC8, TO) were used, with one (P3) only downloaded but not processed as the plane didn't fly in a grid pattern. Will use P3 for cross validation further down the track.

Also refactored tiling function from the slow for-loop into a vectorized linear algebra implementation via scikit-image and numpy. This was cleaner and much faster than using a spatial index or parallel asyncio (which I've tried). Seconds instead of hours! This tiling code also has a more elegant UNIX philosophy vibe now.

TODO: Move download links to a separate file, and have hash checksums too? Plus think hard about having unit tests in place.
weiji14 added a commit that referenced this issue Oct 5, 2018
Rookie mistake, turns out the 'bottom' field in the CReSIS RDS csv data isn't actually the WGS84 elevation, but the range from the sensor. Used a python pdal filter to do `ELEVATION-BOTTOM` to get the actual bottom elevation as referenced to the WGS84 Ellipsoid. Also added a YUML diagram to visualize the pipeline. Part of #21.

As an aside, may no longer need to use some fancy spline interpolation scheme to fix the crossover errors I found after 061242a. Was thinking of using Generic Mapping Tools (GMT) or some PDAL filter like 'median absolute deviation' to remove outliers.
@weiji14 weiji14 closed this as completed in 607557d Oct 8, 2018
weiji14 added a commit that referenced this issue Nov 7, 2018
Getting serious with data integrity. Explicitly listing all the data files with their SHA256 checksums (required) and their download URL (if available). Note only the Pine Island Glacier datasets are missing URL. Links upstream to #7, #8, #20, #21.
weiji14 added a commit that referenced this issue Nov 19, 2018
New CRESIS csv file was uploaded a few days ago, and the unit test caught it! Good ol' unintended consequences of unit testing :D Fix our unit test by choosing another blank file, and add this new dataset to our data_list for good measure. Relates to #21.
weiji14 added a commit that referenced this issue Nov 19, 2018
New CRESIS csv file was uploaded a few days ago, and the unit test caught it! Good ol' unintended consequences of unit testing :D Fix our unit test by choosing another blank file, and add this new dataset to our data_list for good measure. Relates to #21.
weiji14 added a commit that referenced this issue Nov 19, 2018
New CRESIS csv file was uploaded a few days ago, and the unit test caught it! Good ol' unintended consequences of unit testing :D Fix our unit test by choosing another blank file, and add this new dataset to our data_list for good measure. Relates to #21.
weiji14 added a commit that referenced this issue Nov 19, 2018
New CRESIS csv file was uploaded a few days ago, and the unit test caught it! Good ol' unintended consequences of unit testing :D Fix our unit test by choosing another blank file, and add this new dataset to our data_list for good measure. Relates to #21.
weiji14 added a commit that referenced this issue Nov 19, 2018
@weiji14 weiji14 added the data 🗃️ Pull requests that update input datasets label Feb 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data 🗃️ Pull requests that update input datasets enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant