What are you drawing that needs 180 GB of data? That's the whole
question. That's a lot of data for vectors.
In other words going back to my previous point - you do not need to draw
all of the detail at lower scales. Use scaling rules to address that and
performance should show a big increase.
On 21/07/22 08:42, Andreas via Qgis-user wrote:
Hi Asim,
meanwhile I found out that creating a spatialite database needs (unlike
postgres) only very little RAM for building. On the other side, after
running a wole day and night on conversion of the ~30GB osm_europe.pbf
with ogr2ogr, I have a 180 GB database now which needs minutes to load...
Don't know if postgres is more performant. Setup is much more
complicated.
Regards,
Andreas
Am 20.07.22 um 03:43 schrieb Asim:
>
> On 7/15/22 4:11 PM, Andreas via Qgis-user wrote:
>> I think postgres itself is not the problem at all, but the scripts
that
>> move the vector tiles into the database. In the instructions for usage
>> of these import scripts is written that they need at least as much RAM
>> as the size of the vector file. So I assume it has to load the whole
>> file into memory before it can be processed.
>
> Thank you for the clarification, Andreas. I'm new to the GIS ecosystem
> but the OGR FDW seems to be addressing the problem of not having to
load
> entire vector data at once: https://github.com/pramsey/pgsql-ogr-fdw.
>
> Asim
>
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
