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
Rasterio 1.0 comes with some methods to set metadata for band-level units and descriptions. The methods are only available on a dataset writer object. In the case of riomucho, the code calling it never has access to that object. All it sees is:
with riomucho.RioMucho(..., dst_path, ...) as rm:
rm.run(jobs)
What's the best solution? Do we expose these methods on the rio mucho object? Or is there a more generalizable way for us to reach into the dataset object methods from a rio-mucho caller?
Almost 2 years later: I propose that we keep riomucho out of the metadata business. To do that, we need to let the constructor accept open dataset objects as well as paths. Yes?
Rasterio 1.0 comes with some methods to set metadata for band-level units and descriptions. The methods are only available on a dataset writer object. In the case of
riomucho
, the code calling it never has access to that object. All it sees is:What's the best solution? Do we expose these methods on the rio mucho object? Or is there a more generalizable way for us to reach into the dataset object methods from a rio-mucho caller?
See mapbox/rio-toa#23
thoughts @dnomadb @sgillies ?
The text was updated successfully, but these errors were encountered: