Skip to content

Conversation

alexolinhager
Copy link
Contributor

Introduces a geometric_features collection of all GIS tidewater outlet glaciers in the Uummannaq/Disko Bay region of Greenland.

@alexolinhager alexolinhager force-pushed the UummannaqDisko_regions branch 3 times, most recently from 30fbfe7 to 9c18fd5 Compare August 14, 2025 21:42
ntroduces a geometric_features collection
of all GIS tidewater outlet glaciers in the
Uummannaq/Disko Bay region of Greenland.
@alexolinhager alexolinhager force-pushed the UummannaqDisko_regions branch from 9c18fd5 to b5b0dd4 Compare August 14, 2025 21:54
Copy link

@trhille trhille left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting a few minor changes after visual inspection.
@xylar, how do you recommend testing this?

The function :py:func:`geometric_features.aggregation.landice.uummannaq_disko`
aggregates the GIS tidewater outlet glaciers flowing into the Ummannaq and Disko Bay region of
Greenland. Glacier boundaries were defined using the ice basin layer in QGreenland
(https://github.com/nsidc/qgreenland/) and manually manipulated near the glacier termini to create
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a version tag here in case these basin definitions change in future QGreenland releases?

Greenland. Glacier boundaries were defined using the ice basin layer in QGreenland
(https://github.com/nsidc/qgreenland/) and manually manipulated near the glacier termini to create
a buffer zone around each outlet glacier, so that QGreenland boundaries encompass the full glacier area
defined on the MALI mesh.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On which MALI mesh?

Parameters
----------
gf : geometric_features.GeometricFeatures
An object that knows how to download and read geometric features
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording "knows how to" is strange to me.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind, now I see that this is taken from other places in the code base.

@xylar
Copy link
Collaborator

xylar commented Aug 18, 2025

@xylar, how do you recommend testing this?

@trhille, take a look at:
https://mpas-dev.github.io/geometric_features/main/adding_features.html#co-developing-geometric-features-with-other-packages

You should create a compass development environment as usual, then install geomtertic_features from this branch in edit mode, then set $GEOMETRIC_DATA_DIR as described. Make sure you add exporting $GEOMETRIC_DATA_DIR to the compass load script so it happens in your tests as well.

@xylar
Copy link
Collaborator

xylar commented Aug 18, 2025

@alexolinhager, it seems like maybe you're doing your development without having pre-commit installed. If you have the development environment active (and have run pre-commit install once), it should lint and format the code before it lets you make commits. This isn't a big deal but typically leads to a cleaner development workflow than linting after the fact.

It seems right now like you have some trailing whitespace.

@trhille
Copy link

trhille commented Aug 18, 2025

Testing

I tested this using https://github.com/alexolinhager/compass/tree/create_uummannaq_disko at commit f185877 rebased onto COMPASS/main. It appears to be working as intended:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants