BUG: fix reading files with unsupported OGR types (skipped fields) #110
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.
I was testing locally with https://github.com/OSGeo/gdal/blob/master/autotest/ogr/data/arrow/test.feather, and that includes a bunch of fields with unsupported types, and that actually raises errors because of
None
being present in thefields
(where we expect a integer for the index or a string for the field name)(just quickly pushing here instead of opening a bug report)