<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Stefan,<br>
<br>
I agree this is an important area and deserves being addressed
properly.<br>
It is also one that would be perfect for a set of unit tests.<br>
<br>
I noticed that you started to collect issues that have been filed
concerning this topic or related ones, I think this is a very good
initiative.<br>
<br>
A good approach to deal with this topic would be to<br>
* create a list of variables that influence the calculation<br>
* create a set of combinations of these variables (or eventually a
full matrix) with expected results<br>
<br>
Once this is formulated it should be straightforward to create unit
tests, see which calculations are wrong and then fix them while
being sure not to break others (because of the test suite).<br>
Will you be present in Denmark?<br>
<br>
Kind regards,<br>
Matthias<br>
<br>
<div class="moz-cite-prefix">On 05/11/2015 09:57 AM, Blumentrath,
Stefan wrote:<br>
</div>
<blockquote
cite="mid:d0787246ab0747afb3ce8d8748a8afd7@NINSRV23.nina.no"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0cm;
margin-right:0cm;
margin-bottom:8.0pt;
margin-left:0cm;
line-height:106%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear devs,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">With QGIS you delivered
a really excellent product with tons of useful features and
I am very fond of it. I am aware that you get lots of user
requests and have to prioritize according to that. Yet, my
humble feeling is that there is one topic which did/does not
receive the attention it probably deserves.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Proper area and distance
calculation is a central functionality of any GIS. It is
used by probably 97.5% of the users and should work in any
case and without the need for the user to define some (at
least for beginners) non-obvious settings, which in addition
can get changed back by QGIS without the user`s notice, e.g.
when loading data in different CRS (including Open Layers).
Unfortunately, this seems to be a long open issue in QGIS
(see: <a class="moz-txt-link-freetext" href="https://hub.qgis.org/issues/12057">https://hub.qgis.org/issues/12057</a>). If I may make one
wish for the Hackfest next week, please make Bug #12057 (and
related issues) a top priority of the event!
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If such basic
functionality gives wrong results, personally I would
consider it as a risk for the good reputation of the QGIS
project. Assume a user delivered project results to a
customer, which are based on wrong area calculations (not
unlikely that this happens), what do you think he or she
feels about QGIS after that... And even if one discovers it
beforehand. That does not exactly contribute to the user`s
faith in the reliability of QGIS.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I dare say that this
series of bugs is so severe, that if it gets fixed
(hopefully one and for all), it would provide reason enough
to justify a 2.8.3 release (BTW. Thanks for 2.8.2).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Probably also worth
writing a test for this bug, given it`s (long) history?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Stefan<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>