1

I have a SHP point file created from CSV with QGIS 2.4.0 Chugiak. It contains some data on noise in a certain point. When I import from CSV, it seems to be fine, but when I export to SHP and open the attribute table - the real-type numbers are wrong ("reduced" number). The funny thing is, that when I open this SHP with older QGIS NextGIS 1.8 - everything is fine.

Is it some kind of bug?

I attach the printscreen:

Left is Nextgis, right QGIS Chugiak. The suspicious fields are marked red.

closed as off-topic by underdark Jan 7 '18 at 10:21

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – underdark
If this question can be reworded to fit the rules in the help center, please edit the question.

  • when I copy and paste to spreadsheet from QGIS Chugiak, the real numbers look OK. – Piotr Sadowski Jul 24 '14 at 18:49
  • 2
    It is a classical problem, please read What Every Computer Scientist Should Know About Floating-Point Arithmetic or, with Python: Floating Point Arithmetic: Issues and Limitations – gene Jul 24 '14 at 18:54
  • I'm just a normal user, not a programmer or system designer. I can set a floating point precision in CSV. It seems to be a software problem (displaying) as the old QGIS does the job. It does not solve why everything else displays the numbers correctly except for QGIS Chugiak. – Piotr Sadowski Jul 24 '14 at 19:11
  • It seems that the values are displayed incorrectly only in the attribute table, so the problem is of "less annoyance". – Piotr Sadowski Jul 24 '14 at 19:17
  • 1
    OK the rounding worked in 2.4.0 Chugiak, just created a new field with a precision set to 1 and deleted the old field. – Piotr Sadowski Jul 24 '14 at 19:37