<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 Richard,</p>
<p id="reply-intro">On 2021-02-04 09:43, Richard Duivenvoorde wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">On 2/4/21 9:23 AM, Andreas Neumann wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">The same discussion also pops up in the Swiss and QGIS user group e-mail lists again and again and I believe it should be able to come up with funding, if some developer could take the lead on implementing this in QGIS core. I was hoping that Jürgen would be available to implement it, as he also did the DXF/DWG importer and it would make sense, that the DXF/DWG importer also integrates with a vector georeferencing solution.</blockquote>
<br />Hi Andreas,<br /><br />Sorry but I fail to see the dxf 'connection' :-). Would this not be a very generic vector tool, for example to be used by people who receive svg's or so.... or data which they do not know the crs of or....</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">I agree that the vector georeferencing should also be possible for other non-dxf data, as a separate tool - but if done properly, both cases would be possible.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
The majority of the DXF files from architects and planners is typically not in the correct CRS coordinates. It is a very common case, having to fit the DXF data to the other GIS data (typical some form of cadastral data). In this case, it would be really, really nice if the DXF/DWG importer could already integrate the vector geoereferencing into the import process.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /><br />Also: this is very much about 'data quality', not sure if I would make QGIS be responsible for fixing data if people feed messy data into QGIS...?</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Yes - but the reality is, that the majority of the DXF/DWG data is not using real-world CRS coordinates, but some local system.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /><br />Isn't it better to make the plugin just work (and also promote it a little, I never would have made the connection about 'vector georeferencing' and 'bender' ;-)</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<p>The vector bender should definitely serve as an inspiration for the core implementation, but I really think this needs to work in QGIS out of the box, without the need of installing plugins.</p>
<p>Plugins are often a major source of instability and frustration for QGIS users ... and they often fail to work in upcoming QGIS releases. This doesn't mean I don't appreciate the work of a plugin developer, in this particular case the work of the author of the "Vector Bender" plugin - the outcome and quality of plugins is often great - but once the functionality of a plugin becomes "mainstream" we should consider implementing the same thing in C++ in QGIS core.</p>
<p>Thanks for the discussion!</p>
<p>Andreas</p>
<p><br /></p>
</body></html>