<html><head></head><body><div class="ydp25afb989yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Well, it is linked with other aspects, maybe the two more important I see are:</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Learning curve: To create a new layer and populate it well, you need to understand TopoGeometry, Layers, TopoElements and maybe Components, be able to do something like:</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div> INSERT INTO states (name, tgeom)<br clear="none"> SELECT state_name, CreateTopoGeom(<br clear="none"> 'mytopo',<br clear="none"> 3, -- areal<br clear="none"> layer_id(findLayer('states', 'tgeom'))<br clear="none"> TopoGeometryArray_agg(tg)<br clear="none"> )<br clear="none"> FROM counties<br clear="none"> GROUP BY state_name;</div></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Simplifies a lot the understanding of it.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div dir="ltr" data-setdir="false">This also helps to know if we are doing it wrong, knowing the TopoGeometries we are going to use as child, we can verify they are actually childs of that layer, and stop the query, we can't do that with TopoElements, this also helps when we are trying to use or start using Topology.</div></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Probs using something like this would impact on performance, the check and some internal conversions, still the code would need to transform to TopoElements, I think in the other hand, if this has not a big impact, would be useful to have nicer code knowing what we are doing is right, we can always make mistakes, and this is something we can handle.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thx!<br></div></div><div id="yahoo_quoted_2274846955" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
El miércoles, 13 de noviembre de 2024, 11:56:55 a. m. GMT-3, Sandro Santilli <strk@kbt.io> escribió:
</div>
<div><br></div>
<div><br></div>
<div>On Wed, Nov 13, 2024 at 12:44:26PM +0000, Felipe Matas wrote:<br clear="none"><br clear="none">> I still I think would be nicer to work directly with TopoGeometries<br clear="none">> than TopoElements in this cases, is also more intuitive, there is a lot<br clear="none">> of advantages to use them :)<br clear="none"><br clear="none">Concrete proposals are welcome, with example queries.<br clear="none"><br clear="none">Right now you would do something like this:<br clear="none"><br clear="none"> INSERT INTO states (name, tgeom)<br clear="none"> SELECT state_name, CreateTopoGeom(<br clear="none"> 'mytopo',<br clear="none"> 3, -- areal<br clear="none"> layer_id(findLayer('states', 'tgeom'))<br clear="none"> TopoElementArray_agg(tg::TopoElement)<br clear="none"> )<br clear="none"> FROM counties<br clear="none"> GROUP BY state_name;<br clear="none"><br clear="none">How would you make it more intuitive ?<div class="yqt0557720861" id="yqtfd92763"><br clear="none"><br clear="none">--strk;<br clear="none"></div></div>
</div>
</div></body></html>