<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi,</p>
<p>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.</p>
<p>@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.</p>
<p>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.</p>
<p>Hopefully, there can be a fix about this Shapefile issue in QGIS 2.14 ...</p>
<p>Andreas</p>
<p>On 2016-01-20 07:34, Matthias Kuhn wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->Hi all,<br /><br /> Here is some more eplanation of the issue:<br /><br /><a class="moz-txt-link-freetext" href="http://gis.stackexchange.com/questions/58101/how-to-avoid-creating-corrupt-shapefiles-during-editing/79677#79677">http://gis.stackexchange.com/questions/58101/how-to-avoid-creating-corrupt-shapefiles-during-editing/79677#79677</a><br /><br /> 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 ;-) )<br /> 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.<br /> 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.<br /> 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.<br /><br /> Best regards,<br /> Matthias<br /><br />
<div class="moz-cite-prefix">On 01/19/2016 10:54 PM, Mats Elfström wrote:</div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div dir="ltr">Hi!
<div>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.</div>
<div>With limited resources, it is even more important that bugs are handled according to a simple risk analysis.</div>
<div>In this case, it would go something like this:</div>
<div>What is the probability that users will edit shape files (high, moderate, low): High</div>
<div>What is the probability that QGIS will damage shape files: Moderate (as I understand)</div>
<div>What is the severity of the potential damage (fatal, reparable, negligible): Fatal</div>
<div>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.</div>
<div>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.</div>
<div> </div>
<div>Regards, Mats.E</div>
<div> </div>
</div>
<div class="gmail_extra"><br />
<div class="gmail_quote">2016-01-19 22:14 GMT+01:00 Saber Razmjooei <span><<a href="mailto:saber.razmjooei@lutraconsulting.co.uk">saber.razmjooei@lutraconsulting.co.uk</a>></span>:<br />
<blockquote class="gmail_quote" style="border-left: 1px #ccc solid; padding-left: 1ex;">
<div lang="EN-GB">
<div>
<p class="MsoNormal"><span style="color: #1f497d;">Dear Uwe,</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">There are some work-arounds and solutions provided within the ticket.</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">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.</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">I totally agree with you that there should be a warning to users to make them aware of this limitation.</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">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). </span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">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:</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"><a class="moz-txt-link-freetext" href="http://qgis.org/en/_downloads/PublicQGISfinancialreport2014.pdf">http://qgis.org/en/_downloads/PublicQGISfinancialreport2014.pdf</a></span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">If you think, there should be more work done to increase the quality of QGIS, you can get involved or contribute to the project:</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"><a class="moz-txt-link-freetext" href="http://qgis.org/en/site/getinvolved/governance/sponsorship/sponsorship.html">http://qgis.org/en/site/getinvolved/governance/sponsorship/sponsorship.html</a></span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="color: #1f497d;">Regards,</span></p>
<p class="MsoNormal"><span style="color: #1f497d;">Saber</span></p>
<p class="MsoNormal"><span style="color: #1f497d;"> </span></p>
<div>
<div style="border: none; padding: 3.0pt 0cm 0cm 0cm;">
<p class="MsoNormal"><strong><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">From:</span></strong><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"> Qgis-user [mailto:<a class="moz-txt-link-abbreviated" href="mailto:qgis-user-bounces@lists.osgeo.org">qgis-user-bounces@lists.osgeo.org</a>] <strong>On Behalf Of </strong>Uwe Fischer<br /><strong>Sent:</strong> 19 January 2016 19:10<br /><strong>To:</strong> 'qgis-user ML'<br /><strong>Subject:</strong> [Qgis-user] QGIS big fail in deleting Shapes!!</span></p>
</div>
</div>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';">Hello all,</span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';"> </span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';">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: <a class="moz-txt-link-freetext" href="https://hub.qgis.org/issues/11007">https://hub.qgis.org/issues/11007</a></span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';"> </span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';">It is a well known problem (for 1,5 years!!) that <em><u>QGIS is not able to delete shapes in a reliable way</u></em>!! 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.</span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';"> </span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';">My questions are:</span></p>
<p><span style="font-family: Symbol;">·</span><span style="font-size: 7.0pt;"> </span><span style="font-family: 'Verdana','sans-serif';">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 ...</span></p>
<p><span style="font-family: Symbol;">·</span><span style="font-size: 7.0pt;"> </span><span style="font-family: 'Verdana','sans-serif';">does anybody have information about how they are planning to handle this problem at the development team?</span></p>
<p><span style="font-family: Symbol;">·</span><span style="font-size: 7.0pt;"> </span><span style="font-family: 'Verdana','sans-serif';">is there a workaround for this? Do the GRASS vector tools bring out reliable results?</span></p>
<p><span style="font-family: Symbol;">·</span><span style="font-size: 7.0pt;"> </span><span style="font-family: 'Verdana','sans-serif';">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?</span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';"> </span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';"> </span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif';">Regards,</span></p>
<p class="MsoNormal"><span style="font-family: 'Verdana','sans-serif'; font-variant: small-caps;">Uwe Fischer</span></p>
</div>
</div>
</div>
<br /><br /><hr />
<p style="font-family: arial,sans-serif; font-size: 10px; color: #999;">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.</p>
<p style="font-family: arial,sans-serif; font-size: 10px; color: #999;">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.</p>
<p style="font-family: arial,sans-serif; font-size: 10px; color: #999;">If this email contains a quote or offer to sell products, carry out work or perform services then our <a href="http://www.lutraconsulting.co.uk/downloads/Lutra%20Consulting%20Standard%20Terms%20and%20Conditions.pdf">standard terms and conditions</a> shall apply unless explicitly stated otherwise.</p>
<p style="font-family: arial,sans-serif; font-size: 10px; color: #999;">Saber Razmjooei and Peter Wells trading as Lutra Consulting.</p>
<br /><br /></div>
<br /> _______________________________________________<br /> Qgis-user mailing list<br /><a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br /> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br /> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></blockquote>
</div>
<br /><br clear="all" />
<div> </div>
-- <br />
<div class="gmail_signature">
<div dir="ltr">______________________________________________<br /> Mats Elfström, Väpplingvägen 21, SE-227 38 LUND, Sweden<br /> tel: +46 46 145959 / mob: +46 70 595 39 35<br /> alt e-mail: <a href="mailto:mats.elfstrom@telia.com">mats.elfstrom@giskraft.com</a><br /><br /></div>
</div>
</div>
<br /><fieldset class="mimeAttachmentHeader"></fieldset><br />
<pre>_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></pre>
</blockquote>
<br />
<pre class="moz-signature">--
Matthias Kuhn
OPENGIS.ch - <a class="moz-txt-link-freetext" href="https://www.opengis.ch">https://www.opengis.ch</a>
Spatial • (Q)GIS • PostGIS • Open Source</pre>
<!-- html ignored --><br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br /> Qgis-user mailing list<br /><a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br /> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br /> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></div>
</blockquote>
<p> </p>
<div> </div>
</body></html>