To support different TMS in mosaic.json specification, it is necessary to explicitly provide the _geographic_crs field. By including, the rest of the tooling is able to instantiate the transformations between projected space and geographic space.
Here is a test using sueprmorecando with a planetary TMS. This will fail here when morecantile attempts to access the _geographic_crs field in the input data. This will default to None and then proj will throw the error that no transformation exists between our planetary CRS and WGS84.
I think we can fix this in a number of places. The easiest integration is to provide that key on the planetcanetile side and use all of the other tooling as it already exists.
To support different TMS in mosaic.json specification, it is necessary to explicitly provide the
_geographic_crsfield. By including, the rest of the tooling is able to instantiate the transformations between projected space and geographic space.Here is a test using sueprmorecando with a planetary TMS. This will fail here when morecantile attempts to access the
_geographic_crsfield in the input data. This will default to None and thenprojwill throw the error that no transformation exists between our planetary CRS and WGS84.I think we can fix this in a number of places. The easiest integration is to provide that key on the planetcanetile side and use all of the other tooling as it already exists.