Hi Markus, Thanks for your response. The error does seem strange given the facts you outline. I can provide you with one of the input files (OSM building polygons) as this is open access (licensing). However, unfortunately the other file contains Maxar building polygons that have strict licensing to my organisation. Hence, I cannot share this file. However, given my past experience with Grass and file size limitations when using the v.select 'disjoint' operation I do not anticipate you having a problem recreating the problem. I suspect that if I share the osm building polygon file with you, and you add a few polygons to a copy of the file, and then perform the disjoint operation on the original osm file verses the copy, that you will most likely be able to reproduce the error. Is this sufficient? If so, how/where do I upload the file? The osm geojson file is just over 4 GB in size. Best wishes, Chris On Thursday, 20 May 2021, 21:20:11 BST, Markus Metz <[email protected]> wrote: Hi Chris, 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. You have already listed the commands leading to the error, could you also provide the input files file.json, file2.gpkg for debugging? Best, Markus M
On Thu, May 20, 2021 at 6:39 PM Christopher Lloyd via grass-user <[email protected]> wrote: 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. Best wishes, Chris On Thursday, 20 May 2021, 16:48:14 BST, Markus Neteler <[email protected]> wrote: Hi Chris, On Thu, May 20, 2021 at 2:00 PM Christopher Lloyd <[email protected]> wrote: > > 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, The vector limit is as follows: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Large_vector_data_processing --> In all GRASS versions, the limit with topology is at time 2^31 - 1 (about 2 billion) features per vector map. > 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. This said, perhaps v.select lacks a proper declaration? Could you tell us how many vector features per map you are dealing with (say: those which work and those which fail)? Best wishes, Markus _______________________________________________ grass-user mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________ grass-user mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-user
