You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example gu.examples.get_path("everest_landsat_b4_cropped") does not have the same pixel interpretation as gu.examples.get_path("everest_landsat_b4") (likely because of the way our old crop() function was overridding the attribute to "Area" when we saved that file, see #127).
This is creating a lot of new warnings in the documentation (for instance here: https://geoutils.readthedocs.io/en/stable/core_lazy_load.html#lazy-passing-of-georeferencing-metadata).
We should probably update it to be the same interpretation to facilitate the documentation example, and update the few tests that relied on that difference to override the attribute back to "Area" before the test.
The text was updated successfully, but these errors were encountered:
rhugonnet
changed the title
Cropped landsat data creates warnings in documentation due to different pixel interpretation
Cropped Landsat example data warns in documentation due to different pixel interpretation
Aug 2, 2024
The example
gu.examples.get_path("everest_landsat_b4_cropped")
does not have the same pixel interpretation asgu.examples.get_path("everest_landsat_b4")
(likely because of the way our oldcrop()
function was overridding the attribute to "Area" when we saved that file, see #127).This is creating a lot of new warnings in the documentation (for instance here: https://geoutils.readthedocs.io/en/stable/core_lazy_load.html#lazy-passing-of-georeferencing-metadata).
We should probably update it to be the same interpretation to facilitate the documentation example, and update the few tests that relied on that difference to override the attribute back to "Area" before the test.
The text was updated successfully, but these errors were encountered: