I have a very large dataset (about 120k records) and about a dozen layers, all focused on California for the moment. That is, all the shapes like zips, census tracts, counties etc. are selected using the query builder to narrow to just this state.

My issue is when I try to export a qgis2web map on my Win7, what ends up happening is my computer disk space gets maxed out to whatever I have available (currently 65GB) as there is a .tif file being created (ostensibly by the qgis2web plugin but, I'm not certain it's not a setting or another plugin conflict). Is that the norm and am I simply supposed to provide more disk space for such a gigantic image file?

I'm also using a hosted GeoServer to host my shapefiles and have my data in a postgres/postGIS-extended database. My belief is it's somewhat foolish to parse all that data in QGIS to create a map when in effect the data and shapes for the map I end up making (in OpenLayers or Leaflet) will be called from GeoServer.

Is there a way to minimize the load on QGIS w/ qgis2web so that it can do it's job more efficiently and I load the GeoJSON file with the 112k data records manually?

QGIS 2.16.1 | qgis2web v1.13.1 | GeoServer 2.9.0 | Postgres 9.5.4 | PostGIS 2.2.2r14797

  • Are any of the layers rasters? My understanding is that qgis2web outputs geojson's rather than rasters. I haven't had success getting the qgis2web plugin to work for raster layers. It seems that this is where "tiling" typically comes in. You could try running qgis2web with just a single layer, getting the basic framework/index.html for the webpage, and then manually adding the rest of the layers... – jbukoski Aug 13 '16 at 4:54
  • If all my shapes and data are hosted via my Postgre/PostGIS GeoServer, isn't there a way to call the data from there using server-side processing vs loading all the geojson data into the map sourcecode itself? I also wonder if there's a reason I'm not seeing why the qgis2web crashes or can't produce a big enough file. Isn't that a function of my computer's memory (processing time) and my level of patience? – enjoypb Aug 14 '16 at 22:05

For your Geoserver layers, make sure you don't check "Encode to JSON". That should leave the layers as remote WFS layers. However, they will still load fully - I need to find out whether I can implement viewport bbox loading.

TIFFs are created if you have raster layers - disable any you have, I guess, since you imply that you don't expect to have any raster output.

  • Thanks Tom. Great job on this tool. You gave me a clue, and is it fair to say, that I should be creating my layers as WMS vs. starting and calling everything from GeoServer through the GeoExplorer. Would that allow me to create the export with qgis2web without so much (I'm assuming) overhead? – enjoypb Aug 19 '16 at 4:38
  • Yes, that would do it, definitely in the case of WMS, and with the proviso I mentioned above (which is probably a blocker for you) that WFS layers are (I think) downloaded completely, rather than just features visible. Further testing needed to confirm that last point, as it might differ between qgis2web's Leaflet and OpenLayers 3 output. – Tom Chadwin Aug 19 '16 at 15:11
  • In a word, yes. Come back with any other questions or issues, probably as a new question – Tom Chadwin Aug 21 '16 at 19:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.