<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
Hi and thanks for your response,<br>
</div>
<div class="BodyFragment"><font size="2">
<div class="PlainText"><br>
</div>
<blockquote style="border-color: rgb(200, 200, 200); border-left: 3px solid rgb(200, 200, 200); padding-left: 1ex; margin-left: 0.8ex;" itemscope="" itemtype="https://schemas.microsoft.com/QuotedText">
<span style="font-size:11pt">
<div class="PlainText">Most likely. I would try splitting these big faces into smaller<br>
</div>
<div class="PlainText">pieces. A way to do so would be inserting abitrary lines cutting<br>
the plane into a grid. This would also split lines, further<br>
reducing working set for each further insertion. You could add<br>
these lines upfront or during the load, to see how they affect<br>
</div>
<div class="PlainText">the loading (it's good that you use multiple transactions).</div>
</span></blockquote>
<span style="font-size:11pt">
<div class="PlainText"><br>
</div>
<div class="PlainText">Never thought of that approach, it seems a good way to go.</div>
<div class="PlainText">My only doubt about this is that we use a no tolerance topology, but there is a need for snaps (that will be made manually) but only on start/end points. With this approach I will have to ignore the nodes where lines and grid intersect,
but it seems feasible.</div>
<div class="PlainText">I don't get the part of adding during load, do you mean when adding a line if there is no grid line nearby, to create it before insert it?</div>
<div class="PlainText"><br>
</div>
<blockquote style="border-color: rgb(200, 200, 200); border-left: 3px solid rgb(200, 200, 200); padding-left: 1ex; margin-left: 0.8ex;" itemscope="" itemtype="https://schemas.microsoft.com/QuotedText">
<div class="PlainText">What version of PostGIS are you using ? What GEOS version ?</div>
</blockquote>
<div class="PlainText">POSTGIS="3.0.1 ec2a9aa" [EXTENSION] PGSQL="120" GEOS="3.7.1-CAPI-1.11.1 27a5e771" PROJ="Rel. 5.2.0, September 15th, 2018" LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.3.1" WAGYU="0.4.3 (Internal)" TOPOLOGY<br>
<br>
</div>
<blockquote style="border-color: rgb(200, 200, 200); border-left: 3px solid rgb(200, 200, 200); padding-left: 1ex; margin-left: 0.8ex;" itemscope="" itemtype="https://schemas.microsoft.com/QuotedText">
<div class="PlainText">Note that the Polygonize function will NOT properly setup edge-linking<br>
(next_right_edge, next_left_edge) so you'd still not end up with a valid<br>
</div>
<div class="PlainText">topology when only using AddEdge + Polygonize.</div>
</blockquote>
<div class="PlainText">I hadn't noted it, i saw the fields were populated and not realized that it only references itself. In a first step I'm only using the topology to fix snaps and generate faces. Is there any downside to not having the edge linking correct?<br>
</div>
<div class="PlainText"><br>
<blockquote style="border-color: rgb(200, 200, 200); border-left: 3px solid rgb(200, 200, 200); padding-left: 1ex; margin-left: 0.8ex;" itemscope="" itemtype="https://schemas.microsoft.com/QuotedText">
One improvement that was implemented in spatialite was to allow for<br>
TopoGeo_addLinestring to NOT detect the creation of new faces while<br>
still doing edge-linking. It still implied constructing an invalid<br>
<div>topology but the Polgonize step would then make it valid.<br>
</div>
</blockquote>
<div>I saw your PR trying this approach for batch creation, unfortunately my knowledge of the topology codebase is very small to help in this matter. But is there any way of funding to make this feature happen?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Alexandre Silva<br>
</div>
</div>
</span></font></div>
<img src="http://newsletter.impresapublishing.pt/i/barra_ip.jpg">
</body>
</html>