On Fri, 29 Jul 2022 at 06:22, Madry, Scott via Qgis-user
wrote:
>
> Thanks Chris, but I do think that this is a topic is worth considering by the
> QGIS community, beyond the limitations of the archaeic shapefile format. We
> are moving into an era of very big data, both raster and vector, and Q
A shapefile is a vector files, as far as I know. I don't think any
rasters are stored in this format.
If there is a large volume of data, it may have a great many records
referencing a large number of features. Vector layers are usually made
up of a number of points that together form one feat
Thanks Chris, but I do think that this is a topic is worth considering by the
QGIS community, beyond the limitations of the archaeic shapefile format. We are
moving into an era of very big data, both raster and vector, and QGIS should be
able to meet this challenge. This will require some foresi
*chris hermansen*
/Thu Jul 28 13:05:08 PDT 2022/
With respect I think this conversation is moving off the point, which was
related to a 5gb shapefile
https://en.m.wikipedia.org/wiki/Shapefile
Which is beyond the design limi
Scott and list,
With respect I think this conversation is moving off the point, which was
related to a 5gb shapefile
https://en.m.wikipedia.org/wiki/Shapefile
Which is beyond the design limits of the Shapefile standards and perhaps
therefore the source of the problem that the OP has.
Notably no
Dear colleagues,
As we move more into the world of big data, IOE, data mining, and data
analytics, dealing with larger and larger data sets will become required, and,
eventually, the norm.
GRASS GIS has made very good progress in this regard, optimizing the code to
run on massively parallel co
On 7/28/2022 5:52 AM, krishna Ayyala via Qgis-user wrote:
dbf file itself is 5.1GB. Rest all other files are
less than 500MB. It is the number of records which is huge. It
has about 117,2100 points.
Is that 117,200 points or 1,172,10
You could export the shapefile and use *Layer Options > RESIZE=YES*. This
is the same as the ogr2ogr switch *-lco RESIZE=YES*, which reduces the
attribute column widths down to their minimum width required to store
the longest actual value in the data. A dbf file allocates space for the
full column
Past a point, trying to run a GIS app with very large data structures
just doesn't work well. If you really need all the information you're
carrying around for your analysis or whatever, you may need to reach for
different tools or use the tools you have differently.
I assume it's not so much
so, maybe you should really drop all unneccessary fields or maybe all but an id
field, and then create a relation to the original database, but in any case I
would convert that stuff away from ESRI-Shape to Geopackage beforehand, as is
it is a pita.
On 28.07.22 13:52, krishna Ayyala wrote:
d
dbf file itself is 5.1GB. Rest all other files are less than 500MB. It is
the number of records which is huge. It has about 117,2100 points.
On Thu, Jul 28, 2022 at 12:02 AM Bernd Vogelgesang via Qgis-user <
qgis-user@lists.osgeo.org> wrote:
> how big is the dbf file of that shape? Maybe you can
Hi,
There is a distinct possibility that the 5GB shape file is corrupt or that it
will be if you manipulate it. It’s too big for the normal shape file format.
I would first save it as a geopackage then stat looking at why the file is so
big.
Unless shapes can be simplified without loosing
how big is the dbf file of that shape? Maybe you can also drop some
attributes.
Am 28.07.22 um 03:46 schrieb krishna Ayyala via Qgis-user:
Hello,
I have a shapefile of 5GB in size. Is it possible to convert this
shapefile to a smaller size file? It can be any format, not
necessarily a shapefile.
Hello,
I have a shapefile of 5GB in size. Is it possible to convert this shapefile
to a smaller size file? It can be any format, not necessarily a shapefile.
But, preferably a vector format. I tried to convert it into tiles, but that
didn't work as it was losing the resolution. I am looking to conv
14 matches
Mail list logo
