CSV writer: do not quote integer fields by default (only if STRING_QUOTING=ALWAYS is specified) #8813
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
…OTING=ALWAYS is specified)
|
What I think was a real problem in the gis.stackexchange case was that the field was defined to be integer in the .csvt file but GDAL did not trust it. Without .csvt it is quite possible that strings like '0123' appear later in the data, but having .csvt indicates that user has taken the responsibility. |
no, the issue in the gis.stackexchange case was only on the writing side. Even if the field was typed as integer, it would be written as quoted. |
|
Right, I can see with ogrinfo that the reading side was OK. |
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.
Fixes https://gis.stackexchange.com/questions/470855/integer-field-of-csv-file-always-output-as-string-when-processed-with-ogr2ogr