Thanks for that Even On 20 January 2016 at 09:23, Even Rouault <even.roua...@spatialys.com> wrote:
> Le mercredi 20 janvier 2016 09:04:52, Neumann, Andreas a écrit : > > Hi, > > > > Regarding GDAL update to version 2.0: if your platform is Windows, I > > already asked Jürgen if he can update to version 2.0 - as there are > > other issues/new functionality that would be enabled by moving to GDAL > > 2.0 (like better Geopackage support, curve support (for Interlis and > > later also Geopackage) and probably some other improvements). So there > > is a good chance that QGIS 2.14 on Windows will ship with GDAL 2.0. > > FYI, GDAL 2.0.2 RC1 should be out for the end of the week. > > > > > @Uwe: while I totally agree that this is a severe error that should be > > fixed, apparently it isn't that easy. And I can only recommend that you > > should not build your GIS projects around Shapefiles. There are other > > options around, like Postgis, SpatiaLite or Geopackage that also allows > > to share data with ArcGIS. And you could also store and edit your data > > in SpatiaLite, Postgis or Geopackage and then only export to Shapefiles > > if you need to deliver your data to your client. Shapefiles are from the > > past century and should be avoided - for many reasons. > > > > I also remember that Marco Hugentobler (Sourcepole) was contracted to > > fix these Shapefile issues for the province of Vorarlberg - though I may > > be wrong. So there is already someone investing to fix this bug. Marco - > > correct me if I am wrong. > > > > Hopefully, there can be a fix about this Shapefile issue in QGIS 2.14 > > ... > > > > Andreas > > > > On 2016-01-20 07:34, Matthias Kuhn wrote: > > > Hi all, > > > > > > Here is some more eplanation of the issue: > > > > > > > http://gis.stackexchange.com/questions/58101/how-to-avoid-creating-corrup > > > t-shapefiles-during-editing/79677#79677 > > > > > > I spent quite some time to fix this issue as much as possible from QGIS > > > side (Hint: "they" are not just lazy and ignore problems ;-) ) It seems > > > that there is also a second (closely related) problem left to be solved > > > and it looks that it can be solved by shipping a newer GDAL version. > > > Apparently the issue has not been completely solved yet and apparently > > > it is considered to be from "critical" over "big fail" to "fatal" from > > > the audience. It would be awesome if you could ask the maintainer of > > > your operation system's builds for a quote to ship QGIS with GDAL 2.0 > on > > > your operation system. We will gladly provide you with email addresses. > > > > > > Best regards, > > > Matthias > > > > > > On 01/19/2016 10:54 PM, Mats Elfström wrote: > > > Hi! > > > While all that Nicolas and Uwe says is generally true and reasonable, > it > > > is also true that bugs and errors can be more or less dangerous. With > > > limited resources, it is even more important that bugs are handled > > > according to a simple risk analysis. In this case, it would go > something > > > like this: > > > What is the probability that users will edit shape files (high, > moderate, > > > low): High What is the probability that QGIS will damage shape files: > > > Moderate (as I understand) What is the severity of the potential damage > > > (fatal, reparable, negligible): Fatal And High * Moderate * Fatal > equals > > > a probable risk for fatal damage, which ought to prompt for a rapid fix > > > of ths bug, regardless of where it resides in the QGIS ecosystem. But > > > oddly enough, I have browsed through many of the posts on the shape > file > > > issue, but have yet to find a technical description of the exact cause > > > and origin of this bug. > > > > > > Regards, Mats.E > > > > > > 2016-01-19 22:14 GMT+01:00 Saber Razmjooei > > > <saber.razmjo...@lutraconsulting.co.uk>: > > > > > > Dear Uwe, > > > > > > There are some work-arounds and solutions provided within the ticket. > > > > > > Also, work is underway to resolve the issue in the next LTR release. > Last > > > time I checked (5 minutes ago) it is still present in master. > > > > > > I totally agree with you that there should be a warning to users to > make > > > them aware of this limitation. > > > > > > In general, QGIS and other GIS/non-GIS proprietary software come with > > > bugs. The reason developers haven't fixed this bug and other bugs is > due > > > to lack of resources (time, money). > > > > > > The project steering committee is committed to resolving the bugs and > > > they have already allocated a big proportion of their income for bug > > > fixing. You can see last year's financial report hear: > > > > > > http://qgis.org/en/_downloads/PublicQGISfinancialreport2014.pdf > > > > > > If you think, there should be more work done to increase the quality of > > > QGIS, you can get involved or contribute to the project: > > > > > > > http://qgis.org/en/site/getinvolved/governance/sponsorship/sponsorship.ht > > > ml > > > > > > Regards, > > > > > > Saber > > > > > > FROM: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] ON BEHALF > OF > > > Uwe Fischer SENT: 19 January 2016 19:10 > > > TO: 'qgis-user ML' > > > SUBJECT: [Qgis-user] QGIS big fail in deleting Shapes!! > > > > > > Hello all, > > > > > > today I was working on a shape dataset and I had to delete some > features. > > > Later I opened the shapefile in ArcMap by chance and I found that the > > > features were not deleted. They still did exist. I repeated the process > > > - and got the same result. Then, searching the internet, I found this > > > incredible post: https://hub.qgis.org/issues/11007 > > > > > > It is a well known problem (for 1,5 years!!) that _QGIS is not able to > > > delete shapes in a reliable way_!! I was horrified to read this because > > > it is the same as if a Word processor would not be able to delete a > > > letter from a text. I cannot understand why the QGIS developers haven't > > > fix that yet. If QGIS really wants to compete with ArcMap, they should > > > fix it as soon as possible. At least, the according menu entries or > > > buttons should be inactivated if they don't bring out reliable results. > > > > > > My questions are: > > > > > > · is this information still up to date? I can't read all of the > > > 80 answers to the post now to get in-depth information ... > > > > > > · does anybody have information about how they are planning to > > > handle this problem at the development team? > > > > > > · is there a workaround for this? Do the GRASS vector tools > bring > > > out reliable results? > > > > > > · are there more of those software errors in QGIS that might > lead > > > to huge problems in working on vector data and sharing them with > others? > > > If so, is there a „black list" of things one is never allowed to use in > > > QGIS if you don't want to destroy your datasets? > > > > > > Regards, > > > > > > Uwe Fischer > > > > > > ------------------------- > > > > > > This email and any files transmitted with it are confidential and > > > intended solely for the use of the individual or entity to whom they > are > > > addressed. If you have received this email in error please notify the > > > system manager. This message contains confidential information and is > > > intended only for the individual named. If you are not the named > > > addressee you should not disseminate, distribute or copy this e-mail. > > > Please notify the sender immediately by e-mail if you have received > this > > > e-mail by mistake and delete this e-mail from your system. If you are > > > not the intended recipient you are notified that disclosing, copying, > > > distributing or taking any action in reliance on the contents of this > > > information is strictly prohibited. > > > > > > Whilst reasonable care has been taken to avoid virus transmission, no > > > responsibility for viruses is taken and it is your responsibility to > > > carry out such checks as you feel appropriate. > > > > > > If this email contains a quote or offer to sell products, carry out > work > > > or perform services then our standard terms and conditions [1] shall > > > apply unless explicitly stated otherwise. > > > > > > Saber Razmjooei and Peter Wells trading as Lutra Consulting. > > > > > > _______________________________________________ > > > Qgis-user mailing list > > > Qgis-user@lists.osgeo.org > > > List info: http://lists.osgeo.org/mailman/listinfo/qgis-user > > > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > _______________________________________________ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
