Martin Ždila

Workaround is to extract mask from the tiff and do the composition using nested layers and correct comp-op operations. See https://github.com/mapnik/mapnik/issues/4209#issuecomment-772855269

I have no plans, but if you want I will do it as I introduced this buggy feature :-). I am not sure about the exact input to replicate this...

I tried to add some debug messages and recompile it all but now it fails with runtime error: ``` Error: projection::forward not supported without proj4 support (-DMAPNIK_USE_PROJ4) ``` Any hint...

You can find `no_foot.svg` at https://github.com/FreemapSlovakia/freemap-mapnik/blob/develop/images/no_foot.svg Reduced sample: ```xml [no_foot] = 1 accessRestrictions geojson {"type":"Feature","geometry":{"type":"LineString","coordinates":[[-0.000004,0],[0.000004,0]]},"properties":{"no_foot":1}} ```

I am missing `simplify` for (multi)polygons which is mentioned in issue description. Also for GeometryCollections (it would simplify all (multi)linestrings there). I think it deserves a separate issue. May I...

In my case it would be useful for knowing `admin_centre` nodes in `process_relation`.

Thank you. I actually ended with `copy_path_flat` as I am using Cairo-rs.

I had this problem while executing `VACUUM` where huge temp file was attempted to be created in `/var/tmp`. Workaround: `SQLITE_TMPDIR=/path/to/alternative/tmp sqlite3 db.mbtiles`

Thanks for your solution, but... > I don't believe that dispatching in the cancelled$ will work for you since once things are cancelled, I don't send anything that is dispatched...

> Problem with doing it in SQL is that parameterization (variables) can't be used there. Variables should actually be supported in SQL escaped by `!`: `!@variable!`