Use Clip Raster by Mask tool from the Toolbox and click on the green iterator to clip the raster image by each smaller boundary inside the shapefile:
Using the above tool with iterator enabled, here is the result:
qgis2web supports rule-based symbology. However, it only supports a very limited number of expressions. Your rules probably contain expression functions not supported by qgis2web.
If you can post an exported QML style as a new issue at https://github.com/tomchadwin/qgis2web/issues, someone can investigate whether qgis2web can be enhanced to support the ...
By using this expression :
color_hsv(0, scale_exp( day( age( "END" , animation_datetime() )),0,365,10,100,2),100)
In the data defined override for your polygon fill color you get the effect from red to pale red as the time goes.
This work like this color_hsv set the color with H set at 0 (for
red), S set as a scale_exp fonction to change over time and V ...
In my case, at least, I worked out that it depends on whether my cursor (ready for the next click to create the next point in the line or polygon) is hovering over any map feature in any level that it could snap to. If so, a hover text should appear by your cursor showing the name of that feature. Right-clicking doesn’t work when this is the case. But just ...
You can also use QGIS (which is open source) and/or Blender plugin Blender GIS.
Using QGIS, you can make a SHP (shapefile) out of a DEM and with Blender GIS you make a mesh out of the SHP (see this question and this question), or, you can import SRTM directly into Blender using only Blender GIS.
With the QGIS > Vector general > Merge vector layers tool I recently ran into a similar issue (missing or ´NULL´ed attributes in the resulting merged layer). As a solution I recommend using the SAGA > Vector general > Merge vector layers tool:
It has additional options for adding source information and matching fields by name:
We could create a new button on the toolbar which lets you choose a style to apply to the selected layer by writing some code into the Python Console. Open the console using Ctrl + Atl + P and then copy/paste the code below:
action = QAction(QIcon(""), "Load style for selected layer", iface.mainWindow())
What about forgoing 0.5D?
If you don't really need extruded polygons, bot only a 3D-like representation, the 2.5D rendering option might work for you.
You can apply a calculated value to be used as "extrusion" height, based on one or multiple fields.
Of course this is not a real extrusion, but might suffice in many cases.