Repository navigation
feat: Announce geoparquet mirror size via STAC file extension - #93
Merged
Merged
Conversation
lubojr
approved these changes
Sep 7, 2026
lubojr
left a comment
Collaborator
There was a problem hiding this comment.
Thanks!
Good point with the ParquetSource catalog ref falling out of sync with the remote parquet file size, but as long as the client handling stays a possible optimization and not a mandatory property, that's fine!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Geoparquet collection mirrors now include their byte size, so the client can fetch the parquet footer without first probing for the file length. GitHub Pages compresses the file and a HEAD request does not return the actual file size, which points at the wrong offset.
This covers both catalogs generated with -gp, and collections pointing at an external ParquetSource. In the case of
ParquetSource, the file could be republished without the collection reflecting its updatedfile:size, the client will have to expect the possibility of that and fallback accordingly.