Should be on top of #246 When reading COGs, it could be a problem that offset data is rather big, so partially reading only needed offset data may be useful. This also somewhat links to @spoutn1k's PR #242 that adds types for ProcessedEntry, DecodedEntry and BufferedEntry.. I'll open an issue for discussing a bit more over-arching design questions
Should be on top of #246 When reading COGs, it could be a problem that offset data is rather big, so partially reading only needed offset data may be useful. This also somewhat links to @spoutn1k's PR #242 that adds types for ProcessedEntry, DecodedEntry and BufferedEntry.. I'll open an issue for discussing a bit more over-arching design questions