-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Processing Refactor fields: can't change an "int" field to "double" with 0 precision #20363
Comments
Author Name: Arnaud Morvan (@arnaud-morvan) FieldsMapper use standard processing function "output.getVectorWriter" to create output storage, and give it selected type and precision. |
Author Name: Victor Olaya (@volaya) IS this a Processing issue or a QGIS one? Processing just passes the precision value to the QgsField object, and it seems that QGIs is not handling it as it should
|
Author Name: Giovanni Manghi (@gioman) Still true on master, please change the category if it is a QGIS issue rather than a Processing one.
|
Author Name: Alexander Bruy (@alexbruy) This is not a Processing bug and even not QGIS one. Seems GDAL does not allow to create float fields with zero precision
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman) End of life notice: QGIS 2.18 LTR Source:
|
Author Name: Filipe Dias (@fsdias)
Original Redmine Issue: 12171
Affected QGIS version: master
Redmine category:data_provider/ogr
Steps to reproduce:
Run Refactor fields using the attached shapefile
Go to field "Nt", change its type to "double" and set Precision to 0
The new field still has "Nt" as "int". If the Precision is changed to 1 or more, it works.
The text was updated successfully, but these errors were encountered: