Use ogr json #5968
Draft
Use ogr json #5968
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
eliotjordan
force-pushed
the
use-ogr-json
branch
2 times, most recently
from
54c0826
to
e8fb0dd
Compare
eliotjordan
force-pushed
the
use-ogr-json
branch
from
e8fb0dd
to
4ef1b25
Compare
eliotjordan
force-pushed
the
use-ogr-json
branch
from
4ef1b25
to
5ecfb90
Compare
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.
Use json formatted orginfo output. Companion to: #5967
Will have to wait until Figgy boxes are upgraded. GDAL/OGR needs to be updated in order to add -json flag for ogrinfo command.
Our prod and staging boxes are at GDAL 3.6.4. Our CI image is at GDAL 3.4.1. This feature need at least GDAL 3.7. :(