<div dir="ltr"><div>Hi Chris,</div><div><br></div><div>this " ERROR: Unable to seek: Invalid argument" is a strange error because v.select uses exactly the same functions to seek and read data as the modules you used to produce the input vectors for v.select.</div><div><br></div><div>You have already listed the commands leading to the error, could you also provide the input files file.json, file2.gpkg for debugging?</div><div><br></div><div>Best,</div><div><br></div><div>Markus M</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 20, 2021 at 6:39 PM Christopher Lloyd via grass-user <<a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:verdana,helvetica,sans-serif;font-size:13px"><div></div>
<div dir="ltr">Hi Markus, Thanks for your reply - sure. In current and previous successful runs of the disjoint operation in v.select I have input shapefile subsets of up to 2 GB in file size (file size just the shp file extension itself - not dbf etc.). Shapefiles of 2.5 GB size failed and had to be split. These correspond to 10,659,000 features and 12,159,000 features respectively. I don't believe that the error is linked to any intrinsic limitation of the shapefile format as I also receive the same error when I input to Grass the (unsplit) polygon datasets in geojson or geopackage format.</div><div dir="ltr"><br></div><div dir="ltr">Best wishes, Chris</div><div dir="ltr"><br></div>
</div><div id="gmail-m_-2811439781530378454yahoo_quoted_1739117157">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div>
On Thursday, 20 May 2021, 16:48:14 BST, Markus Neteler <<a href="mailto:neteler@osgeo.org" target="_blank">neteler@osgeo.org</a>> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Chris,<br clear="none"><br clear="none">On Thu, May 20, 2021 at 2:00 PM Christopher Lloyd<br clear="none"><<a shape="rect" href="mailto:chrislloyd2@yahoo.co.uk" target="_blank">chrislloyd2@yahoo.co.uk</a>> wrote:<br clear="none">><br clear="none">> Hi Markus, Having split my input data into smaller sized shp files, these now process fine using v.select. So clearly the problem that I had lies with some file size limitation with the v.select 'disjoint' algorithm - also failing with one input file prior using the v.extract algorithm. The original (large) input files input to grass ok using v.in.ogr,<br clear="none"><br clear="none">The vector limit is as follows:<br clear="none"><br clear="none"><a shape="rect" href="https://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Large_vector_data_processing" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Large_vector_data_processing</a><br clear="none">--> In all GRASS versions, the limit with topology is at time 2^31 - 1<br clear="none">(about 2 billion) features per vector map.<div id="gmail-m_-2811439781530378454yqtfd94288"><br clear="none"><br clear="none">> but then failed when using v.select. Might you be able to indicate the file size limitation for the v.select algorithm and the reasons for this? Thanks.</div><br clear="none"><br clear="none">This said, perhaps v.select lacks a proper declaration?<br clear="none"><br clear="none">Could you tell us how many vector features per map you are dealing<br clear="none">with (say: those which work and those which fail)?<br clear="none"><br clear="none">Best wishes, Markus<div id="gmail-m_-2811439781530378454yqtfd60449"><br clear="none"></div></div></div>
</div>
</div></div>_______________________________________________<br>
grass-user mailing list<br>
<a href="mailto:grass-user@lists.osgeo.org" target="_blank">grass-user@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/grass-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/grass-user</a><br>
</blockquote></div>