Skip to content
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

Closed
qgib opened this issue Feb 10, 2015 · 6 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers

Comments

@qgib
Copy link
Contributor

qgib commented Feb 10, 2015

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.


@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2015

Author Name: Arnaud Morvan (@arnaud-morvan)


FieldsMapper use standard processing function "output.getVectorWriter" to create output storage, and give it selected type and precision.
With type double and precision 0, I confirm that resulting field is displayed as integer in fields tab of layer properties dialog.

@qgib
Copy link
Contributor Author

qgib commented Jun 26, 2015

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


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Dec 27, 2015

Author Name: Giovanni Manghi (@gioman)


Still true on master, please change the category if it is a QGIS issue rather than a Processing one.


  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented Jan 12, 2016

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


  • assigned_to_id removed Victor Olaya
  • category_id was changed from Processing/QGIS to Data Provider/OGR

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/


  • status_id was changed from Open to Closed
  • resolution was changed from to end of life

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant