manually set proj:epsg to ensure items are compatible with old versions of GDAL STACIT #4
Conversation
This file contains 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
hrodmn
force-pushed
the
fix/proj-epsg
branch
from
307d15a to
81f6150
Compare
hrodmn
changed the title
gadomski
previously requested changes
Feb 28, 2025
hrodmn
dismissed
gadomski’s stale review
I incorporated your suggestions - thanks!
gadomski
approved these changes
Feb 28, 2025
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.
Description
Some versions of GDAL require the
proj:epsgfield in item metadata for the STACIT driver. We need to figure a way to write items that are compatible with versions as old as GDAL 3.7.Checklist
scripts/test)