<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<body>
<div dir="auto">
<div dir="auto"><br></div><div dir="auto"><br></div>
<div id="aqm-original" style="color: black;">
<div dir="auto">On December 14, 2022 15:24:28 Stefan Blumentrath <Stefan.Blumentrath@gmx.de> wrote:</div>
<div><br></div>
<blockquote type="cite" class="gmail_quote" style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;">
<div dir="auto">Hei,</div>
<div dir="auto"> </div>
<div dir="auto">I do have a use case where I would like to filter maps in a STRDS by spatial extent before e.g. t.rast.univar processes all registered maps.</div>
<div dir="auto">In particular, I want to process only maps from a STRDS that intersect with the current computational region.</div>
<div dir="auto"> </div>
<div dir="auto">The reason is that the maps registered in the STRDS are collections of single scenes of satellite images or collections of smaller mosaics that cover only parts of the total extent of the STRDS.</div>
<div dir="auto"> </div>
<div dir="auto">Currently, that does not seem to be supported by TGIS, and I see two options to address that:</div>
<div dir="auto"> a) patch the scenes together with a given granularity (e.g. daily mosaics), leave GRASS GIS functions untouched and hope that there is some coverage for reasonable region settings. or:</div>
<div dir="auto"> b) add a spatial filter to the "get_registered_maps"[1] function in abstract_space_time_dataset.py, and then subsequently flags to relevant modules that make use modified function...</div>
<div dir="auto"><br></div>
<div dir="auto">For b) I would think that the most efficient way to handle it would be to add a where clause like it was done for the semantic labels? In that case, it may make sense to add an index for north, south, east, and west too, no? Maybe also top and bottom...</div></blockquote></div><div id="aqm-original" style="color: black;" dir="auto"><blockquote type="cite" class="gmail_quote" style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;"><div dir="auto"></div>
<div dir="auto"><br></div>
<div dir="auto">My main question, however is if my case is just a corner case, or does some sort of spatial filteing possibility make sense in general / more broadly...</div></blockquote></div><div dir="auto"><br></div><div dir="auto">It seems a bit of a corner case, but in fact something I could use, of I understand it right. </div><div dir="auto"><br></div><div id="aqm-original" style="color: black;" dir="auto"><blockquote type="cite" class="gmail_quote" style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;"><div dir="auto"></div>
<div dir="auto"><br></div>
<div dir="auto">Any feedback is much appreciated, esp. before I evtl. start working on b).</div>
<div dir="auto"><br></div>
<div dir="auto">Kind regards,</div>
<div dir="auto">Stefan</div>
<div dir="auto"><br></div>
<div dir="auto">1) https://github.com/OSGeo/grass/blob/main/python/grass/temporal/abstract_space_time_dataset.py#L1604</div>
<div dir="auto"><br></div>
<div dir="auto">_______________________________________________</div>
<div dir="auto">grass-dev mailing list</div>
<div dir="auto">grass-dev@lists.osgeo.org</div>
<div dir="auto">https://lists.osgeo.org/mailman/listinfo/grass-dev</div>
</blockquote>
</div><div dir="auto"><br></div>
</div></body>
</html>