Hi Andreas

Of course I fully understand your point about the need for financing, and 
hopefully George`s offer will change things for topological correct editing.

However, there could be several reasons for a lack of funding until now:
Probably, many users are not really aware of the bug(s)? Back in 1.7.4 editing 
was no longer possible once invalid geometries were produced by "Avoid 
intersection" and users got an error message. Nowadays, you can continue 
digitizing without noticing that geometries are not topologically correct. The 
result looks good and you have to actively search (or check) for such 
digitization errors. I guess, not everybody does that, so I assume also a lack 
of awareness could be a reason for the lack of funding...

Furthermore, some users who are aware may prefer such (of course not too 
convenient) workarounds over trying to raise some money for funding a proper 
fix.
And finally, as it is unfortunately the case for me - for example -, even if I 
am seriously affected by the bug it is really very difficult (for not to say 
impossible) to raise a reasonable amount of money to get this (or another bugs) 
fixed, because:
In my Institute ArcGIS is the "Standard" GIS application, and I am one of few 
"nerds" (that is at least how I feel I am sometimes being looked at) who use 
OSGeo products. I was and am actively promoting (amongst other OSGeo 
applications) QGIS in my institute because I am convinced that QGIS is in many 
cases much more suitable for our purposes than ArcGIS. One very important 
activity is mapping (and digitizing) habitat types for public authorities, who 
request data with proper topology.
So, the topology problems are definitely an obstacle regarding promoting QGIS 
here. And since my bosses already paid for ArcGIS licenses (which does not have 
these problems) and a wider introduction of QGIS will also cause some extra 
transaction costs (e.g. learning) in short term, the consequence is that my 
institute will stick to ArcGIS. This makes it extremely difficult to convince 
my bosses to donate some money for bug fixing, even though QGIS offers (from my 
point of view) superior solutions for our problems and we will benefit from 
using QGIS in the long run... It is a bit of a witches circle in a way, and the 
only alternative would be to use private money...

Cheers
Stefan


-----Original Message-----
From: qgis-developer-boun...@lists.osgeo.org 
[mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf Of Andreas Neumann
Sent: 14. november 2013 10:54
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Bug with avoid intersection - willing to fund fix

Hi,

So if there is so much interest in having this issue fixed I assume that there 
would be plenty out there who would fund the fix!

The fix won't happen if noone pays for it - just complaining about this does 
not help.

Get an estimate from some developer (e.g. Sandro Santilli oder
Sourcepole) to know how much it would cost to fix.

As much as I like GRASS - and it is very good to know that this workaround 
exists (thanks Stefan for mentioning it!) - I don't think it is reasonable to 
ask people to go through GRASS to get proper data out of their QGIS digitized 
data set.

Who will take the lead to ask a developer?

Andreas

Am 14.11.2013 10:40, schrieb Blumentrath, Stefan:
> Hi George
> 
> I had a lot of trouble with those issues too, and I would really love to see 
> them fixed. In other words, I agree with Giovanni that these are pretty 
> important bugs for many and not really uncommon digitization use-cases and 
> would support his categorization as blocker...
> 
> However, my current workaround is to ignore the untidiness in the topology at 
> first and then send the vector dataset through GRASS which is (at least for 
> not too big datasets) quite convenient using the Sextante/Processing 
> framework (see also discussion here):
> http://osgeo-org.1560.x6.nabble.com/Running-v-clean-on-a-QGIS-vector-l
> ayer-Polygon-through-Sextante-td5050418.html
> 
> Cheers
> Stefan
> 
> 
> 
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to