Jiri Drbalek

I still don't know what exactly causes that deadlock, but Mapnik package from Alpine works - no surprise - well: My test app: ```c++ #include #include #undef NDEBUG #include int...

Building node-mapnik: ```dockerfile FROM mapy-sk-mapnik-build:latest RUN apk add nodejs npm WORKDIR /build RUN git clone https://github.com/mapnik/node-mapnik.git WORKDIR node-mapnik RUN git checkout v3.0.x RUN git submodule update --init RUN make release_base...

There are more ways how to deal with clipped features. The avoid-edges is rather radical one, but the only fully reliable. You have to use it for all colliding features,...

A problem in many cases is that `node::Buffer` is created from `std::string` which cannot handover its internal buffer ownership to non-`std::string` object.

I think this is great solution. It can be a simple wrapper function around `Nan::NewBuffer()`.

The `mapnik/value` directory is not missing. It's part of the main dependency - Mapnik itself ( https://github.com/mapnik/mapnik/tree/master/include/mapnik/value) - which is apparently not installed in a directory visible to the build...

Hi @shawmat, it's not about downloading these files manually. Before building python-mapnik, you must [install Mapnik](https://github.com/mapnik/mapnik/blob/master/INSTALL.md).

@clebio Only `mapnik-config` has to be available in `PATH`. `setup.py` fetches needed information through the `mapnik-config` like [here](https://github.com/mapnik/python-mapnik/blob/947db1b362145bd26cef1e70beeff8dd91c919bd/setup.py#L114).

@clebio This is different problem. I'm also not able to compile latest mapnik with latest python-mapnik because of some breaking changes in mapnik. What is working for me is combination...

This does not necessarily need to be a part of Node Mapnik. There might be some Node module that can encode PNG this way giving it raw data from `img.data()`.