Skip to content

CornerOfOrigin not used #189

@claxn

Description

@claxn

I have the following use case: I am using the TileMatrix class to set up my own tiling system, instead of using TileMatrixSet directly. After defining TileMatrix instances for several "tiling levels" (or zooms), I create a TileMatrixSet instance by using the pre-initialised matrices.

However, when using the cornerOfOrigin argument/attribute, the class design and usage of TileMatrix and TileMatrixSet seems to be decoupled. For instance, I would expect that the following method:

def _matrix_origin(self, matrix: TileMatrix) -> Coords:

called within

def xy_bounds(self, *tile: Tile) -> BoundingBox:

makes use of cornerOfOrigin. But instead, only the orderedAxes argument is taken into account. Shouldn't xy_bounds consider the origin of the grid, i.e., if it is "topLeft" or "bottomLeft"? In my case I would need "bottomLeft".

Maybe I misunderstood the correct usage of TileMatrix and TileMatrixSet - it would be great to have this feature available making it more generic and easy to use - thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions