-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Data not being saved to PostGIS database consistently #23898
Comments
Author Name: John Zielinski (John Zielinski) Just for reference, here's the range of doubles (float8) that 1A.x has in the tables above:
|
Author Name: John Zielinski (John Zielinski) Found something new. Two snapped points again ended up being not the same but this time visible in the vertex editor (just the x value): -90.237137558 I suspect it's because the shortest form was less than the maximum digits displayed. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Giovanni Manghi (@gioman) End of life notice: QGIS 2.18 LTR Source: QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle. We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4 Most plugins have been either migrated or incorporated into the core QGIS code base. We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it. You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket. If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment. The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.
|
Author Name: John Zielinski (John Zielinski)
Original Redmine Issue: 15982
Affected QGIS version: 2.18.0
Redmine category:data_provider/postgis
I'm using QGIS Desktop with a PostGISdatabase. I've created a polygon with 4 points (A to D) and then another polygon inside it with 3 points. Those three points were then snapped to 3 of the points in the first polygon (A, C and D). The vertex editor shows this (I've changed the first column here to label the points):
As you can see 1A = 2A, 1C = 2C and 1D = 2D. In my database however:
The three common points are not the same! They round to the values shown in QGIS but cause random errors when I do ST_Contains on the polygons. Sometimes polygon 1 contains polygon 2 and sometimes it doesn't. The reason for the randomness is that by resnapping just one point and saving I get:
Totally different values as far as PostGISis concerned.
Just to be sure it's not PostGIS I tried this:
And I always get the following in the database no matter how many times I do the UPDATEs:
Note: The values in the database I've show were read by a C program that used a custom Postgres function to read the internal PostGIS GSERIALIZED binary data. This made sure nothing along the line mucked with the values (no conversions to or from WKT/WKB). The coordinates were printed using the very accurate and precise David M. Gay's floating-point conversion library.
The text was updated successfully, but these errors were encountered: