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

Track CRS info in BoundingBox and changes to GeoBox constructors #38

Merged
merged 9 commits into from Apr 27, 2022

Commits on Apr 22, 2022

  1. Keep track of CRS in BoundingBox #25

    Adding .crs property to BoundingBox class, it no longer derives from
    namedtuple so there is some potential for breakage compared to what's
    in datacube-core.
    Kirill888 committed Apr 22, 2022
    Configuration menu
    Copy the full SHA
    09e6607 View commit details
    Browse the repository at this point in the history
  2. More usefull methods for bounding box

    .from_transform - construct from shape+affine
    .polygon return geometry from bbox
    Kirill888 committed Apr 22, 2022
    Configuration menu
    Copy the full SHA
    4fc47d7 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    c944f89 View commit details
    Browse the repository at this point in the history
  4. Add method for computing GeoBox footprint

    compute footprint of geobox in any projection with
    configurable padding and precision
    Kirill888 committed Apr 22, 2022
    Configuration menu
    Copy the full SHA
    c473e7f View commit details
    Browse the repository at this point in the history
  5. Moved ROI types into types

    Kirill888 committed Apr 22, 2022
    Configuration menu
    Copy the full SHA
    5715b50 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    edf5ec5 View commit details
    Browse the repository at this point in the history
  7. Replace alignment with anchor

    `align=` was too confusing and hard to document, concept of anchor I
    feel is more reasonable. You can anchor pixel edges to 0,0 or pixel
    center to 0,0, or you can leave it floating. Or you can pick any
    location within a pixel and say that 0,0 should coincide with that.
    
    center == (0.5, 0.5)
    edge == (0, 0)
    
    Also replacing _align_pix methods, that were hard to decipher, with
    snap_grid method in odc.geo.math
    Kirill888 committed Apr 22, 2022
    Configuration menu
    Copy the full SHA
    ef19d5b View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    2860c44 View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    8094832 View commit details
    Browse the repository at this point in the history