-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ff69973
commit 7bcbcaf
Showing
4 changed files
with
416 additions
and
14 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7bcbcaf
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.
Added function
coincident.plot.boxplot_terrain_diff
which creates boxplots for elevation differences for two input DEMs or an input DEM and point GeoDataFrame. Dynamically adjusts ylims and ticks based on distribution where the two ylims are the elevation differences and counts of each group. Added tests as well.NOTE: docs/examples/elevation_plotting.ipynb is definitely not ready to merge into Main. Hard to give good examples with 2mb notebook limit. The functions themselves, though, are close to "merge-ready"
7bcbcaf
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.
It would be great if we could execute the notebook dynamically (which would require sliderule in the
docs
environment), but then we can have large outputs b/c they just end up on the website rather than the code repository. We can also increase that limit if need be ( I did once from the scientific python template default of 1MB, but if these notebooks change regularly then the size could balloon...coincident/.pre-commit-config.yaml
Line 18 in 56c8f44
7bcbcaf
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.
Ah gotcha. I do like the idea of dynamically executing the notebook, but I'm not quite sure what the best way forward is (and how many example notebooks we'll actually end up having). I can maybe identify a smaller 4-way overlap AOI and do the demo on DEMs at a coarser but not too-coarse resolution for now? Thanks for this!