-
Notifications
You must be signed in to change notification settings - Fork 30
Description
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:
morecantile/morecantile/models.py
Line 842 in 329b722
| def _matrix_origin(self, matrix: TileMatrix) -> Coords: |
called within
morecantile/morecantile/models.py
Line 1125 in 329b722
| 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!